[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

247.0. "<FOOTNOTE> problem within <LIST>s" by CHEST::ALFORD (Ice to see you.....) Wed Jan 03 1990 15:32

    I am hoping that one of the TEX experts reads this Conference, because
    I have a sneaking suspicion that that sort of knowledge could be useful
    for my problem !

    I have this *very* large (60 .sdml files) book which is compiling
    through, creating the TEX files, Contents, Index, including all the
    files and figures it needs and then it gets a VOILA ERROR...

    I am using VMS V5.1, DOCUMENT V1.1 with the command line :-

document/contents/index/cond=book MSTH_V31_PROFILE online.reference bookreader



VOILA ERROR--The following symbols are undefined:
        pgid = 109, offset =  81044, symbol = '_DECW_HEADFN_DDAG_1_17'
%DVC-E-OUTPUTFAIL, error writing to output file
-DVC-I-INPUTFILE, input file is: 
$28$DUA61:[ALFORD.MSTH]MSTH_V31_PROFILE.DVI_BOOKREADER;
-DVC-I-ONPAGE, on page [4] <CR><LF>
%DVC-E-BOOKABORT, aborting run -- book not created

    The symbol '_DECW_HEADFN_DDAG_1_17' is created by DOCUMENT as the 
    reference to a <FOOTNOTE>

    The footnote is embedded in a nested <LIST>


<LIST>(UNNUMBERED)
<LE>....
<LE>....
<LE>....
   <LIST>(UNNUMBERED)
   <LE>....
   <LE>Phase Review Process<footnote>(ddag\Be aware that it should be replaced
       by the Business Software Project Methodology Reference Manual Q2/Q3
       FY90) 
   <ENDLIST>
<LE>....
<LE>....
<ENDLIST>

    This footnote works perfectly well for all but BOOKREADER output formats. 
    Is there a quirk with the online format that can't cope with a <FOOTNOTE>
    inside a nested <LIST> ? 

    As far as I can tell, the reference to the footnote is being created, but
    the footnote itself is not. 

    I can provide both the .SDML and the .TEX file for examination, both of
    which are far too long to post here. 
    
T.RTitleUserPersonal
Name
DateLines
247.1should be in headerVAXUUM::UTTWed Jan 03 1990 17:0021
    Would you send me the .SDML file? (*NOT* all 60 .SDML files -- pare it
    down to something short (<100 lines, preferably) that reproduces the
    problem.)
    
    No one has previously reported problems with footnotes in lists and I
    can't think of any reason off the top of my head why there should be
    any. The undefined symbol message actually indicates that the footnote
    is in a <headn> tag, not in text, and that it's the first footnote in a
    <headn> tag (could also be <chapter>, <appendix>, or <title>), and that
    is uses (obviously) a double dagger. Do you have a footnote that
    matches this description? If so, make sure that it is coded properly:
    
    <headn>(Header text<footref>(ddag)\sym)
    <footnote_text>(ddag\footnote text.)
    
    But you never know with footnotes...sigh, so send me a file if none
    of the above helps.
    
    Thanks,
    
    Mary
247.2time to upgrade?VAXUUM::UTTWed Jan 03 1990 17:078
    I just noticed that you are using DOCUMENT 1.1 (what version of the
    online tools?). Your best course of action might be to upgrade to
    DOCUMENT 1.2 and the latest online tools. (See note 244 for info
    about the about-to-be-released Writer's Toolkit.) Even if this turns
    out to be a bug in the current tools, I would not be able to give you
    a fix for the baselevel you are running.
    
    Mary
247.3It works now !CHEST::ALFORDIce to see you.....Mon Jan 08 1990 07:4427
    Mary,
    
    your suggestion proved to be the start of the solution, thanks.
    
    There was a <head4><text<footref>(ddag)\ref_sym) in that segment of
    text.
    
    The combination was :-
    
    <head4>(<footref>(ddag)\)
    .
    <le><footnote>(ddag\)
    
    The problem was cured by putting in a <footnote_text> for the first
    <footref>(ddag) and  changing the <le><footnote> to a DAG version and
    the problem went away.
    
    <footnote_text>(ddag\)
    <head4>(<footref>(ddag)\)
    .
    <le><footnote>(dag\)
    
    Why the problem occured in the first place, I don't know, but I think a
    general solution with footnote problems would be to humour them :-)
    
    Jane.