Conference vaxuum::online_bookbuilding

Donna,
	I'm not sure about the first problem you describe.  Could you give me 
small sample .SDML file that demonstrates the problem?  I'll try to reproduce 
it here.
	As far as your second problem, it's fixed with the latest release of 
bookbuilding tools.  See Note 64.9 in this conference.  If you're using a
baselevel prior to 4-August-1989, you need to update.
	After updating your bookbuilding tools, try running the files through
again.  The latest baselevel may even fix both problems.  If you're still
having problems, let me know and I'll check it out for you.  

Wayne

    Turns out the latest baselevel was installed on our system on August
    4th and the books in question were built prior to or on that date.
    We're rebuilding them.  I'll let you know if the first problem is
    corrected.  
    
    Thank you
    donna

    Wayne,
    
    Turns out we're still expriencing the odd line breaks.  The latest
    baselevel was installed on our system on 8/4. I sent you mail pointing
    you to files that show this behavior.
    
    donna
    

    The poor line breaks are due to TeX's difficulty in formatting lines
    and paragraphs with very long, unbreakable text in them, for example,
    KER$ENTER_KERNEL_CONTEXT and ELN$PHYSICAL_ADDRESS. I believe that the
    solution to this problem is to allow the text to break at the
    underscores and am taking this up with the TeX gurus in our group.
    Unfortunately, I can't predict at this time when a solution might be
    available.
    
    Thanks,
    
    Mary

    Would <HYPHENATE>(KER$ENTER_\KERNEL_\CONTEXT) help?
    

    Sure, but it would be *very* painful to go through a whole book and
    add <hyphenate> tags!
    
    Mary

    Painful? Yes. 
    
    The <hyphenate> tag would be a "work around," which means it:
    
    	1. Would add more work.
    
    	2. Likely would have to be undone in the future.
    	
    	3. May meet current, pressing needs.
    

I am still seeing this problem with lines breaking short when there is
a long word after them that isn't breaking. Any more news on this problem?

Sally    

    This was a DOCUMENT bug that was fixed in V1.2B. What version of
    DOCUMENT are you using, and what doctype(s) exhibit this behavior?
    Are you using any symbol files that contain tag definitions that may
    be outdated?
    
    Mary

Hi Mary,

We are using V1.2B of DOCUMENT, ONLINE.HANDBOOK is the doctype we used.
We use the LP_BOOKNAMES, VMS_BOOKNAMES symbols file and the book itself
has a symbols file. We have removed the CUP$ONLINE_DEFS.GDX (can't remember
if this is the name, but whatever file it was that was needed in V1.2A)
file from any local symbols file. The file is in USER2:[JALBERT.BOOK]
and is named AA-GQ93H-TE.DECW$BOOK. If you copy this file from that area
it is part of the bookshelf you just copied from my area. It's the Rdb/VMS
Release Notes. It occurs in 2 places, Section 3.11.29 under Solution 2,
second -- in the list, and in Section 3.11.50 the first line.

Thanks!

Sally

    I copied Sally's files and narrowed the problem down to the following
    lines:
    
<subhead1>(VAX Format)

<CODE_EXAMPLE>
SQLSRV$SQLCA_SQLERRD associate_id ,sqlerrd_array
<ENDCODE_EXAMPLE>

<head2>(RDML/EPascal Ignores /LINKAGE=PROGRAM_SECTION 
Qualifier\54_RDMLEPascalIgnoresLINKAGEPR) 
<p>                                                                
RDML/EPascal ignores the /LINKAGE=PROGRAM_SECTION qualifier.  RDML/EPascal
only supports the /LINKAGE=GLOBAL_VARIABLE mechanism for linking multiple
modules.  

    The 'problem' is an obscure one and it's not even clear that it's a bug
    or a real problem. I talked to our friendly local TeX guru and learned
    that this occurs because \codexample (in the .tex file) saves the 
    previous paragraph's formatting attributes, in this case, those of the
    head, which are restored after the code example ends; thus, text after
    the code example has the attributes of the previous head (which are
    different from paragraph text).
    
    Putting a <p> and text after the header and before the <code_example>
    will correct the problem (just a <p> will correct the problem). It's
    not really good form to code a head with no text that follows; in this
    particular case, the constuction was used to show a statement format,
    something for which there are specific template tags. Since there are
    more correct ways to code the information, I am reluctant to call
    this a DOCUMENT bug.
                                                               
    Mary