[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference koolit::document

Title:VAX DOCUMENT
Notice:See also BOOKIE::CUP_DOCTYPES
Moderator:NSIC00::KLERK
Created:Thu Jul 30 1987
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4794
Total number of notes:23435

4751.0. "ACCVIO in SOFTWARE.ONLINE Device Conversion; V3.0B" by XDELTA::HOFFMAN (Steve, OpenVMS Engineering) Fri Apr 05 1996 14:22

T.RTitleUserPersonal
Name
DateLines
4751.1Support Contact(s)?XDELTA::HOFFMANSteve, OpenVMS EngineeringFri Jun 14 1996 10:153
4751.2MOLAR::DELBALSOI (spade) my (dogface)Fri Jun 14 1996 10:413
4751.3Resending...XDELTA::HOFFMANSteve, OpenVMS EngineeringFri Jul 19 1996 10:585
4751.4No Change In V3.2B: Still ACCVIO'ing...XDELTA::HOFFMANSteve, OpenVMS EngineeringThu May 08 1997 17:1838
$   DOCUMENT /CONTENTS/INDEX/NOPRINT/CONDITION=xxx -
        xxx$SRC:xxx_IG_NF.SDML SOFTWARE.ONLINE BOOKREADER  /OUT=xxx$DOC:
%DOC-I-IDENT, DECdocument  V3.2B (c) 1995-1997 Touch Technologies, Inc.
[ T a g    T r a n s l a t i o n ]...
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-SETCONDTN, Setting condition xxx
   on line 1 of file xxxD$:[xxx.xxxDOC.SRC]xxx_IG_NF.SDML;2
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-FILEWRTOK, File xxx_IG_NF_FRONT_MATTER.TEX written
%TAG-I-FILEWRTOK, File xxx_IG_NF_PRE-INSTALL.TEX written
%TAG-I-FILEWRTOK, File xxx_IG_NF_THE-INSTALL.TEX written
%TAG-I-FILEWRTOK, File xxx_IG_NF_POST-INSTALL.TEX written
%TAG-I-FILEWRTOK, File xxx_IG_NF_AP_NEW_FEATURES.TEX written
%TAG-I-FILEWRTOK, File xxx_IG_NF_AP_EXAMPLE.TEX written
[ T e x t    F o r m a t t i n g ]...
%TEX-I-LINETOOSHORT, Line too short - on page [118]
%TEX-I-LINETOOSHORT, Line too short - on page [118]
%TEX-I-LINETOOSHORT, Line too short - on page [123]
%TEX-I-PAGESOUT, 128 pages written.
-TEX-I-OUTFILENAME, 'xxxD$:[xxx.xxxDOC]xxx_IG_NF.DVI_BOOKREADER'
[ C o n t e n t s   G e n e r a t i o n ]...
[ T e x t    F o r m a t t i n g   C o n t e n t s ]...
%TEX-I-PAGESOUT, 46 pages written.
-TEX-I-OUTFILENAME, 'xxxD$:[xxx.xxxDOC]xxx_IG_NF_CONTENTS.DVI_BOOKREADER'
[ I n d e x    G e n e r a t i o n ]...
%INX-I-READING, reading file 'xxxD$:[xxx.xxxDOC]xxx_IG_NF.INX'
%INX-I-WRITING, writing file 'xxxD$:[xxx.xxxDOC]xxx_IG_NF_INDEX.TEX;'
%INX-S-CREATED, 'xxxD$:[xxx.xxxDOC]xxx_IG_NF_INDEX.TEX;' created
[ T e x t    F o r m a t t i n g   I n d e x ]...
%TEX-I-PAGESOUT, 163 pages written.
-TEX-I-OUTFILENAME, 'xxxD$:[xxx.xxxDOC]xxx_IG_NF_INDEX.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
%DVC-I-INCLUDING, including input file:
   xxx_IG_NF_CONTENTS
%SYSTEM-F-ACCVIO, access violation, reason mask=00, 
virtual address=0000000065636F79, PC=000000000801806B, PS=00000002
$

4751.5ACCVIO Sensitive To <LMF> Tags -- Old Bug Is Back?XDELTA::HOFFMANSteve, OpenVMS EngineeringThu May 08 1997 17:2415
   Interestingly, this ACCVIO appears to be sensitive to the LMF tags. 
   When I remove the tags -- well, actually, when I comment the tags
   out -- the ACCVIO goes away.

<COMMENT>
<LMF>(VDE_IG_FRONT)
<LMF_PRODUCER>(DEC)
<LMF_PRODUCT>(xxx)
<LMF_RELEASE_DATE>(0)
<LMF_VERSION_NUMBER>(0)
<LMF_ALTNAME>(BOOKBROWSER)
<ENDLMF>
<ENDCOMMENT>

4751.6Where?FORTY2::KNOWLESPer ardua ad nauseamFri May 09 1997 05:0222
    Where are the tags you give in .-1? They have to appear before any tag
    that produces text. I don't know what error you'll get if you go
    against this, but this *may* be your problem.
    
    The first place people think of to put them is immediately after the
    title [BONG]. I find the most reliable practice is to use the
    <LMF_INFO> tag immediately after the title, with an argument
    pointing to the LMF info. Then put the LMF tags in a symbols file.
    (This will encourage you and your colleagues to use *one* set of LMF
    tags with a multi-book licence identifier - I think that's what it's
    called - which'll make things even more intuitive, manageable, and less
    error-prone.)
    
    b
    
    ps I still use 2.1 and can't vouch for anything that may or may not
    happen on 3.2B (or indeed what may or may not be documented now).
    
    pps Another possible explanation for your error is that you're (maybe
    unknowingly) specifying LMF info twice. Use SEARCH *.SDML to check this
    out. I think DOCUMENT would stop processing rather more gracefully in
    this case, but it certainly wouldn't like it. 
