Contents

1  Quick Start

2  PDF Output Files

3  The T_EX Live CD

4  Public Domain T_EXware

5  Font Reconstitution and Metafiles

6  Windows 2000 Compatibility

7  Universal Modern Fonts

• For use with non-T_EX applications to create a graphic inserts, tables, or other items to be included in T_EX documents via the T_EX \special command.
• For producing documents with text having a "T_EX look", but using a non-T_EX application.

8  Increased Capacities

9  TIFF Image Library Hooks

10  Improved Installation and Un-Install for Windows

11  Enhanced Virtual Font Handling

• Nested virtual fonts are now recognized. Earlier releases would not recognize nested virtual fonts; only the first level of virtual character mapping would have an effect. This was not necessarily a limitation, since nested virtual font schemes can always be "flattened" into an equivalent single level, and single-level virtual fonts can be rendered much faster than nested ones. However, since certain packages (like L^AT_EX times) supply nested virtual fonts, and converting them to un-nested equivalents is difficult, direct support for nested virtual fonts is desirable.
• Actual font naming convention: Earlier releases used a non-standard convention that a virtual font, such as arial.vf, could map to a font of the same name (in this case, arial); it was implicit that the mapped-to font (arial) was the actual TrueType font and not a recursive reference to the virtual font arial.vf itself. This implicit convention is incompatible with support for nested virtual fonts, so the following convention now applies: A virtual font may map to a font name which includes a parenthesized suffix, and this will force the previewer to treat that mapped-to font as an actual font of the same name, less the suffix. For example, if the virtual font arial.vf contains a mapped-to font reference of the form: (MAPFONT D 0 (FONTNAME arial (Actual))(COMMENT Arial TrueType in Windows)) then the font name "arial (Actual)" refers to the actual font named "arial"; the previewer will not attempt to find a nested virtual font of that name. In the old scheme no longer supported, arial.vf would have contained an apparently self-referencing mapped-to font of the form: (MAPFONT D 0 (FONTNAME arial)(COMMENT Arial TrueType in Windows))
  If you continue to use old virtual fonts with this obsolete convention, they will result in a warning message that arial.vf contains a circular self-reference; however the virtual font will still work correctly because the previewer will interrupt such circularity by converting the reference to an actual font reference.
  Recursive, self-referential virtual fonts, while not necessarily erroneous (see Knuth's example), are still not supported.
  In accord with this convention, the File Export Metrics function now names references to Windows fonts with "(Actual)" suffixed to the name. If you are creating virtual fonts by hand, you can use more specific suffixes as reminders of the actual font source, such as "(ATM)" for Adobe Type Manager. The previewer makes no use of the suffix; it is merely looking for the leading parenthesis as an actual-font indicator.
  Here is the precise rule used by the Previewer to detect names of actual fonts: If the font name referenced in a virtual font contains a left-parenthesis, the Previewer interprets the referenced font as an actual font with a name consisting of the referenced name truncated at the left-parenthesis. Thus the suffix "(Actual)" is not strictly required for you to indicate an actual font; any suffix with a left parenthesis will work, even a left parenthesis alone. Since TrueType and ATM font names do not use parentheses, this convention is orthogonally compatible with any system font names.
• New virtual fonts: DC fonts. A new set of virtual fonts provides access to the DC fonts using the Unicode rendering in the 32-bit previewer and the new naming convention for actual fonts. This provides correct rendering across all national versions of Windows 95 and Windows NT.
• New virtual fonts: times package. The L^AT_EX times package replaces the Computer Modern text fonts with the fonts Times (for Roman text), Helvetica (for sans serif text), and Courier (for typewriter text). These are implemented in the original package by three levels of nested virtual fonts, with the actual fonts being PostScript fonts rendered by the DVI-PostScript translator dvips. In TRUET_EX, we simply replace the lowest level of these virtual fonts with new virtual fonts resolving to the TrueType fonts Times New Roman, Arial, and Courier, with appropriate character code remapping. We assume that the multi-lingual extended character sets are available in these TrueType fonts, which is the default in Windows NT and available in Windows 95 when the Windows 95 "multilanguage extensions" (see the Windows 95 help for details) are installed. If the multilanguage extensions are not installed in Windows 95, or if you are running under Windows 3.1, many accented non-English characters will not render when using times. Note also that the multiple levels of virtual font nesting will noticeably slow preview rendering of documents using these fonts.
• New virtual fonts: MathTime package. The L^AT_EX mathtime package replaces the Computer Modern math fonts with the MathTime fonts, which are Type 1 fonts stylistically compatible with the Times text font. The MathTime fonts require Adobe Type Manager (ATM) version 3.01 running on Windows 95 (ATM is not available for Windows NT as of this writing). A set of virtual fonts for TRUET_EX maps the character sets properly so that the L^AT_EX output will render properly with the ATM font encodings. While the virtual fonts are freely available with TRUET_EX, the MathTime Type 1 font files and Adobe Type Manager are proprietary products available from other vendors.
• New encoding tables: Several new encoding tables are now included in the dialogs for the File Export Metrics function; these tables represent various Unicode encodings and the PSNFSS "8r" encoding.

12  Omega Support

12.1  Extensions for Omega

• The previewer interprets DVI files containing character codes larger than a single byte.
• The previewer loads 16-bit font metrics (Omega XFM or OFM files in addition to T_EX TFM files) and virtual fonts (Omega OVF or XVF format in addition to T_EX VF format).
• Virtual fonts can directly access and render all code positions in 16-bit Unicode fonts such as are available in Windows NT and Windows 95. This means you can use any national character or math symbol anywhere in a Unicode font.
• All extensions are upward compatible: the previewer still accepts the older TFM and VF files, as well as DVI files using the traditional single-byte encoding. The previewer will look first for an OFM or XFM file, and then a TFM file, when looking for a font metric file; and likewise for a OVF or XVF file, and then a VF file, when looking for a virtual font file.

12.2  Accessing Unicode Fonts

12.3  Sparse Font Optimization and Unicode Virtual Packets

13  Corrected and Updated Metric Export

13.1  Metric Export Formats Supported

13.2  Selecting Input and Output Encodings

13.3  Ligatures Supported

13.4  Getting Unicode Fonts in Windows

13.5  Limitations

C> \truetex\bin\ttf_edit arial.ttf font 3 1 afm > arial.afm

13.6  Making 8-Bit T_EX Fonts from Unicode Fonts

13.7  Using Adobe Type Manager (ATM) for Type 1 Fonts with Windows 95

14  Using the Windows Registry

14.1  Using the Registry for Font Substitution

14.2  Using the Registry for Preferences

15  Message Window

16  Enhanced Special-Handling in 32-bit Edition

16.1  Accessing Memory-Mapped Special-Texts

• To make pointer of proper type, your handler must first cast the pointer f (which has type "FILE *") to type "LPVOID".
• This pointer value points to the beginning of the DVI file, so you must add an offset of offset to (LPVOID)f to point to the start of the '134special text.
• The memory-mapped text is not null-terminated, as is the case for the parameter text. Handlers must take care to access the text from (LPVOID)f+offset to (LPVOID)f+offset+total_len-1 only, and must not rely on a null character termination for parsing.
• DVIGDI32.EXE passes this memory-mapped pointer only for lengthy '134special's. Typical '134special's are shorter than 1023 characters and will result in (LPVOID)f being NULL. This avoids the overhead of memory-mapping unless necessitated by the rendering of a lengthy '134special.
• The pointer is a read-only pointer. Attempting to write to a pointed-to location will result in a WIN32 virtual memory exception.
• Liquidation calls now always send a NULL f. Formerly this happened to be a valid FILE * stream pointer for the DVI file.
• Virtual fonts can themselves contain '134special's, and (unless lengthy) such '134special's are indistinguishable to the handler. In the case of a lengthy virtual font '134special, DVIGDI32.EXE will not memory-map the underlying virtual font file (that is, (LPVOID)f will always be NULL). That is, a lengthy '134special in a virtual font will result in a NULL value for f although text_len<total_len. This makes lengthy '134special's in virtual fonts accessible only in their first 1023 characters via the text parameter. The path and name in such cases refers to the DVI file, not the virtual font file, and thus is no help in locating the '134special text.
• Special handlers must not retain pointers to data or (in WIN16) file streams between calls. These pointers are temporary and will become invalid if, for example, the underlying DVI file is reformatted by another process.
• There is a slight possibility of a race condition should the underlying DVI file change (such as being reformatted by another application from the .tex file) while a special handler is rendering the text of a '134special. Memory-mapping tends to insulate the text from such races, although there is a slight possibility of a mixture of old and new text appearing in the same special region if the total text was longer than a WIN32 virtual memory page (for example, 4 KB in Windows 95). Handlers should therefore strive to handle garbaged texts gracefully, since an incomplete rendering in such circumstances is of no consequence. This avoids the need for a complex (and non-T_EX-standard) file-locking and synchronization mechanism between the T_EX formatter and previewer processes.
• On liquidation and closing calls the pointer "f" is now always NULL.

16.2  Messages from special handlers

17  Font Encoding Maps

18  Initial Window Sizing

19  Long File Names

20  DDE Server

20.1  DDE Commands Implemented

• [Open(command-line)] Opens DVI file previews and sets options based on the text of command-line. The command-line argument may contain one or more DVI file names (you may omit the extension .dvi, and TRUET_EX will automatically append it) and command-line options.
  TRUET_EX will interpret command-line in the same way as a command line given in a launch via the Windows Program Manager, Windows 95 Start arguments, or a WinExec() call. Exception: issuing a print command via DDE (that is, the -w option in an execute string) will not cause the previewer to automatically exit after printing, unlike the automatic exit which normally follows with a Start, Program Manager, or WinExec() launch for printing. Follow DDE printing command(s) with a DDE Exit when you want the previewer to exit.
  DDE client applications should specify file names in DDE execute strings as fully qualified paths, since there is no reliable way for clients to know the previewer's current directory. Names unqualified by a directory or qualified by a relative directory are potentially ambiguous.
  Although the Open command opens a document preview window in the previewer's MDI frame window, it will not bring the frame window to the top of the Windows desktop. Typically you will want to follow an Open with a Show or SetPos command to bring the document into view.
• [Show(SW-COMMAND )] Sets the "show state" of the previewer frame (outermost MDI) window using the Windows API ShowWindow() function. Each of the argument(s) should be a string giving a symbolic name of a show state for ShowWindow(). For example, "[Show(SW_SHOWMINIMIZED)]" will minimize the previewer.
  Since the previewer examines the DVI file for changes on each repaint (if the Re-Open DVI Files on Change preference item is enabled), you need not close a previewed document when re-formatting. Simply ensure a repaint with a Show command.
• [SetPos(hwndInsertAfter,x, y,cx,cy,fuFlags )] Changes the size, position, Z-order, activation, etc., of the previewer frame window using the Windows API SetWindowPos() function. The parameters are as described in the Windows documentation for SetWindowPos(), except that hwnd is implicitly the previewer MDI frame window. Specify hwndInsertAfter as the string NULL, as a string giving one of the symbolic values such as HWND_BOTTOM, or as a scanf()-recognizable decimal or hex integer value of a window handle. The coordinates x,y,cx,cy must likewise be scanf()-recognizable decimal or hex integers. The fuFlags parameter should be one or more of the SWP_... symbolic values, with multiple values joined with a | operator. For example, " [SetPos(HWND_TOP, 100, 100, 300, 300, SWP_SHOWWINDOW)] " moves the previewer to the top of the Z-order in a 300 × 300 window at coordinate (100,100) and causes the window to be shown.
• [Close(filename)] Closes the first DVI child window with a file name matching the supplied filename. If filename does not contain a directory, TRUET_EX will close the first child it finds with a matching name part; if filename is the empty string, then TRUET_EX will close the first DVI child window. If you supply a file name qualified by a relative or absolute directory, the directory and file name associated with the child window must be equivalent to the path you supplied when you originally opened the preview window; however, matching will treat upper and lower case as equivalent and backslashes equivalent to forward slashes. To avoid ambiguity, use the same fully-qualified, absolute path name for both opening and closing a document. You can interactively examine the directory and file name for a given DVI child window in the previewer by selecting the View Show DVI Info menu item. Unlike Open, you must supply the extension (.dvi) as part of filename, as it is not implicit.
• [Exit] Exits the previewer, unless printing is active. If any print job(s) are active, the previewer will not exit, but instead will display a message box that the print job(s) must finish (or be cancelled by the user) before exiting. There is currently no way for a DDE client to inquire of or receive notice of when TRUET_EX printing completes.

20.2  DDE Argument Syntax

20.3  DDE Service Enabling/Disabling

20.4  DDE Platform Interoperability

20.5  Programming a DDE Client

...
#include <dde.h>
...
HWND hServerWnd;                /* DDE server window                        */
...
/* We maintain a state variable to track the progress of a DDE execute      */
/* string conversation from initiation, to execution, to termination.       */
#define IDLE 1                  /* Idle, awaiting user input                */
#define INITIATING 2            /* Sent initiate, awaiting server ACK       */
#define EXECUTING 3             /* Sent execute, awaiting server ACK        */
#define TERMINATING 4           /* Got server's exec ACK, terminating       */
int ConversationState = IDLE;

    case WM_DDE_ACK:
            /* DDE server response.  The ACK for both the        */
            /* initiate and the execute arrive here, so we       */
            /* must take care to discriminate between them       */
            /* by examining the transaction state.               */

            /* The first ACK we might get is the server's        */
            /* response to our initiation.                       */
            if (ConversationState==INITIATING) {
                ConversationState = EXECUTING;
                hServerWnd = (HWND) wParam;
                DoDDE(
                        "[Open(\\\\kcc\\\\chk\\\\4192.dvi)]"
                        "[Open(\\\\kcc\\\\chk\\\\4196.dvi)]"
                        "[Open(\\\\kcc\\\\chk\\\\4197.dvi)]"
                        "[Open(\\\\kcc\\\\chk\\\\4198.dvi)]"
                    );
                ConversationState = TERMINATING;
                TermDDE();
                ConversationState = IDLE;
                }
            /* Otherwise we have the ACK for the execute;      */
            else if (ConversationState==EXECUTING) {
                /* Here we could examine the return status     */
                }
            /* This case is an error of synchronization        */
            else {
                }
            break;

void
IniDDE(void) {
    /* Initialize conversation with DDE server                 */
    ATOM app, topic;
    app = GlobalAddAtom("TrueTeX");
    topic = GlobalAddAtom("View");
    SendMessage(HWND_BROADCAST,WM_DDE_INITIATE,(WPARAM)hMainWnd,
            MAKELPARAM(app,topic));
    if (app) GlobalDeleteAtom(app);
    if (topic) GlobalDeleteAtom(topic);
    }

BOOL
DoDDE(char *cmds) {
    /* Send DDE commands to DDE server.  Return whether apparently */
    /* successful.                                                 */
    HGLOBAL hCmds;
    char FAR *p;
    if (hServerWnd==NULL) {
        MessageBox(hMainWnd,"Cannot connect to DDE server!",Title,MB_OK);
        return(FALSE);
        }
    hCmds = GlobalAlloc(GMEM_MOVEABLE|GMEM_DDESHARE,strlen(cmds)+1);
    if (hCmds==NULL) {
        MessageBox(hMainWnd,"No memory for DDE!",Title,MB_OK);
        return(FALSE);
        }
    p = GlobalLock(hCmds);
    if (p==NULL) {
        GlobalFree(hCmds);
        MessageBox(hMainWnd,"No memory for DDE!",Title,MB_OK);
        return(FALSE);
        }
    lstrcpy(p,cmds);
    GlobalUnlock(hCmds);  p = NULL;
    if (!PostMessage(hServerWnd,WM_DDE_EXECUTE,(WPARAM)hMainWnd,
#if _WIN16
            MAKELPARAM(0,hCmds)
#elif _WIN32
            (LPARAM)hCmds
#endif
            )) {
        GlobalFree(hCmds);
        MessageBox(hMainWnd,"Cannot connect to DDE server!",Title,MB_OK);
        }
    return(TRUE);
    }

void
TermDDE(void) {
    /* Terminate conversation with DDE server                      */
    if (hServerWnd==NULL) return;
    PostMessage(hServerWnd,WM_DDE_TERMINATE,(WPARAM)hMainWnd,0L);
    hServerWnd = NULL;
    }

21  Recursive Directory Searching

22  Using Multiple Configuration (.INI) Files

23  Initial Working Directory

24  Quiring

25  Virtual Fonts

26  T_EX Font Names

27  '134special Handler Sources

28  TEXWAKEUP Preference for initex3x.exe

29  Programming with the Setup Utility

29.1  How Setup Organizes Distribution Disks

29.2  Modifying Setup for Network-Master Installation

29.3  Setup command-line syntax

• -v: Toggles verbose mode, which is useful for debugging.
• -s: Toggles installation silent mode, which omits routine messages, and only displays messages when errors occur. Use with -f if you want absolutely no messages in the absence of errors; otherwise a target-directory selection dialog will still appear. Using -v will override -s. Silent mode does not affect un-installs very much; we feel that the user should know and confirm when things are being removed from his system.
• -q: Like -s silent mode, except for un-installation. Use with caution.
• -p name: Uses product name name in dialogs. Title bars in windows will show this, followed by "Setup" (or "Un-Install" if -u preceded). It will also be used as the "Start Menu" subdirectory for installation/un-install.
• -d dest: Uses dest as the default destination (target) directory for installation or un-installation. This is the initial value that will appear in the user dialog prompting for the target directory, or giving notice of a mandatory target directory, if the -f option is given, where the installation/un-installation will begin (the dialog or notice will not appear if -s is given). Not valid for 2nd pass invocation.
• -m manif: Uses manif as the starting manifest file name. This is valid during 1st or 2nd pass invocation or un-install. The 1st pass does not load the manifest, but will pass along the name in a -m argument to the 2nd pass invocation, where it will be loaded and used without further notice.
  You can specify more than one manifest file name by separating them with commas, such as "-m execs,fonts" specifying that files execs and fonts in the source (during install) or target (during un-install) directory will be used as starting manifests. Manifests can in turn call other manifests in a nested fashion; see the TRUET_EX "manifest" file comments for a description of the format.
  Note that Setup will compute a full path name of the manifest file which is the concatenation of the source directory with the manifest file name (default manifest or -m value) during an installation (that is, -u was not specified), or the destination directory (that is, -u was specified). To specify such a destination directory during un-installation, use -d, and perhaps -f.
  It is your responsibility as the setup media creator to make sure the manifest is present in the source directory on the installation media for installation files, and that the the installation manifest installs a suitable un-installation manifest into the target directory (assuming you want to provide an un-install feature).
  Manifest script files can direct Setup to install or un-install software with a number of actions, described fully in the TRUET_EX manifest file on TRUET_EX Setup Disk 1. Actions can create sub-directories of the target directory, make any of those directories the current working directory, execute programs from the source media (typically self-extracting archives), copy and remove files directly by name, stream-edit text files to replace placeholder strings with the target directory (useful for creating customized .INI files), send DDE commands to the Windows program manager to create and populate program groups in the Start Menu, and verify that the run-time environment is a proper version of Windows, and load other manifest files.
  Setup loads the entire manifest into memory from one or more manifest files and closes the files before starting to perform the manifest actions. Besides checking the syntax of the manifest, this permits the manifest files to originate on removable media volumes that are switched during the installation process.
• -f: The destination directory (default or -d destination) is fixed. The user will not be presented a dialog offering a chance to change the default. Not valid for 2nd pass invocation.
• -u: Un-installs: invokes an installation destination dialog, and uses file name manifest in the destination directory (or another manifest name relative to the destination with the -m option) to un-install files and fonts. You probably should use -d with this to specify where the application's un-install manifest resides, since the usual convention is to name the installation (not un-install) manifest with the name "manifest". Use -p, too, before the -u. Do not use source and destination arguments with the un-install option; the un-install invocation should contain only dashed options.
  An un-installation manifest may be unable to directly delete certain files, such as executables files that are running (the setup.exe program itself, for example) or fonts that have been opened and locked by the operating system. The un-install mode of Setup will schedule such files for deletion on the next system re-start, using either the Windows 95 WININIT method or the Windows NT MoveFileEx method, as is appropriate to the run-time environment.
  The reasonable expection of a user is that an application's un-install manifest is a "mirror image" of the installation. That is, the un-install manifest should list all the files and fonts that the installation originally created.
  It is not an error, nor will a message appear, if a file to be removed by a manifest is not present or a font to be unregistered is not registered. This allows you to create a global un-installation manifest that covers the whole application, even though you may only have installed part of it. You can also create manifests which will register and un-register sets of fonts in the Windows system, without altering the underlying TrueType font files.
  Un-install manifests should unregister fonts before removing the corresponding TrueType files. This order is not important in most situations, however, as the same result will exist after a system re-start.
  The un-install mode of Setup has no provision to remove directories. This means application directories, perhaps empty, will always remain despite un-installation. You should advise the user that he should examine the vestigial directories for any critical files that might remain (such as documents that might have been created in the TRUET_EX application directory tree), and that he should manually remove directories using the Windows Explorer or other method when he is satisfied that they are empty.
  Option -u is not valid in a 2nd-pass invocation.

29.4  Other Setup Programming Considerations

29.5  Examples of Using Setup

30  Other Network Issues

31  Character Composition in Exported Font Metrics

• Accent-plus-letter composition: for example, making an "Amacron" from a letter "A" plus an accent "macron". The script knows how to place the following accents, including skew for italic correction:

  Composable Accent Characters
  Name	Position	Example
  umlaut	top-center	ö
  acute	top-center	ó
  breve	top-center	o
  caron1	top-center	ô
  cedilla	bottom-center	o
  circumflex	top-center	ô
  comma	top-right	L'
  dieresis	top-center	ö
  dotaccent	top-center	\.o
  grave	top-center	ò
  hungarumlaut	top-center	ö
  macron	top-center	¯o
  ogonek2	bottom-right
  period	top-center	\.o
  ring2	top-center
  1For D/d/L/l, changes to comma at top-right.
  2Accent is not present in the Computer Modern
  fonts used in this portable document.
• Ligature-from-sequence composition: the script will compose ligatures from separate characters if the input font does not contain the ligated character: ff, fi, fl, ffi, ffl, IJ, ij, SS, Æ, æ, , and .
• Synonyms: the script will recognize variations on character names:

  hyphenchar	hyphen
  ng	eng
  Ng	Eng
  Uhungarumlaut	Udblacute
  uhungarumlaut	udblacute
  Ohungarumlaut	Odblacute
  ohungarumlaut	odblacute
  Zdotaccent	Zdot
  zdotaccent	zdot
  hyphenchar	hyphennobreak
  compwordmark	zeronobreakspace
  Idotaccent	Idot
  dbar	dmacron
  visiblespace	spaceliteral
  etc.
• Fallbacks: the script will substitute certain closely similar characters for missing accents, such as a period for a dotaccent.

31.1  Composition Language for Experts

add and array begin clear cos count currentdict cvi cvn cvr cvs cvx def dictstack dict div dup end eq exchf exec exit falsef forall getinterval get ge gt idiv ifelse iff index known length le lt mod mul neg not orf pop put readonly roll round sin stack storef string sub tanf truef vpl_literal vpl_set vpl_wd_ht_dp_ic where

32  COMMDLG.DLL Required

33  Win32s

34  Bugs Corrected

35  TrueT_EX Release Summary

36  Regarding Copyrights and Other Legal Matters

36.1   Copyright Notice

This distribution [of L^AT_EX macros] is Copyright 1993 1994 1995 1996 The L^AT_EX3 Project and the individual authors: Leslie Lamport, Johannes Braams, David Carlisle, Alan Jeffrey, Frank Mittelbach, Chris Rowley, Rainer Schoepf.

36.2  TIFF Library Copyright Notice

36.3  Info-Zip Disclaimer

37  Technical Support

Footnotes: