Conference vaxuum::document_ft

         
         There is a tag called <keep>, the argument to this tag
         is any word that you don't want to have hyphenated.  It
         takes the form of 
         
         <keep>(DONT.HYPHENATE_THIS$WORD)
         
         Chris

    Since, stylistically, I loathe hyphenation, I put the following
    command at the top of every file:
    
    <INCLUDE_TEX_FILE>(NO_HYPHEN.TEX)
    
    and NO_HYPHEN.TEX contains:
    
\pretolerance=100000
    
    Regards,
    BobW

    I'm afraid neither replies .1 nor .2 really answer the original
    question. If you have 10-20 user-defined symbol names per page 
    it is simply not feasible to enclose them all in <KEEP> tags.
    While avoiding all hyphenation makes a bad situation worse.
    (Sorry guys.)
    
    I believe the questions are:
    
    1)  Is there a way to turn off hyphenation at underscores?
    
    2)  Is there a way to turn off hyphenation at embedded periods?
    
    --Andrew

    
    Andrew is (as usual) correct. We have two ways of controlling the
    hyphenation of words with underscores and slash characters (/).
    Providing special processing when a word has an embedded period
    is something we hadn't yet considered.
    
    Here's the way these are handled.
    
    1. By default, DOCUMENT treats underscore characters and slashes
       the same way that it treats explicit hyphens in a word. If a
       line contains a long string with a lot of _ or / in it, TeX
       will break any line following the _ or the /, but will not 
       introduce a hyphen character to show continuation. This was
       an intentional design decision based on our original specs.
    
    2. This behavior can be overridden in a DESIGN file, if this
       behavior is inappropriate for a specific type of document.
       The following should be put in the DESIGN file:
    
       \def\_{\underscore}
       \def\slash{/}
    
       These could also be put in the DOC$LOCAL_ELEMENTS file to make
       the change system-wide.
    
    3. There is also a way to 'trap' a certain set of specific names
       and keep them from being hyphenated. This method involves the
       TAG$$LOCAL_STRINGS file. (This is not documented for customers;
       the interface is tricky and error-prone.) We have used this in
       previous versions of DOCUMENT and it is still in use in some
       places.
    
       After the tag translator finishes translating the tags in a file,
       but before the text formatter runs, a post-translate routine
       is invoked. This program fixes up special characters and makes
       sure that the text formatter is handed 'clean' text. It also
       looks for a file with the logical name TAG$$LOCAL_STRINGS. If
       this logical is defined, it is assumed to be a file that contains
       a set of strings to be translated and their outputs.
    
       If you look in DOC$LOCAL_FORMATS:CUP$LOCAL_STRINGS.TXT, you will
       see the list of product names that we look for and handle. In
       that file, you see things like:
    
       'MACRO-11'	'\:{MACRO--11}'		/* MACRO-11 */
    
       This input/output/comment sequence is read in during
       post-translation. Any occurrence of MACRO-11 (with a hyphen)
       is translated so the hyphen is an en-dash (which looks better)
       and it uses the shorthand \:{ } to put a hbox around it, so it
       will never be split across lines.
    
    
    I hope that this helps enough to solve some of the problems in .0.
    
    
    patti 

    Thanks Patti. That definitely helps.
    
    --Andrew