4751.7<LMF>: As Close To The Front As Allowed...XDELTA::HOFFMANSteve, OpenVMS EngineeringFri May 09 1997 16:1933
:    Where are the tags you give in .-1?

   As mentioned, I've disabled all LMF tags, and now all manuals I
   have been having trouble with are now building...

   Here are the first tags from the first module included via the
   first <element> in the profile file -- three tags precede the <LMF>
   tag -- <PROFILE>, <ELEMENT>(for the attached file) and <FRONT_MATTER>.


<FRONT_MATTER>(xxx_MANUAL_FRONT)

<comment>
<LMF>(xxx_MANUAL_FRONT)
<LMF_PRODUCER>(DEC)
<LMF_PRODUCT>(xxx)
<LMF_RELEASE_DATE>(0)
<LMF_VERSION_NUMBER>(0)
<LMF_ALTNAME>(BOOKBROWSER)
<ENDLMF>
<endcomment>

<TITLE_PAGE>
<INCLUDE>(xxx$SRC:xxx_SYMBOLS.SDML)
<SET_CONDITION>(xxx_MANUAL_FRONT_MATTER)
<PRODUCT>(xxx)
<comment>(<LMF_INFO>(xxx_MANUAL_FRONT))
<TITLE>(<REFERENCE>(xxx_MANUAL_NAME_1)<LINE><REFERENCE>(xxx_MANUAL_NAME_2))
<ORDER_NUMBER>(<REFERENCE>(xxx_order))

...

4751.8Try thisFORTY2::KNOWLESPer ardua ad nauseamTue May 13 1997 05:4723
    It's a while since I built a Bookreader book in anger, so my info may
    be Best Before March 1996, but if I were you I'd move these tags -
    
    <LMF>(xxx_MANUAL_FRONT)
    <LMF_PRODUCER>(DEC)
    <LMF_PRODUCT>(xxx)
    <LMF_RELEASE_DATE>(0)
    <LMF_VERSION_NUMBER>(0)
    <LMF_ALTNAME>(BOOKBROWSER)
    <ENDLMF>
    
    Move them out of the source file and put them in
    xxx$SRC:xxx_SYMBOLS.SDML. This leaves only one LMF-related tag in the
    source file, and - as far as I remember - DOCUMENT doesn't care where
    the <LMF_INFO> tag is in relation to the text, as long as it's in the
    source file somewhere. The parameter to this tag points to the block of
    LMF info in between the <LMF> and <ENDLMF> tags: so leave your coding
    as it is (without the comment tag, of course: <LMF_INFO>(xxx_MANUAL_FRONT)
    )
    
    No promises, but give it a try.
    
    b
4751.9The HTML version lacks LMF checks, so...XDELTA::HOFFMANSteve, OpenVMS EngineeringFri May 16 1997 14:485
   I decided the Bookreader version of the manual did not require any
   LMF-based protection, and -- as should be obvious -- I simply removed
   the <LMF> tags that were causing me all the problems.