[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

816.0. "No 8-bit characters with TERMINAL destination" by RTOADC::CAAHANS (Hans Bachner, ADG Munich) Tue Aug 18 1987 04:31

    I found that MCS-characters (esp. �, �, ...) disappear when DCOUMENT
    is invoked with the TERMINAL destination. Although DOCUMENT tries
    to replace them with a 'best match' (like a for �, ss for �, ...),
    this is not the expected behaviour, as there are lots of terminals
    capable of the multinational character set. So why not keep them
    in the text as are ?
    
    At least, the replacement should conform to the language rules, which
    (for German) means ae for �, Ae (or AE in uppercase text) for � etc.

    Hans.
T.RTitleUserPersonal
Name
DateLines
816.1/DEV=(multinational)CLOSET::SEGALTue Aug 18 1987 11:365
    To access 8-bit MCS characters for destinations which do not
    print them by default (TERMINAL, MAIL, LINE_PRINTER) use the
    /DEVICE=(multinational) qualifier to the DOCUMENT command.
                                                           
    Lee
816.2A work-around and an apologyWRONGO::PARMENTERDepuis maintenantTue Aug 18 1987 12:1148
    
    There is MCS support for the line-printer/terminal device-converter,
    but we forgot to give you any easy way to get at it.  What you must
    do is add one line to the entry for TERMINAL, MAIL, and LINE in
    DOC$STANDARD_FORMATS:DOC$DESTINATIONS.DAT.  The line should be as
    follows:   "parameter presence MULTINATIONAL_CHARACTER_SET" and
    should be put at the very bottom of the entry.  PLEASE BE VERY CAREFUL
    in doing this, because DOC$DESTINATIONS.DAT is a fragile file.
    Below is a sample entry, in the form you will want.
                                                                  
DESTINATION TERMINAL LPR -
 /dvi_filetype=.DVI_LINE -
 /exclude_action=(print) -
 /fonts_filetype=.LINE_FONTS -
 /format_file=SDMLLPR -
 /output_filetype=.TERM -
 /special_characters=TEX$LPCHARS
 parameter number HORIZONTAL_OFFSET
 parameter number VERTICAL_OFFSET
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter number NUMBER_OF_PAGES
 parameter number /value=2
 parameter presence MULTINATIONAL_CHARACTER_SET

                                              
    Once you have done this, you may type:
    
    DOCUMENT TEST S.R TERM/dev=multinational
    
    and get what you are after.
    
    
    The reason for the confusion arises from the fact that we must still
    support 7-bit terminals in the U.S.  We needed to provide the 7-bit
    terminals with a fall-back mechanism.  This mechanism is described
    in the DEC standards (# 169 I believe).  Unfortunately, we forgot
    to make it easy for our loyal Europeans to use the MCS they know
    and love.  Sorry for any confusion.
    
    
    David
    
    
    
    
    
    
816.3when will this be fixed?VIDEO::LASKOThere are no temporary workarounds...Mon Aug 24 1987 00:548
    Someone should do their homework on DEC STD 169: applications are
    required to support DEC Multinational, system ports are required
    to provide fallback mechanisms: the versions of VMS that VAX Document
    is intended for (cf. SPD) all support sufficient fallback mechanisms
    to 7-bit ASCII (viz. $SET TERM/FALLBACK).
    
    DEC MCS should be the default for the device-converters in question,
    not ASCII-7.
816.4CLOSET::ADLERWed Sep 02 1987 16:311
We'll fix it in the next release.  --Brian