[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

98.0. "Enhancement needed to for conditions?" by COOKIE::JOHNSTON () Thu Mar 12 1987 15:27

No error is received when using <cond> in a source but failing to use 
<set_condition> or \condition to process the file.  All related 
conditions show up in final output.  Consider this input sans any 
<set_condition> or \condition:


<FIGURE>(Four Parts Of The Performance Model\model_fig)
<condition>(ln3)
<FIGURE_FILE>(ln03\model_fig.six\24)
<endcondition>
<condition>(lno)
<FIGURE_SPACE>(24\Pix of Performance Model)
<endcondition>
<ENDFIGURE>



The final output prints two figure captions with rules.  The sixel file 
is not included in final output.

T.RTitleUserPersonal
Name
DateLines
98.1SuggestionsVAXUUM::KOHLBRENNERThu Mar 12 1987 16:3232
    1. We don't want to issue an error message if you have
       <condition> tags in your file, but have not supplied
       a <set_condition> tag or a /CONDITION qualifier.  Some
       users want to use only one condition-name and either
       set it (with <set_condition> or /CONDITION=) or not
       set it (that is, do nothing).
    
       THe example that you gave implies that you would always
       want to have either LN3 or LNO set, so for you, not maving
       one or the other condition-name set would be an "error".
       We haven't built the condition-name facility to recognize
       that kind of "error."    
    
       THere are lots of suggestions for enhancements to condition-names,
       so we'd better add this to the list.
    
    2. Getting either of the conditionalized sections in your output
       when you have not set any condition-names is a puzzle, though.
       I would investigate two things:
    
       Look in a /SYMBOLS file or some other included file for one
       or more <set_condition> tags.
    
       If you are doing something in the way of a local doctype
       or using the logical TAG$LOCAL_TAGS to define your own tags,
       be sure that you have not supplied a definition for <condition>.
    
       I cannot reproduce the problem here. If I conditionalize something
       it disappears from the output unless I explicitly set the condition.
    
    bill
    
98.2Does this syntax work ?UKOSC::BRUNNOCKAndy Brunnock - Greyhound ManFri Mar 13 1987 16:1420
    Its probably because DOCUMENT sees <FIGURE> first before the condition.
    The <CONDITION> flag would then be ignored within the context set
    by <FIGURE>.
    
    Try this syntax instead :
    
    
    <condition>(ln3)
    <FIGURE>(Four Parts Of The Performance Model\model_fig)
    <FIGURE_FILE>(ln03\model_fig.six\24)
    <ENDFIGURE>
    <endcondition>

    <condition>(lno)
    <FIGURE>(Four Parts Of The Performance Model\model_fig)
    <FIGURE_SPACE>(24\Pix of Performance Model)
    <ENDFIGURE>
    <endcondition>
    
    Andy (guessing)
98.3Lazy wretch that I am...COOKIE::JOHNSTONFri Mar 13 1987 21:149
re: .2

For me, not ideal because it's redundant.  Think I'll concentrate on 
toilet-training myself better.

Thanx for the suggestion, anyway.  


Rose
98.4use <figure_file> betterCLOSET::ANKLAMSun Mar 15 1987 13:4622
    
    I'd like to know which doctype produced two captions. Here, using
    S.R, I get a caption and a 4-pica space between rules, but the caption
    is set only once. What happened, effectively, is that the <figure>
    and <endfigure> tags were processed, but since no condition was
    set, neither the <figure_file> nor the <figure_space> tag was
    processed. (<endfigure> just puts space out by default if there's
    nothing in the figure.)
    
    However, what Rose is trying to do is much better handled taking
    advantage of options provided by <FIGURE_FILE>, which was designed
    with precisely what she is doing in mind:
    
    <figure>(caption)
    <figure_file>(LN03\filename.six\24)
    <figure_file>(LN01\space\24\this is text for the space)
    <endfigure>
    
    This requires no use of conditionals at all. 
    
    patti anklam
    
98.5I missed the obvious...COOKIE::JOHNSTONMon Mar 16 1987 11:5612
Why is the obvious never so obvious to me (do others have this problem)?

Thanx for pointing out the non-benefit of using conditionals in my 
particular case.  

I'll try recreating the problem in 98.0 and will send you the file.
I was using soft.spec.

Thanx

Rose

98.6<FIGURE_FILE> nogo for LN01COOKIE::JOHNSTONMon Mar 16 1987 13:4662
Patti, I tried using <FIGURE_FILE> instead of <CONDITION>, as you suggested.
It worked fine for line printer output, but not for ln01.  I tried it two
different ways, using \Space as you showed in your example and as explained
in the release notes; and simply replacing the file name with an explanation
as shown in the User's Guide:

Example 1
---------

<FIGURE>(Four Parts Of The Performance Model\perf_model_fig)
<FIGURE_FILE>(ln03\perf_model_fig.six\24)
<FIGURE_FILE>(ln01\Space\24\Paste performance model here)
<FIGURE_FILE>(line_printer\Space\24\Paste performance model here)
<ENDFIGURE>

Example 2
---------

<FIGURE>(Four Parts Of The Performance Model\perf_model_fig)
<FIGURE_FILE>(ln03\perf_model_fig.six\24)
<FIGURE_FILE>(ln01\Paste performance model here\24)
<FIGURE_FILE>(line_printer\Paste performance model here\24)
<ENDFIGURE>


An empty .lno file was created.  A single blank page is output.
The message, by the way, sent with ln01 output is (notice the *LN03* message
and font file not found): 

[ D e v i c e  C o n v e r s i o n ]...

This is DVItype, Version 2.6, with LN03 Version 0.92

Topp 1.90
No such file:triub14
Unable to read font file triub14
[P r i n t i n g  F i l e]...

The .lis file shows:

Missing character: There is no ["B5] in font palaci10!
[1-1] [1-2] [1-3]
%TEX-I-PAGESOUT, 3 pages written.


I looked through the release notes, using the index as my guide, and couldn't 
find anything that indicated LN01 wouldn't work in this case.


Does this look like our font pointers are messed up?  Or is it a DOCUMENT
problem?

We are running 06 and 07 here.  I double-checked, and I did process the file
under 07.


Thanx

Rose

P.S.  Couldn't recreate the two caption problem.  I'll try to do better about
keeping the old files around awhile after I've corrected a problem.
98.7CLOSET::ADLERMon Mar 16 1987 18:193
Do you have LN01 support installed under BL07?

--Brian
98.8Sys. Mgr says he installed itCOOKIE::JOHNSTONMon Mar 16 1987 19:0012
I checked with the system manager who installed it.  He said "yes", and
he showed me a hard copy of the install procedure wherein he installed printer
support three different times, one each for lineprinter, ln01, and ln03.

Again, we have 06 and 07 running with baselevels.com, if that makes a difference
or can help us track this down.


What should we check next?

Thanx

98.9did you get the TLN files?CLOSET::ANKLAMTue Mar 17 1987 17:0016
    
    Sorry it took me so long to think of this, but I was thinking so
    hard about the conditionals and the figure files, the real problem
    didn't jump out at me.
    
    If the system manager installed support for the LN01, he/she must
    also have requested the *fonts*. The message from the driver indicates
    that the fonts are not there. To check for yourself, do:
    
    $ DIR DOC$LN01_FONTS:*.TLN
    
    if there are no files there, tell the system manager to send MAIL
    to CLOSET::LN01FONTS for instructions
    
    patti