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

Conference vaxuum::online_bookbuilding

Title:Online Bookbuilding
Notice:This conference is write-locked: see note 1.3.
Moderator:VAXUUM::UTT
Created:Fri Aug 12 1988
Last Modified:Mon Jul 15 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:440
Total number of notes:2134

263.0. "<LMF> requires just one <REF> in <TITLE>?" by CASEE::THOMSON (Richard Thomson) Wed Jan 17 1990 10:31

    Hi guys

    A quick <LMF> question: I can understand why it is necessary for the
    <TITLE> to contain the <REF...> to the <DEF_BOOK_SYM>, but why is it
    necessary for it to contain *only* that reference?

    For example, I use a separate <REF> for my Version number, and this
    causes a warning to be issued.

    (You may be getting the picture by now that this week's task is to get
    rid of all the warning messages that have been accumulating in our book
    builds 8^).

    Regards

    Richard
T.RTitleUserPersonal
Name		DateLines
263.1beats me...CLOSET::UTTWed Jan 17 1990 18:206
    Post or send me an example of your coding and I'll take a look at it.
    
    Thanks,
    
    Mary
263.2Example code...CASEE::THOMSONRichard ThomsonThu Jan 18 1990 08:0726
    I think this should (not) work:
    
    <DEFINE_SYMBOL>(document_status\)
    
    <DEFINE_BOOK_NAME>(lmf_hypersession_ui_spec\User Interface Specification
            for
            <REFERENCE>(hypersession) <REFERENCE>(memex_version_number))

        <LMF>(lmf_hypersession_ui_spec)
        <LMF_PRODUCER>(DEC)
        <LMF_PRODUCT>(VAX-[tbs])
        <LMF_RELEASE_DATE>(0)
        <LMF_VERSION_NUMBER>(0)
        <LMF_ALTNAME>(BOOKBROWSER)
    
    <FRONT_MATTER>
    <TITLE_PAGE>

    <TITLE>( <REFERENCE>(document_status) <REFERENCE>(lmf_hypersession_ui_spec))

    <ENDTITLE_PAGE>
    <ENDFRONT_MATTER>

    Thanks

    Richard
263.3for now, only one <ref> in <title>CLOSET::UTTMon Jan 22 1990 15:3033
    Richard,
    
    Well, this was interesting. First off, you are missing an <ENDLMF>
    tag at the end of your <LMF> block.
    
    Secondly, it actually does work the way you have it coded, even though
    you get a message about the LMF tags missing. That message refers to
    the <reference> tag that is *not* the book symbol name (in this case,
    document_status). The <reference> tag for the actual book symbol
    (lmf_hypersession_ui_spec) pulls in the LMF info and all is well --
    the LMF information will be in the book header.
    
    The problem here is that the LMF tags are not smart enough to know
    which is the actual symbol name and which is just some text expansion
    stuff, like document-status. Both symbol names end up being passed
    to the converter as the book symbol name. The converter uses the
    last symbol name it receives as the book symbol name. In this case,
    it was the actual symbol name and the correct info showed up in the
    header. Had you reversed the order of the <reference> tags in your
    <title> tag, the document_status symbol would have (incorrectly)
    showed up in the book header as the book symbol.
    
    So, I think that with a little tinkering with the LMF tags to be a
    little smarter, we can allow more than one <reference> tag in the
    <title> tag. It won't happen for DOCUMENT 1.2B, but it's on the
    wishlist.
    
    For now, given that the results of more than one <reference> tag in
    the <title> tag can be flaky, try to stick to only one.
    
    Thanks,
    
    Mary
263.4At least it's not my fault!CASEE::THOMSONRichard ThomsonWed Jan 24 1990 09:1415
    Hi Mary,

    Thanks muchly for the investigation. I am glad to report that I do have
    the <ENDLMF> tag in my real code, but it was carelessly left out of the
    example.

    We have got round the problem by defining a special title symbol for
    LMF that is only used in the <TITLE> tag. The "vin ordinaire" symbol
    definition is used everywhere else.

    Another good reason to look forward to V1.2C!

    Thanks again

    Richard