Conference vaxuum::online_bookbuilding

    I've got mine right at the top of the file (before the title). Do
    you have the <define_book_name> tag before the <lmf> tag? I would
    assume that you have to define the argument for the <lmf> tag before
    you use it. 
    
    			Alfred

<profile>

<LMF>(deex_user)
<LMF_PRODUCER>(DEC)
<LMF_PRODUCT>(DECISION-EXPERT)
<LMF_RELEASE_DATE>(0)
<LMF_VERSION_NUMBER>(0)
<LMF_ALTNAME>(BOOKBROWSER)
<ENDLMF>

<set_online_topic>(head2)
                     
<element>(s1033front.sdml)
<element>(s1033c1.sdml)
<element>(s1033c2.sdml)
<element>(s1033c3.sdml)
<element>(s1033c4.sdml)
<element>(s1033c5.sdml)
<element>(s1033c6.sdml)
<element>(s1033c7.sdml)
<element>(s1033c8.sdml)
<element>(s1033c9.sdml)
<element>(s1033c10.sdml)
<element>(s1034gl.sdml)
<index_file>

<endprofile>

    Also, make sure you use a <reference> tag in the <title> tags:
    
    <title>(<reference>(book-symbol-name))
    
    The admonition about not putting anything in front of  the <title>
    tag refers only to text or tags that generate text. That results
    a bogus page 1 and confuses the converter. The LMF tags don't generate
    text.
    
    Mary

    Hi Mary,

    If you have done the right thing, and used the <DEFINE_BOOK_NAME> tag
    instead of the "generic" <DEFINE_SYMBOL> tag, your example in .3 will
    cause the title to be presented in italics. (At least it did last time
    I tried it.) Since I am a firm believer in not hacking because it
    causes too many headaches later on, I elected to remove my <REFERENCE>
    tags from the <TITLE> and just type out the book name.

    I believe that the <TITLE> tag should be able to override the italics,
    but until/unless that happens, what would you advise me to do to
    satisfy all parties/doc-types?

    Regards

    Richard

    Richard,
    
    <title>(<reference>(whatever)) has been working for quite a long
    time now for quite a few people (the VMS writers) so I have to
    believe this is a problem with your coding. It's actually the
    <reference> tag that overrides the italics, and the redef of
    the <reference> tag is part of the online tag defs and should 
    work there. To remove the italics from hardcopy builds, you
    need to reference a file that contains the redef so it is in
    force for hardcopy doctypes. (You don't specify if you are getting
    itals in hardcopy or online builds.) Use the following qualifier
    on the DOCUMENT command line:
    
    /SYMBOLS=DOC$LOCAL_FORMATS:CUP$ONLINE_DEFS.GDX
    
    If you are doing this and it doesn't solve the problem, please send
    me the SDML file for your front matter.
    
    Thanks,
    
    Mary

    
    Hi again,
    
    I'm still having the same problem I reported in .0, i.e. put the <lmf>
    tags before the <title> and the thing crashes.  Put them after, and it
    can't find them.  
    
    Here's my profile:
    
	<PROFILE>
	<set_online_topic>(head2)
	       
	<ELEMENT>(temp_front.sdml)
	<ELEMENT>(temp_c1.sdml)
	
	<ENDPROFILE>

    and here's the sdml code for my title page...
    
	<FRONT_MATTER>(CD_front)
	<define_book_name>(ug\ODA/CDA Gateway User's Guide)
	<TITLE_PAGE>
	<lmf>(ug)
	<lmf_producer>(DEC)
	<lmf_product>(ODA/CDA Gateway)
	<lmf_release_date>(0)
	<lmf_version_number>(0)
	<lmf_altname>(bookbrowser)
	<endlmf>
	<TITLE>(<reference>(ug))
	<ORDER_NUMBER>(XX--XXXXX--XX)
	<define>(gateway\ODA/CDA Gateway)
	<ABSTRACT>(July 1999)
	This guide describes how to use the <gateway> product. 
	<ENDABSTRACT>
	<REVISION_INFO>(This is a new manual.)
	<REVISION_INFO>(etc.)
	<ENDTITLE_PAGE>

    I'm using the 27-Nov kit, and this command line:
    
    $ doc pro online.hand bookreader/contents -
    _$ /symbols=doc$local_formats:cup$online_defs.gdx
    
    All goes well until the device conversion.  Then this happens:
    
    [ D e v i c e    C o n v e r s i o n ]...
    %DVC-I-IDENT, Online Device converter 2.0 Oct-6-1989
    %DVC-E-PAGECOORDLOST,  PAGE COORDINATION LOST TeXpage = 1, ChunkID =
    7954808
    
    %DVC-E-BOOKABORT, aborting run -- book 
    CUPP$:[HENRY.ODA.USER]PRO.DECW$BOOK not
    created
    -DVC-I-INPUTFILE, input file is:
       CUPP$:[HENRY.ODA.USER]PRO.DVI_BOOKREADER
    -DVC-I-ONPAGE, on page [1]
    
    I'd be grateful if some kind soul could figure this out and tell me
    what I'm doing wrong.
    
    Thanks,
    Frank.
    
    

    
    Re .6,
    
    I forgot to say that I tried putting the <lmf> tags in the profile as
    suggested in .2, and got the page coordination lost error. 
    
    F.

    Make sure you are using the qualifier:
    
    /symbols=doc$local_formats:cup$online_defs.gdx
    
    when you process your file.
    
    Let me know if you have any further problems.
    
    Thanks,
    
    Mary

    Mary,
    
    I've been using /sym=doc$local_formats:cup$online_defs.gdx and it still
    doesn't work.  

    I've appended a .LIS file of the proceedings.  If it might help to see
    the source files,  everything is in 

    HNGOVR::PUBU$:[HENRY.ONLINE]

    I'd sure love to know what I'm doing wrong...

    Thanks,
    
    Frank.

    

%DOC-I-IDENT, VAX Document V1.2-A   2-JUN-1989 16:15:56.35
[ T a g    T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT,  Tag Translator V1.2-004
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-LCL_MSG01, Using online bookbuilding tools, 27-October-1989 baselevel
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-FILEWRTOK, File TEMP_FRONT.TEX written
%TAG-I-FILEWRTOK, File TEMP_C1.TEX written
[ T e x t    F o r m a t t i n g ]...
%TEX-I-INFO, loading online doctype design file, TEX$V2HANDBOOK - on page [1]
%TEX-I-PAGETOOSHORT, Page too short - on page [7]
%TEX-I-PAGESOUT, 17 pages written.
-TEX-I-OUTFILENAME, 'PUBU$:[HENRY.ONLINE]PRO.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-INFO, loading online doctype design file, TEX$V2HANDBOOK - on page [1]
%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME, 'PUBU$:[HENRY.ONLINE]PRO_CONTENTS.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
%DVC-I-IDENT, Online Device converter 2.0 Oct-6-1989
%DVC-E-PAGECOORDLOST,  PAGE COORDINATION LOST TeXpage = 1, ChunkID = 7954808
 
%DVC-E-BOOKABORT, aborting run -- book  PUBU$:[HENRY.ONLINE]PRO.DECW$BOOK
-DVC-I-INPUTFILE, input file is: 
   PUBU$:[HENRY.ONLINE]PRO.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [1] 
 


DOCUMENT /LIST/PRINT=NOTIFY PRO ONLINE.HAND BOOKREADER/CONTENTS/SYM=DOC$LOCAL_FORMATS:CUP$ONLINE_DEFS.GDX/NOPRINT
Date/Time: 21-DEC-1989 11:33:08.59
CPU time: 33.79 secs.
    

    Frank,
    
    I copied over your files and had the same results you did. It turns
    out that there's a bug in the LMF tags that doesn't do the right thing
    with the slash in ODA/CDA and that's what's causing the problem. The
    good news is that it's fixed in V1.2B: your files processed perfectly,
    just as you'd coded them, on our development baselevel.
    
    So, you're not doing anything wrong and your problems should be solved
    when you upgrade to V1.2B of VAX DOCUMENT (due out in the next week
    or so; it will be announced in this notex conference as well as the
    DOCUMENT notes conference).
    
    Thanks,
    
    Mary

    Mary,
    
    That's great.  Thanks a lot for your help.
    
    Happy New Year!
    
    Frank.

    RE .4: Richard,
    
    The problem is the <keep> tag in your <title> tag. You have coded
    your file thus:
    
    <define_symbol>(hyperapplication\Hyperapplication)
    <define_book_name>(memex_users_guide\<reference>(hyperapplication)
    User's Guide)
    <title>(<keep>(<reference>(memex_users_guide)))
    
    The overriding of the italics works by the <reference> tag checking to
    see if it is inside a <title> tag. In this case, however, it sees that
    it is inside a <keep> tag so it says, ok, I'll do italics.
    
    If you remove the <keep> tag, your title page will have no italics.
    
    We already know that some changes/inprovements need to be made to the
    <title> tag, so I'll add this case to the list for consideration for
    some future version. 
    
    You are using <keep> to force the whole title to be on one line, right?
    This may not be a good idea, in that it may look fine on the hardcopy
    title page but not on the **narrower** online window where the title
    might run off the right margin and be partically obscured. I think this
    tag usage might fall in the category of "tags that generate specific
    formatting effects must be used with care..." (Section 2.7 of Coding
    Documentation Source Files for the DECwindows Bookreader). Like <line>,
    you should use <keep> only when you actually want a line to break (or
    not break) for **all** destinations.
    
    Looking at the VAX DOCUMENT User's Guide, Vol 1, your usage of <keep>
    seems to be somewhat outside the scope intended for <keep>. It is
    intended to keep a string of text -- phrase that should be considered a
    single unit (say, VAX-11  or VAX DOCUMENT) from hyphenating. One
    example might be:
    
    <define_symbol>(document\<keep>(VAX DOCUMENT))
    <define_book_name>(user_guide\<reference>(document) User's Guide))
    <title>(<reference>(user_guide))
    
    This coding works fine (no italics).
    
    Mary

    RE: .10
    
    Mary, what's the workaround for this?  V1.2-B is still  not available,
    and we have large docsets to prepare by the end of January.  We're
    encountering the same exact problem as Frank.  What do we do?
    
    
    Susan

I've been getting a Warning that there's no LMF info for my book.  The LMF tags
are in my front matter file:

<front_matter>(front_CHAP) 
<include>(vms_booknames)

<LMF>(ode_guide)
<LMF_PRODUCER>(DEC)
<LMF_PRODUCT>(OPS5)
<LMF_RELEASE_DATE>(0)
<LMF_VERSION_NUMBER>(3.0)
<LMF_ALTNAME>(BOOKBROWSER)
<ENDLMF>

<TITLE_PAGE> 
<order_number>(AA--MI65A--TE) 
<product>(VAX OPS5)
<title>(<reference>(ode_guide))
...
<endpreface>
<endfront_matter>


I put <DEFINE_BOOK_NAME>(ode_guide\Development Environment User's Guide)
into the vms_booknames file.  My log file says:

%TAG-W-LCL_MSG13, tag <TAG_DIAGNOSTIC>, line 1, file
   LISPW$1:[CARRASCO.OPS5_ODE.TEMP]S1080PRO.SDML;
   No LMF information is specified for this document.


Aside from this Warning, the book builds OK and can be read.  Must I move
the LMF tags to the profile?  If so, where do I put the <DEFINE_BOOK_NAME>?  
We don't use a symbol file.  Or can I (she said hopefully) just ignore 
the Warning?


Pilar.

    We also cannot build all our books with LMF info (but we can build
    some of them!).  Has anyone else encountered LMF problems on only
    certain books?  
    
    Here's some mail summarizing our efforts to diagnose the problem:
    
From:	REORG::JALBERT      "Insanity is hereditary, you get it from your kids, of course I don't have any so I don't know where I got mine from" 25-JAN-1990 09:46:42.64
To:	VAXUUM::UTT,SEARLE,GREMBOWICZ,AXTELL
CC:	JALBERT
Subj:	Problem building with LMF information

Hi Mary,

We have a strange problem here with building our books for online with
the LMF information. We have built 12 books for the Rdb/VMS docset and
out of those 12 we have 4 that are giving a warning saying No LMF information
is specified for this document. Pam Axtell has built 3 of her books for
the DBMS docset and all 3 of those are giving the error message that
there is no LMF info. I put the LMF information in the LP_BOOKNAMES file
like was suggested. We use the <product> tag and the <title> tag so
we coded the files with conditions so we could put the <reference> tag
inside the <title> tag. I sent one of the front matter files from one
of the books that wasn't recognizing the LMF info to Sheila and she built
it on DONVAN v1.2 of DOCUMENT and it worked fine. We are including in the
booknames file the CUP$ONLINE_DEFS.GDX file. We did notice that our version
was dated October 27, 1989 and that the one on DONVAN was dated December 10, 1989. We copied the December 10 one from DONVAN and tried building again and
still got the warning. Have you heard of anyone else having problems like
this? Could it possibly be that we don't have the correct versions of some
of the files in the kit? We have to make the March CDROM and we have to
have the books done by next week. Do you have any ideas on this? It's stumping
us over here, and it's getting frustrating. 

Thanks!

Sally

From:	STAR::KRAETSCH     26-JAN-1990 08:49:04.42
To:	WAYNE,MIKEF,MARY
CC:	KIRK,REORG::ROGOFF,UPDATE::JALBERT
Subj:	lmf problems on reorg

Notice in the attached bookinfo output that the symbolic name is the name of
the .sdml file, NOT the book symbol.  The VWI routines init the symbol to the
file name and change it to the symbolic name when called by the DVC.
Obviously, this call is not being made in this case.  I would suggest testing
the build with a shorter symbol name to see if the problem disappears.  I seem
to remember from the meeting yesterday that the books that had this problem
also had the truncated symbol warnings from the <counter> tag.  Perhaps these
warnings are not always harmless?  

joe

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

From:	UPDATE::JALBERT      "Insanity is hereditary, you get it from your kids, of course I don't have any so I don't know where I got mine from" 25-JAN-1990 17:40:18.99
To:	CLOSET::UTT,CLOSET::FITZELL,STAR::KRAETSCH,SEARLE,ROGOFF
CC:	JALBERT
Subj:	I ran BOOKINFO on one of the books that isn't giving the LMF information. this is the result. 

UPDATE> bookinfo [rdbdoc.v31.rdo]aa-n039f-te

 Title:           "VAX Rdb/VMS RDO and RMU Reference Manual"
 Symbolic Name:   "RDO_PRO"
 Build Date:      23-JAN-1990 23:26:22.31
 Structure Level: 2.0

 LMF Information
   Product Name:  ""
   Producer:      ""
   Date:          none
   Version:       0

 Book contains the following directories:
   Contents
   Figures
   Tables
   Index

From:	REORG::JALBERT      "Insanity is hereditary, you get it from your kids, of course I don't have any so I don't know where I got mine from" 26-JAN-1990 09:03:18.36
To:	SEARLE,ROGOFF
CC:	
Subj:	I sent this reply to Mary

From:	REORG::JALBERT      "Insanity is hereditary, you get it from your kids, of course I don't have any so I don't know where I got mine from" 26-JAN-1990 09:01:11.17
To:	CLOSET::UTT
CC:	JALBERT
Subj:	RE: bookinfo info

OK. We did comment out the names of the books giving the <counter> error
and it still didn't work. Could it possibly be the device converter that
we have? We have had many new versions in the last few months because of
other sporadic problems we've been having. The reason I say this is that
we were having a problem with one of our books here not building all the
way. It would get to the device converter and bomb. Barry had sent you
this problem. It was adding a K onto the end of the dvi_bookreader filename?
He was able to run it through the device converter alone though and it
worked. Well, before he ran it through the device converter it was showing
know LMF info when I did a BoOKINFO on it. After he ran it through the device
converter when I ran BoOKINFO on it the LMF information showed up. What
do you think about this theory? I can't think of anything else, I've been
racking my brain since last week on this. I will send you a .log file
of one of the builds that didn't work and give you the list of books not
working.

The ones not getting the LMF info are:

The Rdb/VMS Release Notes
The Rdb/VMS RDO and RMU Reference Manual
The Rdb/VMS SQL Reference Manual
The Rdb/VMS Guide to Using SQL/Services.

The next message I send will be a .log file

Sally
    

    RE: .14. The problem with Pilar Carrasco's files was solved offline:
    She had omitted the inclusion of DOC$LOCAL_FORMATS:CUP$ONLINE_DEFS.GDX.
    Once she did that, she had no further problems with the LMF tags (at
    least none that she's reported yet...)
    
    Apologies for not posting this solution earlier.
    
    Mary

    RE: .16. Whooops! Correction -- I believe that Pilar had the wrong
    version of CUP$ONLINE_DEFS.GDX. In any case, the problem had a simple
    solution.
    
    (The folks on REORG *do* have the correct version of
    CUP$ONLINE_DEFS.GDX -- it's all most mysterious...)
    
    Mary

    RE .15:
    
    I've heard via mail today that the problems the REORG folks were
    encountering were due to a miscoded symbols file. With a corrected
    version of the file, they have been able to build all their books
    *with* the LMF information.
    
    Mary

    The problem in .15 turned out to be an out-of-date version of the
    VMS_BOOKNAMES symbols files many groups use.
    
    We don't know what specifically in the old file caused the problem,
    just that finding and copying a new version to our cluster caused
    the prolem to go away.
    
    So, if you are using VMS_BOOKNAMES symbols file, be aware that an
    old version can somehow keep LMF info from processing correctly.
    
    Kirk

    Hi,
    
    We just installed Version 1-2B. I am getting the same warning message
    as in 240.14 that says there is no LMF info in my book.
    In Version 1-2B, is says remove all references to CUP$ONLINE_DEFS.GDX.
    
    The following is my front matter coding.
    
<FRONT_MATTER>(title_pg)

<TITLE_PAGE>

<define_book_name>(callable\Callable Routines Reference Manual)
<product>(VAX DSM)

<lmf>(callable)
<lmf_producer>(DEC)
<lmf_product>(DSM)
<lmf_release_date>(0)
<lmf_version_number>(0)
<lmf_altname>(BOOKBROWSER)
<endlmf>

<TITLE>( <keep>(<reference>(callable)) )

<ORDER_NUMBER>(AA--PBK0A--TE)
<ABSTRACT>(July 1990)
This document describes the VAX DSM callable interface, which allows routines
written in software languages that run layered on the VMS operating system
to access the DSM database and interpreter.
<ENDABSTRACT>
<REVISION_INFO>(Revision/Update Information:\This is a new document.)
<REVISION_INFO>(Operating System and Version:\VMS Version 5.2 and higher)
<REVISION_INFO>(Software Version:\VAX DSM Version 6.0)
<ENDTITLE_PAGE>(digital equipment corporation<line>maynard, massachusetts)

    
    Any suggestions.
    
    Ruth-Ellen
    
    ps. I am also getting a TEX error... it is looking for
    SDMVOILA.FMT_MACRO IN [TEX.FORMATS]. I have removed all of the
    references to online in DOC$DESIGNS.DAT in DOC$LOCAL_FORMATS. I don't 
    have an logicals pointing to DOC$VOILA... either. This problem is being
    looked at. 

    RE: .20
    
    See 240.12 for Mary's answer.
    
    Wayne

    See 277.1 for a possible answer on the SDMLVOILA thing.
    
    Mark

    Hi,
    
    Yes, the <keep> tag is what caused the problem with the LMF
    information.
    
    I also solved the SDMLVOILA thing. You have DOC$DESIGNS.DAT and
    DOC$DESTINATIONS.DAT in DOC$LOCAL_FORMATS and DOC$LOCAL_STANDARDS.
    You have to get rid of the online references in DOC$LOCAL_FORMATS.
    I edited the DOC$DESTINATIONS.DAT file in DOC$LOCAL_STANDARDS to 
    begin with and still had a DOC$DESTINATIONS.DAT in DOC$LOCAL_FORMATS that 
    was pointing to the old VOILA.
    
    Works okay now.
    
    Ruth-Ellen

>    I also solved the SDMLVOILA thing. You have DOC$DESIGNS.DAT and
>    DOC$DESTINATIONS.DAT in DOC$LOCAL_FORMATS and DOC$LOCAL_STANDARDS.
>    You have to get rid of the online references in DOC$LOCAL_FORMATS.
>    I edited the DOC$DESTINATIONS.DAT file in DOC$LOCAL_STANDARDS to 
>    begin with and still had a DOC$DESTINATIONS.DAT in DOC$LOCAL_FORMATS that 
>    was pointing to the old VOILA.
    
    Note that 240.22 points to 277.1 (on the same topic), and that points
    to CLOSET::DOCUMENT 2737.2, which contains a list of *all* the things
    you should take out of DOC$LOCAL_FORMATS (if you still have them left
    from various old-time kits, workarounds, etc.) after installing V1.2-B.
    
    240.23 points out the first thing that gets in your way when you use
    the online bookbuilding tools.  But please see that someone on your
    system checks 2737.2 to avoid the same sort of problems in SDMLHELP 
    if you're moving from V1.1 directly to V1.2-B.
    
    Mark

    
    After reading all 23 responses to the initiator of this note, I
    still do not know why I'm getting "No LMF information is specified
    for this document".  I have the LMF tags in the frontmatter before
    the <title> tag and after the <titlepage> tag.  I would like to
    include the file right in this note but I'm afraid I don't know
    how to do that.  I have the vax-document notes in front of me but
    I can't find anything on how to include a file.
    
    We are still running V1.2a.  
    
    Diane
    
    
    

    Diane,
    
    Send me the file and I will try it out.
    
    Thanks,
    
    Mary

    For everyones information, I sent Mary the file and she found the
    problem.  I did not have the reference tag inside the <title> tag.
    Obvious mistake on my part.  
    
    Thank-you Mary, for your quick turn-around time.  I appreciate it.
    
    Diane