Conference vaxuum::document_ft

>1. Can someone tell me how I can use normal typewriter face in the
>   middle of some text (e.g. to refer to parts of filespecs etc)
>   like "the good 'ol TeX" did it: 
>
>    bla blah blah {\tt en dit is wat ik wil} blah blah
    
    Try using:
    
    bla blah blah <CODE_EXAMPLE>(en dit is wat ik wil) blah blah


>3. Since Garamond is a Digital standard in most of Europe, are we
>   going to get that too in future?

    I thought this was already an available LPS40 module.  If so, you
    need to create a local doctype that pulls in those fonts.


>4. Now that I started using/modifying some document types to suit
>   our needs or to resemble existing styles, I feel there is a need
>   for two more manuals (as if it wasn't enough already):
>
>    a. A variant of the TeXbook as the DOCUMENTbook, containing
>       definitions and usage of the \documentcommands used everywhere.
>       This is needed since it doesn't resemble TeX very much
>
>    b. A translation list telling me into what <TAG>s are translated into
>       \DOCUMENTcommands. (rather than finding out by doing DOCU/NOTEX).

    There was mention of a doctype designer guide, and I think it is
    a planned document.  For internal use, maybe just providing the
    TeX format files and .GDX files in source form would be adequate
    for initial users, although something describing what you've asked
    for would be nice.

    
    -tl

    Sorry, but Garamond is not one of the standard Digital PostScript
    fonts -- and the standard Digital PostScript fonts are all we use
    for LPS40 and LN03R support (except for the math characters, which
    come from the TeX AM fonts).
    
    There is a lively discussion among groups that make document-creation
    tools and the TBU, which is the official DEC font supplier, as to
    which fonts ought to be in our standard bag for all kinds of editing,
    formatting, and printing applications, as well as for online
    documentation of various flavors on various platforms.  The "standard"
    that specifies Garamond has been brought up in that context.
    Stay tuned for further developments.
    
    Incidentally, I read in some unofficial forum that the "standard"
    really only applies to sales literature.  If there is any truth
    to that rumor at all -- is sales literature the limit of the
    official influence of the "Corporate Identity Committee", or is
    that the only group that chose to observe the standard so far?

    FYI: The Electronic Publishing Interest Committee has shown an
    increased awareness of the Corporate Identity Committee and its
    publishing standards, so you'll find a growing pressure on Digital
    font-makers to make Garamond available (or to change the standard,
    I suppose).
    
    Mark

    re .1, and <code_example>(code text)
    
    That's part 1. Next you'll need to modify your local doctype
    to use one of the monospace fonts for \codexampleintextfont.
    Most of the standard designs just use \tenit for a code fragment
    embedded in text. Assuming your body text is ten point or so,
    you can use \ninepointmono, or you can use the same size as
    \codexamplefont.
    
    Lee

RE: .1

The Doctype Designers Guide is part of the external V1.0 docset, but it's
not what you want. We do have plans to write an "internals" book which will
not be part of the external docset and which will include the info you've
requested. Work on that book will commence once the V1.0 docset is completed.

--Brian