Conference vaxuum::online_bookbuilding

53.0. "What page formatting is allowed in <code_example>?" by LISTNH::SIMONS (Al Simons 381-2187) Thu Dec 22 1988 11:35

In the REPORT doctype, the only one I am fairly familiar with, text within the 
<code_example> <endcode_example> tag pair seems to be represented as it appears
in the source file. DOCUMENT and TEX seem to keep their hands off.

In the ONLINE doctype, my code examples are getting, well, "adjusted". It may
be my error, but I thought I'd ask. The sample below has two anomolies in it
when compiled for ONLINE.

        1) The line after the THEN ("!+") is moved up to the THEN line, and
           a blank line inserted below it.
        2) The long line containing a "-" (minus) wraps making the variable
           named "yet_another_one" appear at the left side of the code
           example. In a large body of code, this makes it very hard to read.

If this is, indeed, the intended behavior, how can I prevent it from wrapping.
I don't want to make it very short in the source, because then the hardcopy
output looks silly.

Thanks for any assistance,
-Al

****************

<front_matter>
<title_page>
<title>(Title text)
<endtitle_page>
<contents_file>
<endfront_matter>
<head1>(head1text\a)
<code_example>
IF some_boolean_is_true
THEN
    !+
    ! do a calculation that will wrap and give ugly output.
    !-
    a_long_variable_name = another_long_variable_name - yet_another_one;
END;
<endcode_example>

    I've been looking into this (a similar problem was reported to via
    MAIL with code examples in templates). Frankly, I am not sure why
    lines are breaking in examples (online only). The TeX macros are
    set up so that lines in this context will not break, ever. I will
    take it up with more knowledgeable TeX experts. Meanwhile, I have
    come up with a workaround which will be in the next baselevel of
    the bookbuilding tools (planned for later this month). 
    
    This problem seems to be very infrequent but if other people notice
    it (especially under the next baselevel), I would appreciate their
    reporting it under this note.
    
    Thanks,
    
    Mary