DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download
Index: ┃ R T

⟦4c653da29⟧ TextFile

    Length: 2937 (0xb79)
    Types: TextFile
    Names: »RELEASE_NOTE«

Derivation

└─⟦5f3412b64⟧ Bits:30000745 8mm tape, Rational 1000, ENVIRONMENT 12_6_5 TOOLS 
    └─ ⟦91c658230⟧ »DATA« 
        └─⟦458657fb6⟧ 
            └─⟦a5bbbb819⟧ 
                └─⟦this⟧ 
└─⟦d10a02448⟧ Bits:30000409 8mm tape, Rational 1000, ENVIRONMENT, D_12_7_3
    └─ ⟦fc9b38f02⟧ »DATA« 
        └─⟦9b46a407a⟧ 
            └─⟦eec0a994f⟧ 
                └─⟦this⟧ 

TextFile


                       DOCUMENT_FORMATTER 10.7.12


Document_Formatter 10.7.12 contains some minor enhancements for the
Compose procedure.

Enhancements
------------

    1)  Two new imperative commands--~If_PostScript and ~If_Not_PostScript--
        were added. They allow conditional input that is or is not processed
        depending on the output device.
        
        ------------------------------------------------------------------
                COMMAND          |  POSTSCRIPT DEVICE  |    OTHER DEVICE
        -------------------------|---------------------|------------------        
        ~If_PostScript (Arg)     |  Arg is processed   |  Arg is discarded
                                 |                     |
        ~If_Not_PostScript (Arg) |  Arg is discarded   |  Arg is processed
        ------------------------------------------------------------------
        
        These commands can be useful when the same input file is used to
        generate output for PostScript laser printers and lineprinters or
        online use. For example:
        
            ~If_PostScript[~Picture(File=Beautiful_EPS_Graphic)]
            ~If_Not_PostScript[~Include(Crude_Stick_Figure)]
        
    2)  A new Boolean ~Setup option--Extra_Blank_At_End_Of_Sentence--was
        added. This option lets the user specify whether Compose, when
        in filling mode, should place one or two blanks at the end of a
        sentence. Compose assumes it has found the end of a sentence
        when it encounters a period, question mark, or exclamation mark
        followed by either the end of the input line or at least two
        blanks.
        
        When Extra_Blank_At_End_Of_Sentence is True (the default),
        Compose outputs two blanks at the end of each sentence. This is
        the way all previous releases of Compose worked.
        
        When Extra_Blank_At_End_Of_Sentence is False, Compose outputs one
        blank at the end of each sentence.
        
        An example follows. Note that Compose always outputs only one
        space after the first period because it is followed by only one
        blank. Compose cannot automatically expand this into two spaces
        because sometimes--for example: for Mr. Smith--that would be
        incorrect.
        
        INPUT:
            Sentence one. Sentence two.   Sentence three.
            Sentence four.
            
        OUTPUT when Extra_Blank_At_End_Of_Sentence is True:
            Sentence one. Sentence two.  Sentence three.  Sentence four.
        
        OUTPUT when Extra_Blank_At_End_Of_Sentence is False:
            Sentence one. Sentence two. Sentence three. Sentence four.

Fixes
-----

    None.

Installation
------------

Document_Formatter 10.7.12 can be used on Delta_1 and Delta_2 systems.
Document_Formatter 10.7.12 should not be used with revision 6.0 or
earlier releases of the Rational Design Facility.