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

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

566.0. "<TAG> Use in <CODE_EXAMPLE> --> Bug" by DECWET::CUSTER () Fri Jun 26 1987 13:09

    I just ran into a strange occurrence using BL08 and the S.R doctype. I
    was trying to produce an example of SDML-coded text.  Here's the
    source code:

--------------------------------------------------------------------        
<P>For example, suppose you had the following text in a file called
PIGLET.SDML:

<CODE_EXAMPLE>

<tag>(P)The first chapter is devoted to explaining the
<tag>(newterm)(production cycle). The information is presented
specifically for the production of <tag>(newterm)(technical
documentation) and is intended to look at this task from the writer's
perspective.  The information is organized in a step-by-step fashion,
with each phase of the production cycle addressed separately.  A
<tag>(newterm)(flowchart) showing the workflow during each phase is
presented, with action required by the writer highlighted in bold
boxes.<footnote>(1\The <EMPHASIS>(Preliminary
DECwest Production and Illustration Guide), by Craig Kosak)

<ENDCODE_EXAMPLE> 
---------------------------------------------------------------------
    
    The output for this example is strange.  Every "<tag>(sdml-tag)"
    sequence that occurs as the first thing on a line is thrown to the left
    of the margin like this: 
    
<P>
    		The first chapter is devoted to explaining the 
<NEWTERM>
    		(production cycle).  The information is presented
    
    		.
    		.
    		.
    
    
    
    Is this expected behavior or a bug?  Anyone have any ideas for a
    fix?   (Note:  the "<tag>(sdml-tag)" sequences that do not appear
    at the beginning of a line in the input are properly output.)
    
    
    	-Helen
T.RTitleUserPersonal
Name		DateLines
566.1<literal>CLOSET::ANKLAMFri Jun 26 1987 13:2018
    
    Yes this was a bug that is fixed in V1.0. There is probably another
    side to this question, but I much prefer to show examples of
    tags using:
    
    <code_example><literal>
    <P>The first chapter is devoted to explaining the
    <newterm>(production cycle). The information is presented
    specifically for the production of <newterm>(technical
    ...
    <endliteral><endcode_example>
    
    Note that in V1.0, the output of doing it this way is exactly the
    same (i.e. the monospaced font) as doing it as Helen did. In all
    lower baselevels, the output of <tag> in a monospaced example was
    the same font/bolding as in normal text.
    
    -pa
566.2<INTERACTIVE> a little trickierDECWET::CUSTERFri Jun 26 1987 13:5143
    Thanks Patti, for the quick reply.  <LITERAL>/<ENDLITERAL> is a
    much simpler way to handle this case and I will recode.
    
    Unfortunately, I just also realized that <INTERACTIVE> examples
    have the same problem.  Here's a source:
    
------------------------------------------------------
<P>The following example demonstrates the GLOSSARY command line
used to create a glossary for PIGLET.SDML and displays the new
glossary file.

<CALLOUTS>
<INTERACTIVE>
<S>($) <U>(GLOSSARY /TEXT=PIGLET)<CO>
<S>(The following new terms appeared more than once in your text file(s):)<CO>
<S>(---------------------------------------------------------------------)
<S>([End of list])
<S>($) <U>(TYPE PIGLET_GLOSSARY.SDML)<CO>
<S>(<TAG>(GLOSSARY))
<S>(<TAG>(GTERM)(flowchart))
<S>(<TAG>(GDEF)())
<S>( )
<S>(<TAG>(GTERM)(production cycle))
<S>(<TAG>(GDEF)())
<S>( )
<S>(<TAG>(GTERM)(technical documentation))
<S>(<TAG>(GDEF)())
<S>( )
<S>(<TAG>(ENDGLOSSARY))

<ENDINTERACTIVE>
<ENDCALLOUTS>
------------------------------------------------------------
    
    I'm wondering how and if <LITERAL> works in this context.  Perhaps
    I need to replace each <TAG> tag with a literal tag like this:
    
       <S>(<LITERAL>(<GDEF>)())
    
    I'll give it a try.  
    
    	-Helen
566.3yes it isCLOSET::ANKLAMFri Jun 26 1987 14:5311
    
    Yes, you'd have to use <literal> inside each <s>() and <u>() tag.
    I hadn't thought of that. 
    
    btw, the <tag> tag was fixed for V1.0 so you can give it up to 8
    additional arguments, <TAG>(LIST\UNNUMBERED\-) produces
    
    <LIST>(UNNUMBERED\-)
    
    Only the first argument is forced to uppercase.