Novice Questions #2

[Colin Klipsch]

Greetings.

Here are some more questions from this Lout novice.  Again, I
apologize if these are obvious or if I've overlooked a relevant
section in the documentation.


(1) The @Sym function provides access to all the glyphs of the
    PostScript Symbol font.  It would be nice to have a similar
    function for the Dingbats font, which Lout also makes available.
    I've been using the following definition, based on @Sym:

        def @Ding right x { {Dingbats Base} @Font x }

    However, this requires using cryptic octal codes instead of
    mnemonic names.  Am I missing something simpler?


(2) Is there an easy way to set up an _outlined_ font in Lout?  By
    that, I mean a font rendered in outline form, with hollow
    interiors.  This can be done in raw PostScript, verbosely, by
    cloning an existing font and changing the "PaintType" attribute in
    its dictionary.  Perhaps outlined fonts could be added to a future
    version of Lout?


(3) I'm arranging one of my documents in two-column landscape mode.
    Mostly it works fine, but the Table of Contents is still in
    single-column mode, and looks ridiculously wide.  Is there a way
    to have the TOC honor @ColumnNumber?  I see that there's an
    @IndexColumnNumber function, but no similar one for the Contents.


(4) I noticed the other day that Lout was hyphenating "MacOS" across a
    line break as "Ma-cOS", which has me looking for a fix.  I found
    the User Guide's discussion of "&-" for suggesting line break
    positions, but this seems to require that I add these two
    characters to every instance of the word in my document; either
    that, or perhaps define a new macro (@MacOS) incorporating the
    "&-" hyphen declaration, and then substitute the macro everywhere.

    Is there a way to teach Lout the proper hyphenation of a peculiar
    word?  I've looked through the files in the "hyph" directory, but
    I don't want to fiddle with the global definitions; I want only to
    supply hyphenation for words specific to my document.


Thanks in advance to anyone who replies.

-- Colin K.