| > Processing using cup.online
> There are two code examples here. Neither one wrap, but the last
one causes the error message box.
>The reason the LMF tags are commented out is because they hang
bookreader.
<comment>
<CONDITION>(bookreader)
<lmf>(book_reader)
<lmf_producer>(ESDP)
<lmf_product>(VAX SLS)
<lmf_release_date>(0)
<lmf_version_number>(0)
<lmf_altname>(bookbrowser)
<endlmf>
<endcondition>
<endcomment>
<DEFINE_BOOK_NAME>(BOOK_READER\VAX SLS Operator Manual)
<INCLUDE>(DOC$LOCAL_FORMATS:SIGHT_DEFS.GDF)
<FRONT_MATTER>(fm)
<TITLE_PAGE>
<TITLE>(<reference>(book_reader))
<ENDTITLE_PAGE>
<CONTENTS_FILE>
<ENDFRONT_MATTER>
<P>
The following example shows an OPCOM request message.
<CONDITION>(bookreader)
<online_popup>(example)
<code_example>(wide)
<ENDCONDITION>
<CONDITION>(postscript)
<CODE_EXAMPLE>
<ENDCONDITION>
<CALLOUTS>
<EMPHASIS>(
%%%%%%%%%%%%% OPCOM, dd-mmm-yyyy hh:mm:ss.cc <callout> %%%%%%%%%%%%%
request [request-id] <callout> from user USERNAME <callout>
_terminal_name:, <callout> "message-text" <callout>
\bold)
<ENDCALLOUTS>
<endcode_example>
<CONDITION>(bookreader)
<endonline_popup>
<ENDCONDITION>
<P>
<underline>(Example:) LOAD request message
<CONDITION>(bookreader)
<online_popup>(example)
<CODE_EXAMPLE>(Wide)
<ENDCONDITION>
<CONDITION>(postscript)
<CODE_EXAMPLE>
<ENDCONDITION>
<EMPHASIS>(
%%%%%%%% OPCOM, 26-JAN-1982 08:58:30.30, message from user SYSTEM %%%%%%%%
JOB 6703, Starting Restore for user HILL
.
.
%%%%%%%% OPCOM, 26-JAN-1982 08:58:57.30 %%%%%%%%
Request 87, from user SYSTEM
Load LMC4 on _MUA0: write enabled
Req by: SYSTEM on TXA5:
Owned by: HILL
Location: HEADQUARTERS
\BOLD)
<ENDCODE_EXAMPLE>
<CONDITION>(bookreader)
<endonline_popup>
<ENDCONDITION>
|
| The problem is the <emphasis>(...\bold) around your code examples. For
some reason, the online code example macros do not allow the lines to
break when code examples are bold faced.
What's the reason? I don't know, but I don't think it's a bug.
The design you are using uses the normal weight monospaced font for
code examples: you are trying to bypass that design to force bold
facing, making your code examples inconsistent with code examples in
other documents of the same design. If there is some reason why your
set of documents *must* have boldfaced code examples, you should use a
modified design, one in which the code example font is defined as the
boldfaced monspaced font. (Easy to do.) This is standard VAX DOCUMENT
philosophy: individual users do not control formatting.
A particular problem here is that the manner in which bold facing is
done in code examples is intended only for occasional use on occasional
words. You are not getting the boldfaced monospaced font: you are
getting overstriking. The Postscript output, while it has the correct
line breaks, is smeary looking.
You couldn't know this: I only just discovered it by delving into the
(shudder) TeXbook. It's called 'poor man's bold' and comes with all
sorts of warnings about why it shouldn't be used: 'The results are
somewhat fuzzy, and they are certainly no match for the real thing if
it's available; but poor man's bold is better than nothing, and once in
a while you can get away with it.' This is a reasonable way to do
things when the design was never intended to use boldface (but there
may, once in a great while, be a need for it).
So, I recommend removing the <emphasis> tags from your code examples
for both hardcopy and online output.
Mary
|