% Y&Y TeX Manual --- plain TeX format release 2.1 % Copyright 2007 TeX Users Group. % You may freely use, modify and/or distribute this file. % Run with kerned Lucida fonts \immediate\write16{Format: \fmtname\space Version: \fmtversion} % \overfullrule=5pt % show justification problem areas \overfullrule=0pt % avoid ugliness in final output % \tolerance=800 % to avoid overfull box blocks ? \catcode`\@11 % make @ act as if it was a letter \newdimen\pc@ % define a new dimension for `pica' for efficiency \pc@12\p@ % a pica is 12 pt (\p@ is predefined in plain TeX) \hsize26\pc@ % horizontal size is 26 picas \vsize12\p@ % vertical page size \vsize41\vsize % is 41 picas (another way of doing this sort of thing) \advance\vsize\topskip % plus topskip amount % \voffset-2.5\pc@ % take out, vertical shift not needed with TWOUP % \hoffset-3\pc@ % take out, horizontal shift not needed with TWOUP \parskip\z@ % set paragraph skip to 0pt \parindent\pc@ % set paragraph indent to one pica % % Define fonts. % Originally: Minion for text, Syntax for heading, Memphis light for typewriter % Now: LucidaBright for text, LucidaSans for heading, and LucidaSansTypewriter % \font\tenrm=lbr at9.5\p@ % \font\tenrm=morg at10\p@ \font\sixrm=lbr at6.1\p@ % \font\sixrm=morg at6\p@ \font\sixbf=lbd at6.1\p@ % \font\sixrm=morg at6\p@ \font\sevenrm=lbr at6.9\p@ % \font\sevenrm=morg at7\p@ \scriptfont\z@\sevenrm \font\tenit=lbi at9.5\p@ % \font\tenit=moi at10\p@ \font\tenbf=lbd at9.5\p@ % \font\tenbf=mob at10\p@ \font\tensc=lbrsc at9.5\p@ % \font\tensc=mosc at10\p@ \font\tendsc=lbdsc at9.5\p@ % \font\tensc=mosc at10\p@ \font\tensl=lbsl at9.5\p@ \font\eightsl=lbsl at7\p@ % fir slanted LaTeX \font\titlef=lsd at16\p@ % \font\titlef=sxb at16\p@ \font\eighttitle=lsd at9.0\p@ % \font\eighttitle=sxb at9.6\p@ \font\sectfnt=lsd at10.6\p@ % \font\sectfnt=sxb at11\p@ \font\subsectfnt=lsd at9.5\p@ % \font\subsectfnt=sxb at10\p@ \font\sixsubsectfnt=lsd at6.1\p@ % \font\sixsubsectfnt=sxb at6\p@ \font\rhfnt=lsr at8.6\p@ % \font\rhfnt=sxr at9\p@ \font\rhfol=lsb at8.6\p@ % \font\rhfol=sxubl at9\p@ % \font\tentt=lbtnr at9.5\p@ % \font\tentt=meml at10\p@ \font\tentt=lstnr at9.5\p@ % \font\tentt=meml at10\p@ % \font\secttt=lbtnr at10.6\p@ % \font\secttt=meml at11\p@ % \font\secttt=lstnr at10.6\p@ % \font\secttt=meml at11\p@ \font\secttt=lstnb at10.6\p@ % \font\secttt=meml at11\p@ \font\cmsy=cmsy10 at 10\p@ % for AMS TeX and AMS LaTeX logos only \font\lbms=lbms at 9.5\p@ % for < and > in -b= etc \font\lbmi=lbmi at 9.5\p@ % for \varepsilon in LaTeX 2e, x, y \font\lbr=lbr at 9.5\p@ % for > % \font\lstr=lstr at 9.5\p@ % for > % \let\sc\tensc % short hand for smallcaps font \let\dsc\tendsc % short hand for bold smallcaps font \let\tt\tentt % short hand for typewriter fixed width font \tenrm % switch to ten point roman text font \baselineskip12\p@ % baseline skip is 12pt % \newwrite\toc % allocate new output stream called TOC \immediate\openout\toc\jobname.toc % open output stream file .toc \def\noindex#1{} \def\tocwrite#1{{\let\index\noindex\xdef\toctext{#1}}\xdef\writeit{\write\toc {\toctext\string{\noexpand\number\pageno\string}}}\writeit} \newcount\sectcnt % allocate new counter for sections \def\section#1{\removelastskip26\p@ plus3.9\p@ minus1.95\p@ \global\advance\sectcnt\@ne{\sectfnt\let\tt\secttt\setbox8\hbox{\the \sectcnt.\kern6\p@}\hangindent\wd8\noindent\box8#1\par}\afterheadtrue \everypar{\afterhead}\global\subsectcnt\z@\nobreak\markbothsame{\the \sectcnt.\ #1}\tocwrite{\string\tocsect{\the\sectcnt}{#1}}\nobreak \vskip13\p@ plus2.6\p@ minus1.3\p@} \def\markbothsame#1{\xdef\chapmark{{#1}}\mark{{#1}{#1}}} \def\chapmark{{}} \newcount\subsectcnt % allocate new counter for subsections \def\subsect#1{\removelastskip19.5\p@ plus3.25\p@ minus1.625\p@\global\advance \subsectcnt\@ne\global\subsubsectcnt\z@{\subsectfnt\let\sixrm\sixsubsectfnt \setbox8\hbox{\the\sectcnt.\the\subsectcnt\kern6\p@}\hangindent\wd8\noindent \box8#1\par}\afterheadtrue\everypar{\afterhead}\nobreak\markright{\the \sectcnt.\the\subsectcnt\ #1}\tocwrite{\string\tocsub{\the\sectcnt.\the \subsectcnt}{#1}}\nobreak\vskip6.5\p@ plus1.95\p@ minus.975\p@} \newcount\subsubsectcnt % allocate new counter for subsubsections \def\subsub#1{\removelastskip13\p@ plus2.6\p@ minus1.3\p@\global\advance \subsubsectcnt\@ne{\subsectfnt\let\sixrm\sixsubsectfnt\noindent\the \sectcnt.\the\subsectcnt.\the\subsubsectcnt\kern6\p@#1}\tocwrite{\string \tocsubsub{\the\sectcnt.\the\subsectcnt.\the\subsubsectcnt}{#1}}\quad \ignorespaces} % \def\markright#1{\expandafter\makerightmark\chapmark{#1}} \def\makerightmark#1#2{\mark{{#1}{#2}}} \def\rhhead{\ifodd\pageno\rightheadline\else\leftheadline\fi} \def\rightheadline{\line{\rhfnt\getrecto\botmark\hfil\rhfol\folio}} \def\getrecto{\expandafter\dogetrecto} \def\dogetrecto#1#2{#2} \def\getverso{\expandafter\dogetverso} \def\dogetverso#1#2{#1} \def\leftheadline{\line{\rhfol\folio\hfil\rhfnt\getverso\botmark}} % \headline{\ifnum\pageno>1\rhhead\else\hfil\fi} \headline{\ifnum\pageno>1\rhhead\else\hfil\fi} % \footline{\ifnum\pageno=\@ne\hfil{\rhfol\folio}\fi\hfil} \footline{\ifnum\pageno=\z@\hfil{\rhfol\folio}\fi\hfil} %% no footer % \newif\ifafterhead \def\afterhead{\doafterhead\global\everypar{}} \def\doafterhead{{\setbox\z@\lastbox}\global\afterheadfalse} \newskip\nextskip \def\simpleremove{\par\ifdim\lastskip=\z@\else\vskip-\lastskip\fi} \def\removelastskip{\par\afterassignment\rem@vel@stskip\nextskip=} \def\rem@vel@stskip{\ifdim\lastskip=\z@\else\doremoveskip\fi\vskip\nextskip} \def\doremoveskip{\ifdim\lastskip>\nextskip\nextskip\z@\else\vskip-\lastskip \fi} \newskip\egskip \def\afterendgroupskip{\par \global\egskip\lastskip\endgroup\afterassignment\removeegskip\nextskip=} \def\removeegskip{\ifdim\egskip=\z@\else\doremoveegskip\fi\vskip\nextskip} \def\doremoveegskip{\ifdim\egskip>\nextskip\nextskip\z@\else\vskip-\egskip\fi} % \newif\iffirstitem \newif\ifinnerlist \def\makelistdisplay{\whang\wd8\advance\whang\leftskip\leftskip\whang} \let\item\zxvqj \def\regbeginlist{\removelastskip6.5\p@ plus1.95\p@ minus.975\p@ \begingroup\firstitemtrue\let\beginlist\innerbeginlist} \def\innerbeginlist{\begingroup\let\itemskip\relax\let\Itemskip\relax\let \endlist\endinnerlist\innerlisttrue} \newcount\itemcount % allocate new counter for items \newskip\qrtrskip \qrtrskip\thr@@\p@ plus1.6\p@ minus.8\p@ \def\itemskip{\iffirstitem\global\firstitemfalse\else\removelastskip\qrtrskip \fi} \def\Itemskip{\iffirstitem\global\firstitemfalse\else\removelastskip\h@lfskip \fi} \def\@tem{\itemskip\advance\itemcount\@ne% \noindent\llap{\hbox to\whang{\hfil\hbox to\pc@{\eqthing\itemcount.\hfil}}}} % \def\bull{$\bullet$} % \chardef\bull=149 % bullet % \def\bull{{\lbms\char15}} % bullet \def\bull{{\lbms\char14}} % openbullet \def\b@tem{\itemskip\noindent\llap{\hbox to\whang{\hfil\raise\p@\hbox to\pc@ {\bull\hfil}}}} \newdimen\whang \def\llist{\beginlist\itemcount96\let\item\@tem\let\eqthing\char \setbox8\hbox{\kern\tw@\pc@}\makelistdisplay} \def\nlist{\beginlist\itemcount\z@\let\item\@tem\let\eqthing\number \setbox8\hbox{\kern\tw@\pc@}\makelistdisplay} \def\blist{\beginlist\let\item\b@tem\setbox8\hbox{\kern\tw@\pc@}% \makelistdisplay} \def\ulist{\beginlist\let\item\u@tem\setbox8\hbox{\kern\tw@\pc@}% \makelistdisplay} \def\u@tem{\noindent\kern-\tw@\pc@} \def\endlist{\simpleremove\global\let\beginlist\regbeginlist \afterendgroupskip6.5\p@ plus1.95\p@ minus.975\p@} \def\endinnerlist{\endgraf\nextskip\lastskip\ifdim\nextskip=\z@\else\vskip- \nextskip\aftergroup\vskip\aftergroup\nextskip\fi\global\let\beginlist \regbeginlist\endgroup} \let\beginlist\regbeginlist % \chardef\other12 % \other will be used for \catcode 12 \def\ttverbatim{\begingroup\ttv \obeyspaces \obeylines} \def\ttv{% % make `less', `greater', and `backslash' active to translate char code \catcode`\<\active \catcode`\>\active % maybe just make these act like \other instead ? % make {, }, $, &, #, %, ~, _, ^ act like \other, not their normal meaning \catcode`\{=\other \catcode`\}=\other \catcode`\$=\other \catcode`\&=\other \catcode`\#=\other \catcode`\%=\other \catcode`\~=\other \catcode`\_=\other \catcode`\^ \other \tt \catcode`\\=\active} % \def\oddcharbackslash{\char"9D\relax} % char 157 for `backslash' \def\oddcharbackslash{\char92\relax} % char 92 for `backslash' % \def\oddchargreat{\char"9C\relax} % char 156 for `greater' \def\oddchargreat{\char62\relax} % char 62 for `greater' % \def\oddcharless{\char"98\relax} % char 60 for `less' \def\oddcharless{\char60\relax} % char 152 for `less' % need to play a game to do the following, since \ is redefined by \ttv % let char 219 act as escape (ala \) in place of \ % also set up active definitions for <, >, \ \bgroup \catcode`\Û\z@ \ttv ÛglobalÛlet\Ûoddcharbackslash ÛglobalÛlet>Ûoddchargreat ÛglobalÛlet<Ûoddcharless Ûegroup {\obeyspaces\gdef {\ }} \outer\def\begintt{$$\let\par=\endgraf \ttverbatim \parskip=\z@pt \catcode`\Û=\z@ \ttfinish} {\catcode`\Û\z@\catcode`Û\\otherÛobeylinesÛgdefÛttfinish#1^^M#2\endtt{#1Ûvbox% {#2}Ûendgroup$$}} \catcode`\Û\active {\obeylines\gdefÛ{\ttverbatim\let^^M=\ \letÛ=\endgroup}} \def\beginlines{\par\goodbreak\vskip6.5\p@ plus1.95\p@ minus.975\p@\nobreak \begingroup\parskip\z@\everypar{\vrule height9.20833\p@ depth3.79167\p@ width\z@}\rightskip\z@ plus\thr@@ em\leftskip\pc@\parindent\z@\obeylines} \def\endlines{\par\endgroup\vskip6.5\p@ plus1.95\p@ minus.975\p@} % % define various logos % \def\yandy{Y\hbox to.35\p@{\hss\sixrm\&\hss}Y} \def\yandyBold{Y\hbox to.35\p@{\hss\sixbf\&\hss}Y} \def\LaTeX{{L\kern-.36em\raise.3ex\hbox{\sc a}\kern-.15emT\kern-.1667em\lower .7ex\hbox{E}\kern-.125emX}} \def\LaTeXSlanted{{L\kern-.26em\raise.3ex\hbox{\eightsl A}\kern-.15emT\kern-.1667em\lower .7ex\hbox{E}\kern-.125emX}} \def\LaTeXBold{{L\kern-.3em\raise.3ex\hbox{\dsc a}\kern-.15emT\kern-.1667em\lower .7ex\hbox{E}\kern-.125emX}} % \def\LaTeXe{\LaTeX\kern.15em2${}_{\textstyle\varepsilon}$} % \def\LaTeXe{\LaTeX\kern.15em2{\lbmi \char34}} \def\LaTeXe{\LaTeX} % \def\LaTeXeBold{\LaTeXBold\kern.15em2{\lbmi \char34}} \def\LaTeXeBold{\LaTeXBold} \def\SliTeX{S{\sc li}{\TeX}} \def\AMS{{\cmsy A\kern-.1667em\lower.5ex\hbox{M}\kern-.125emS}} % \def\AmSTeX{{\the\textfont\cmsyfam A\kern-.1667em\lower.5ex\hbox{M}\kern-.125 \def\AmSTeX{{\cmsy A\kern-.1667em\lower.5ex\hbox{M}\kern-.125 emS}-\TeX} \def\SLiTeX{{S\kern-.06em{\sc l\kern-.035emi}\kern-.06emT\kern-.1667em\lower .7ex\hbox{E}\kern-.125emX}} % \def\AmSLaTeX{{\the\textfont\cmsyfam A\kern-.1667em\lower.5ex\hbox{M}\kern \def\AmSLaTeX{{\cmsy A\kern-.1667em\lower.5ex\hbox{M}\kern -.125emS}-\LaTeX} \font\tii=tii at 10.5pt \font\tibi=tibi at 10.5pt \def\MathTime{{\tii Math\-T\kern-2pt\i me}} \def\MathTimeBold{{\tibi Math\-T\kern-2pt\i me}} % % \def\ang#1{$\langle${#1}$\rangle$} \def\ang#1{{\lbms\char104}{#1}{\lbms\char105}} \def\angi#1{{\lbms\char104}{\it #1\/}{\lbms\char105}} \def\breakpar{{\parfillskip\z@\par}} \def\dottedline{\leaders\hbox to1em{\hss.\hss}\hfill} \def\tocsect#1#2#3{\vskip6.5\p@\noindent{\bf#1.\kern.5em#2\dottedline#3}\breakpar\vskip3.25\p@} \def\tocsub#1#2#3{\noindent\phantom{\bf0.\kern.5em}#1\kern.5em#2\dottedline #3\breakpar} \def\tocsubsub#1#2#3{\noindent\phantom{\bf0.\kern.5em0.0\kern.5em}#1\kern.5em #2\dottedline#3\breakpar} % % \def\vbar{$|$} % \chardef\vbar=`\| % vertical bar separating menu | submenu | subsubmenu % \def\vbar{\,`\|\,} % vertical bar separating menu | submenu | subsubmenu % \def\vbar{$\,|\,$} % vertical bar separating menu | submenu | subsubmenu % \def\vbar{$\,${\lbms\char106}$\,$} % vertical bar separating menu | submenu | subsubmenu % \def\vbar{$\,${\lbms\char105}$\,$} % vertical bar separating menu | submenu | subsubmenu \def\down{$\,${\lbr\char62}$\,$} % > separating menu > submenu > subsubmenu % \def\trademark{$^{\rm TM}$} \chardef\trademark=153 % TM - trademark (not registered) % \chardef\registered=174 % (R) - registered trademark % \chardef\copyright=169 % (C) - copyright % \chardef\paragragh=182 % pillcrow % \chardef\section=167 % section \chardef\onehalf=189 % {1\over2} % \chardef\multiply=215 % \times \chardef\times=215 % \times \chardef\ellipsis=133 % \dots % \def\tip{Advanced Feature: \enspace} \def\tip{{\bf Tip: \enspace}} \def\decreasepageno{\global\advance\pageno-1} \def\newpage{\vfill\eject} \def\blankpage{ \topglue 2in \hbox{ } % to get blank page \newpage % \decreasepageno } % \font\bigggsize=lsr at 18pt \font\bigggsize=lsr at 20pt % \font\biggsize=lsr at 12pt \font\biggsize=lsr at 16pt % \font\bigsize=lbr at 12pt % \font\bigsize=lbr at 11pt \font\bigsize=lbr at 10pt \def\coverpage{ % \nopagenumbers % \topglue 2in \hbox{ } % \vskip 2in \vskip 1in \centerline{{\bigggsize Y\kern-3pt{\biggsize\&}\kern-3ptY TeX System --- release 2.1}} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Define some useful acronyms %%%%%%%%%%%%%%% \def\DOS{{\sc dos}} % \def\DVIWindo{{\sc dviwindo}} \def\DVIWindo{{\sc dvi\-w}indo} \def\DVIPSONE{{\sc dvi\-ps\-one}} \def\DVIPS{{\sc dvips}} \def\PFE{{\sc pfe}} \def\CTAN{{\sc ctan}} \def\CD{{\sc cd}} \def\PS{{\sc ps}} \def\FTP{{\sc ftp}} \def\CTM{{\sc ctm}} \def\PDF{{\sc pdf}} \def\ATM{{\sc atm}} \def\AFM{{\sc afm}} \def\TFM{{\sc tfm}} \def\TIFF{{\sc tiff}} \def\BMP{{\sc bmp}} \def\TIFFTAGS{{\sc tifftags}} \def\WMFSPY{{\sc wmfspy}} \def\TSR{{\sc tsr}} \def\FMP{{\sc fmp}} \def\ANSI{{\sc ansi}} \def\ASCII{{\sc ascii}} \def\EPS{{\sc eps}} \def\EPSI{{\sc epsi}} \def\WMF{{\sc wmf}} \def\WWW{{\sc www}} \def\DSC{{\sc dsc}} \def\PIF{{\sc pif}} \def\AFMtoTFM{{\sc afm}to{\sc tfm}} \def\AFMtoPFM{{\sc afm}to{\sc pfm}} \def\TFMtoAFM{{\sc tfm}to{\sc afm}} \def\PFMtoAFM{{\sc pfm}to{\sc afm}} \def\PFAtoAFM{{\sc pfa}to{\sc afm}} \def\PFBtoPFA{{\sc pfb}to{\sc pfa}} \def\MODEX{{\sc modex}} \def\TWOUP{{\sc twoup}} % \def\DECODE{{\sc decode}} % \def\CLEANUP{{\sc cleanup}} % \def\SERIAL{{\sc serial}} \def\PKtoPS{{\sc pktops}} \def\TUG{{\sc tug}} \def\RAM{{\sc ram}} \def\FMP{{\sc fmp}} \def\WMF{{\sc wmf}} \def\PSNFSS{{\sc psnfss}} % follow may need some tweaking ... \def\TEXNANSI{TeX 'n {\sc ansi}} % \def\yandytex{\yandy\TeX} \def\yandytex{\yandy\ TeX} \def\yandytexBold{\yandyBold\ TeX} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Deal with encoding %%%%%%%%%%%%%%%%%%%%%%%% \input texnansi % in Windows 3.1 with ENCODING=texnansi % \input ansiacce % in Windows NT with TEXANSI=1 \catcode219=\active % \catcode`\Û\active % override ansiacce \catcode ... \coverpage \newpage \decreasepageno \topglue 2in \hbox{ } % to get blank page \newpage \decreasepageno %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Document itself starts here %%%%%%%%%%%%%%% \section{Introduction} % % Need a more general introduction --- provide more context? % Why has user bought the package --- what does (s)he expect? % \TeX\ --- invented by Donald E. Knuth of Stanford University --- is the premiere tool for typesetting % of technical material. \TeX\ excels at displaying mathematic formulae and also features an outstanding paragraph % hyphenation-justification line-breaking algorithm. \TeX\ is a `code based' system, that is, the source file you create is marked up using `control sequences,' and has to be processed by the {\TeX} `compiler' % processor before it is possible to view the typeset result on screen or on the printed page. Since \TeX\ is not {\sc wysiwyg} (or {\sc wysiayg} --- What You See Is All You Get), \TeX\ depends on % \yandytex\ system uses an edit--\TeX--preview cycle to produce the desired results. First, you create or edit a % plain {\ASCII} text source file in a text editor or word processor. Second, you `run \TeX' on the file, % with \yandytex. which creates a compact binary file with extension Û.dviÛ (for `DeVice Independent'). Third, you view the resulting Û.dviÛ file using the previewer. % {\DVIWindo}. If the results are not satisfactory, you go back to step one. Once you are satisfied with the results, you go to a fourth step: Printing your masterpiece of fine typography. %% emphasize speed ? The \yandytex\ System release~2.1 is an implementation of {\TeX} for IBM PC compatibles % running Windows~3.1, Windows NT~3.51, Windows~95, or OS~2/2.1. running Windows~95/98 or Windows~NT 4.0 (or later). It provides many advanced features such as on the fly font reencoding, dynamic memory allocation, partial font downloading, hypertext linkage, % added 1996/July/23 and multiple master font support. % added 1999/July/26 The \yandytex\ System comes with commercial grade fonts in industry standard {\ATM} compatible Adobe Type~1 format (a.k.a. `Post\-Script' fonts), but can also work with TrueType fonts. The \yandytex\ System is, like Gaul, divided into three main parts: \nlist \item {\DVIWindo}: a previewer and printer driver for \TeX\ {\tt.dvi} files. This is the heart of the system --- everything % else is controlled from here. \item {\DVIPSONE}: a device driver that converts \TeX\ {\tt.dvi} files to resolution independent, DSC-compliant, page-independent Post\-Script (PS) files suitable for printing on any Adobe Post\-Script % PS device. \item \yandytex\ itself: a 32-bit implementation of \TeX\ that can run as a `console application' in Windows~95/98 and Windows~NT. % 95/Sep/27 % for {\DOS}, {\DOS} boxes under Windows, and as a % `console application' in Windows NT. % and in a {\DOS} box under Windows 3.1. % rephrased 96/July/23 \endlist \noindent The \yandytex\ System includes Adobe Type Manager (\ATM) 4.0 for rasterizing fonts in Adobe Type~1 format, % the Programmer's File Editor, {\PFE}, the WinEdt editor, and some handy utilities. % programs % shareware ? CTAN ? In addition, the \yandytex\ System CD holds many useful {\LaTeXe} packages from CTAN (Comprehensive TeX Archive Network), extra documentation, as well as handy shareware programs. This manual explains how to install the system, % programs, gives brief instructions on how to use it, and gives hints on how to trouble-shoot the most common % Windows-related problems. This manual does {\it not\/} explain how to use \TeX\ or Post\-Script --- or how to program in \TeX\ or Post\-Script. The standard references for the two languages are {\sl The \TeX book}, % {\it The \TeX book}, by Donald E. Knuth (ISBN 0-201-13448-9), % (Reading, Mass.: Addison-Wesley, 1984) and {\sl Post\-Script Language Reference Manual}, % {\it Post\-Script Language Reference Manual}, 2nd ed., by Adobe Systems Inc. % Incorporated. % (Reading, Mass.: Addison-Wesley, 1990). (ISBN 0-201-18127-4). For {\LaTeX} (a dialect built on top of `plain' \TeX), refer to {\sl {\LaTeXSlanted} --- A Document Preparation System}, 2nd edit. by Leslie Lamport (ISBN 0-201-52983-1), % (Reading, Mass.: Addison-Wesley, 1994) and {\sl The {\LaTeXSlanted} Companion}, by Michel Goosens, Frank Mittelbach, Alexander Samarin % --- (0-201-54199-8). % For information on graphics inclusions see {\sl The LaTeX Graphics Companion}, by Michel Goosens, Sebastian Rahtz, Frank Mittelbach (0-201-85469-4) All of the above-mentioned books are % were published by Addison-Wesley (Reading, Massachusetts, USA). % (Reading, Mass.: Addison-Wesley, 1994) % give ISBN numbers also ? % It is assumed here that the reader has some familiarity with % Windows\registered\ and {\DOS}. % Familiarity with Windows\registered\ and {\DOS}\registered\ is also assumed. \subsect{Necessary Legal Stuff} % % Too flip ? % \yandy, Inc. will, of course, replace defective CDs. % and diskettes. \yandy, Inc. is not responsible for anything bad that happens while you use this software. \yandy, Inc. will, however, gladly take the credit for whatever good things happen. % say more about warranty or lack thereof ? The \yandytex\ System and the fonts supplied with it are copyrighted material and each copy is customized to a particular end user. Do not copy % or distribute. --- except for archival backup purposes. % Always install from the original diskettes. Refer to the end user license agreement printed on the software and font envelopes for exact statement of licensing terms. Please contact \yandy\ for generous site license terms, % information. second platform discounts, % As well as electronic publishing licensing terms for Adobe Acrobat PDF files. as well as information on publishing Adobe Acrobat PDF files with embedded fonts. Use of trademarks in this manual should not be construed as infringements of said trademarks. % those %% say something about fonts in PS or PDF files ? \subsect{Conventions} % Familiarity with % Microsoft Windows\registered\ is assumed. % and {\DOS}\registered\ is % also is assumed. Things you enter into fields in dialog boxes --- or type at the command prompt --- appear in a typewriter font, like so: Ûa:setupÛ. % a:install The same font will be used for folders, % disk directories, file names and so on. % maybe > is better than | ? % A vertical bar (\down) % will be used to A `greater than' sign (\down) % will be used to separates menu items selected from the names of the menus themselves. % submenu selections. % and so on. % separates the names of menu from items selected from % these menus. % submenu selections. % and so on. So, for example, `File{\down}Run' means select `Run' from the `File' menu (when reading constructions of this sort one might say `File {\it down\/} Run' to emphasize % the subsidiary relationship). that `Run' is subsidiary to `File'). More than one level of menu selection may be denoted in this fashion, e.g. `Preferences{\down}Ruler Units{\down}mm.' Another obvious extension of this notation is that `Start{\down}Run' denotes selecting `Run' from the menu reached by clicking on the `Start' button. The notation Ctrl+A denotes typing `A' while holding down the `Ctrl' key. Similarly, the manual refers to the `Shift' and `Alt' keys. %% Also explain \ang{Enter} and \ang{Alt-Tab} etc ? %% And why not use \ang also for other keys, like Esc, Ins, Del ? Console applications and utilities supplied give a command line summary when invoked with Û-?Û on the command line. This is useful, for example, when checking whether a utility has capabilities beyond the basic ones discussed in this manual. % The utilities that come with the system are in the Û\utilÛ subfolder % subdirectory (typically Ûc:\yandy\utilÛ). % Windows NT~4.0 has the `new shell,' that is, % the same look and feel as Windows 95 (while % Windows NT~3.51 still has the look and feel of Windows~3.1). % We'll use the term `new shell' when we want to refer % collectively to Windows NT~4.0 and Windows~95. % % (as distinguished from Windows NT~3.51). % We use the term `folder' in preference to `directory' % since this is common usage with the `new shell.' Adobe Type Manager ({\ATM}~4.0) comes % is available in two forms --- one for Windows~95/98 and one for Windows NT~4.0. ATM consists of two functional parts: (i) a font rasterizer (for on screen display and for printing to non-PS printers), and (ii) a font manager (facilitating font installation and removal). %% distinction between ATM rasterizer and ATM font manager In Windows~2000, the {\ATM} rasterizer is built in, and you do not install {\ATM}. % In this case You install fonts simply by dragging them % (to be specific: the Û.pfmÛ files) to the font folder (a sub-folder of the Windows NT folder --- typically Ûc:\winnt\fontsÛ). % However, in future a version of {\ATM} for Windows~2000 may add the benefits of a font management interface. % (the old ATM~3.02 will run on Windows~95/98, but not on Windows~NT). % (there are no plans to retrofit {\ATM} to Windows NT~3.51). % We'll refer to systems for which {\ATM} is available as % `{\ATM} compatible' systems. % Font installation instructions differ depending % on whether {\ATM} has been installed or not. % We assume here for concreteness that your diskette drive is Ûa:Û. % If it is Ûb:Û, then please replace Ûa:Û with Ûb:Û % Similarly, we assume that your CD driver is Ûd:Û. We assume here for concreteness that your CD drive is Ûd:Û. If it is not, then please replace Ûd:Û with the appropriate drive letter in the instructions that follow. In some of the examples, explicit reference will also be made to subfolders of the \yandytex\ System installation folder. If you install in other than the default Ûc:\yandyÛ folder you will need to make adjustments to these examples. % By the way, do {\it not\/} try to install the system into a folder that has a space in its name (such as ``Program Files''). \subsect{Requirements} % The \yandytex\ System~2.1 requires: \beginlines (i)~IBM PC compatible 486 (Pentium recommended); (ii)~CD ROM drive; % (iii)~3\onehalf" diskette drive (for ATM~3.02); (iii)~16 Meg of {\RAM} (32 Meg when using NT); (iv)~20--30 Meg of free hard disk space; (v)~VGA display (higher resolution recommended); (vi)~Windows~95, 98 or Windows NT~4.0 (or later). % (vii)~PostScript printer if you have PostScript inclusions. \endlines % (vi)~DOS 5.0 or later; % (vi)~Windows 3.1, Windows for Workgroups 3.11, Windows NT 3.51, % Windows~95, or OS/2 release 2.1. % will not run on Windows 3.1 or OS 2/2.1 % CD-ROM :-) % Tech support info ? tech-help@YandY.com, fax number % ask them to give serial & machine configuration ? \section{Installation} There are two parts to the installation: (i) installing {\ATM} and the fonts (do this first), and (ii) installing the {\yandy} TeX System itself. % We'll discuss {\ATM} installation first, since {\ATM} should be installed % first --- except on Windows~2000. % it is best to install the fonts before the \yandytex\ System itself. % %% systems with {\ATM}. % % On `{\ATM} compatible' systems % (i.e. systems for which {\ATM} is currently available), On Windows~95/98 and Windows~NT 4.0, you must install Adobe Type Manager ({\ATM}). {\ATM} rasterizes the fonts for on screen display as well as when printing to non-PS devices. On Windows~2000, the Type~1 font rasterizer is built in, and Type~1 fonts can be installed by dragging them to the ÛfontsÛ folder. % but has some advantages. % % You may, however, still wish to install {\ATM} for its font management functions. % % Install ATM~4.0 for NT if you have it. % --- unless you are using a version of Windows~NT % for which no {\ATM} is yet available. % Then To install {\ATM}, right click on the {\CD} icon and select from the menu % that appears the version of {\ATM} appropriate to your operating system. % If you elect to install {\ATM} {\it without\/} fonts, then you will later need to install the fonts supplied with your \yandytex\ system from the {\ATM} control panel (see section~2.1). % converting them to TrueType format. % during installation. % install the fonts instead from the `Fonts' icon in the Windows control panel % --- this will automatically convert them to TrueType format % (see section on conversion to TrueType format). % give number ??? % While this font conversion is automatic, exactly how it is invoked % depends on the version of Windows~NT being used (see section~2.2). % See section~2.2. % for details. % Give more details? OK! % If you have received the \MathTime\ fonts, first % $run the Ûprepare.batÛ batch file in a temporary folder % directory % on your hard drive % (and Ûtexttune.batÛ) % {\it before\/} installing the fonts % (Either using {\ATM} or by converting them to TrueType format in Windows~NT). % Consult the documentation that comes with the \MathTime\ fonts % for additional details, if necessary. % Note that with large font sets (such as Computer Modern or % Lucida Bright + Lucida New Math), the last diskette typically % often % contains {\it only\/} Û.afmÛ metric % files, Û.texÛ source files, and other ancillary files --- {\it not\/} % installable Û.pfbÛ and Û.pfmÛ files. % So don't be surprised if no fonts are found on the last diskette % of a set! \subsect{Installing Fonts with ATM} % On Windows~95/98 start by installing {\ATM}. % On Windows~NT install {\ATM} if you have {\ATM}~4.0 for NT. Start by installing {\ATM} from the CD. Choose the version appropriate to your version of Windows. % In either case, insert the {\ATM} diskette or CD, % and type Ûa:installÛ from the `Start{\down}Run' dialog. % {\ATM} only exists for new shell... % (or `File{\down}Run' dialog in the Program Manager in Windows~NT). NO % Refer to `Installing {\ATM}' in the {\ATM} manual if necessary. This step normally {\it also\/} installs the fonts that came with your system. % Adobe currently supplies us with {\ATM} version~3.01 for use with Windows~95 % You need at {\it least\/} {\ATM} version~3.02 % for everything to work as advertised in Windows~95/98. % and ATM~4.0 for NT when using Windows~NT. % If you use {\sc pcl} printers in Windows~95, % you need the latest printer drivers, % since the original Windows {\sc pcl} drivers are buggy. % (An upgrade from {\ATM}~3.0 and {\ATM}~3.01 to version 3.02 % is included in the Û\utilÛ subfolder --- % unzip the file Ûatm302up.zipÛ using Ûpkunzip.exeÛ). % (Free upgrades from {\ATM}~3.0 and {\ATM}~3.01 to version 3.02 % are available at Ûhttp://www.adobe.comÛ). % For Windows~NT 4.0 you can use {\ATM}~4.0 for NT if you have it --- % For Windows~NT 4.0 you can use {\ATM}~4.0 for NT (recommended) === % or you can use the automatic conversion to TrueType format % described in the next section. % section~2.2 If you installed {\ATM} {\it without\/} installing fonts, you can selectively install fonts later. % Once you have {\ATM} installed, Start up the {\ATM} control panel --- from the `Start' button select % `Programs{\down}Main{\down}ATM' (ATM~3.02) or `Programs{\down}Adobe{\down}Adobe Type Manager.' % (ATM~4.0). Click on `Add' or `Add Fonts.' Then choose the drive with the CD % (in {\ATM} 3.02, look for a list of drives --- Û[-a-]Û etc. % --- near the bottom of the list of folders), Select each of the folders with the fonts in turn. The names of these folders are: \beginlines (i) CM, AMS, LatxFont, TeX Pi (Computer Modern TeX System); (ii) MathTime, MathPlus (MathTime TeX System); (iii) Lucidabr, LucidExp (Lucida Bright TeX System); and (iv) EM, TeX Pi (European Modern TeX System). \endlines \noindent You may also have additional font folders, such as `XY' (fonts for use with XY-Pic). In each folder, highlight all the font names shown, and click on `Add' % again (A quick way to highlight all font names is to type Ctrl-A). Make sure to \beginlines (1) check `Autodownload for Post\-Script driver,' and (2) do {\it not\/} check `Install without copying files'. \endlines % \noindent Repeat for the other font diskettes. % (note, though, that with some font sets, the last diskette % contains {\it only\/} % Û.afmÛ metric files, Û.texÛ source files, and other ancillary files, % {\it not\/} installable Û.pfbÛ and Û.pfmÛ files). % \subsect{Systems without ATM --- Conversion to TrueType} % \subsect{Systems without ATM --- Windows~2000} \subsect{Installing fonts without ATM} % --- Windows 2000 % Until there is a version of {\ATM} for Windows~NT, In Windows~2000 you can use Type~1 fonts % by converting them to TrueType format using the built-in {\ATM} rasterizer. % built into Windows NT~4.0. % But first replace the Ût1install.dllÛ that came % with your system with the improved version on the CD % in the Ût1installÛ folder. Please refer to Ût1install.txtÛ % for details. % % To convert the fonts, drag the Û.pfmÛ files --- % `fonts' (the To install the fonts, drag the Û.pfmÛ files --- % `fonts' (the the ones with the red `a' icon --- from the folder on the CD to the `Û\fontsÛ' folder --- subfolder of your `ÛwinntÛ' folder. Whenever a font is dropped into the ÛfontsÛ folder, it is automatically registered.% converted and % This can be done conveniently starting from `My Computer.' Open the `Ûc:\winnt\fontsÛ' folder in one window and the folder with the fonts on the {\CD} in another (perhaps by starting again at `My Computer'). Alternatively, you may prefer to use Windows Explorer. Explorer can be reached from `Start{\down}Programs.' Note that you can select the fonts in one folder by holding down the `Ctrl' key and clicking on each Û.pfmÛ file listed. % Then drag the selection to the Û\fontsÛ sub-folder of the % ÛwindowsÛ folder. A convenient alternative is to select {\it everything\/} in a folder by clicking on an item in the folder and then typing `Ctrl'-A. In this case files other than Û.pfmÛ files will {\it also\/} be selected --- and the system will complain about that --- but you can ignore these benign complaints --- nothing bad will happen! % Alternatively you can open the `Û\fontsÛ' subfolder % subdirectory % of your ÛwindowsÛ folder % directory % from Explorer and select `File{\down}Install New Font'. % On Windows NT {\it without\/} the new shell % (i.e. Windows NT~3.51) % double click on the `Control Panel' icon in the `Main' program group. % Then double click on the colorful `Fonts' icon. % Click `Add' and navigate to the diskette with the fonts. % Select all of the fonts listed and click on `Add' again. % On Windows NT with the new shell you can get to the control panel % from `Start{\down}Settings{\down}Control Panel'. % When you install fonts, elect to have the Type~1 fonts made available % to the Post\-Script printer driver % (so the converted TrueType versions % will be used {\it only\/} for on screen display). % In summary, check all three boxes in the dialog box: % \beginlines % (1) `Convert Type 1 Font to TrueType,' % (2) `Install Type 1 Font Files for use on a Post\-Script Printer,' and % (3) `Copy Type 1 Font Files to Fonts Folder.' % \endlines % \noindent If you experience problems resulting from `font name mangling' by the automatic installation in Windows~NT run the ÛsetupttfÛ utility % after installing fonts. after installing all fonts. The `Ûsetupttf.exeÛ' utility % comes with the \yandy\ TeX System % In release~2.1 of {\yandy} TeX System this application is in the may be found in the `Û\utilÛ' subfolder. % (typically Ûc:\yandy\util\setupttf.exeÛ). You can run this utility from `Start{\down}Run' by typing Ûc:\yandy\util\setupttfÛ. % % Flush following alternative ? % Alternatively, start from the command prompt. The command prompt can be reached from `Start{\down}Programs.' At the prompt, type \beginlines Ûc:\yandy\util\setupttfÛ \endlines \noindent then type ÛexitÛ to dismiss the command prompt again. \vskip .05in \subsect{Fonts supplied with the System} With your \yandytex\ System, you will have received % several a CD with folders % diskettes containing fonts in {\ATM} compatible Adobe Type~1 format: \nlist \item {\yandy} CM TeX system includes (i) the Computer Modern fonts, (ii) the AMS font set, as well as (iii) the extra {\LaTeX} + {\SliTeX} font set; \item {\yandy} LB TeX system includes (i) the Lucida Bright + Lucida New Math fonts, as well as (ii) the Lucida Bright Expert font set; % and \item {\yandy} MT Complete TeX system includes (i) the \MathTime~1.1 fonts, as well as (ii) the \MathTime\ Plus fonts. \item {\yandy} EM Complete TeX system includes (i) the EM fonts, as well as (ii) the TeX Pi fonts. \endlist \noindent The text fonts used with \MathTime\ are the Times-Roman, Helvetica, and Courier font families. These are automatically installed with the special version of {\ATM} that we supply. % On Windows~2000 systems when {\ATM} is not used, install these 13 fonts separately from the ÛpsfontsÛ folder in the {\ATM} folder on the CD --- as described above. % in the previous section. % section~2.2 % As mentioned above, % The \MathTime\ % math % fonts themselves % should {\it not\/} be installed straight off the diskette. % Prepare an empty temporary directory, make that the current directory % be installed from a temporary directory in which % and run the Ûprepare.batÛ batch found on the diskette. % All other fonts are installed straight off their respective diskettes. %% forward reference to section describing how to use LB+LNM, MT See sections~3.7.4 and 3.7.5 % for LB+LNM & MathTime % See later % explicit section ? for instruction on how to use fonts other than Computer Modern with plain {\TeX}, {\LaTeX}~2.09, and {\LaTeXe}. \subsect{Installing the Y\&Y TeX System Itself} %% This section is rather long % The \yandytex\ system itself is installed simply by using % Ûd:setupÛ from the `Start{\down}Run' dialog box % where Ûd:Û is your CD ROM drive. % Or double click on Ûsetup.exeÛ on the CD reached from `My Computer.' To install the \yandytex\ system itself, right click on the {\CD} icon and select % installation of the \yandytex\ system. the system installation. % in systems with the new shell (i.e. Windows~95 and Windows NT~4.0). % (assuming that Ûa:Û is your diskette drive). % In Windows NT~3.51, install instead using the `File{\down}Run' % dialog box in Program Manager. % Similarly, we'll assume you are installing the system on Windows~95 and hence % using the `Start' button. % On other operating systems please adjust the instructions as described above. % The ÛsetupÛ installation program first The program first % calls for the three `{\yandy} TeX System' diskettes. installs the basic {\yandy} TeX System with the plain {\TeX} and {\AMS}-{\TeX} formats. At the end of this operation you are given the option to also install {\LaTeXe} and/or {\LaTeX} 2.09. You can install {\LaTeX} at this point or do this latter % These two formats can alternatively be installed later by % running Ûsetup1.exeÛ on the CD (note the digit 1). by right clicking on the {\CD} icon and selecting installation of \LaTeX from the menu. % then it will also refer to the three `{\LaTeX} Support' diskettes. % The `{\LaTeX} Support' diskettes can be installed % separately at a later time, by the way. You can choose which system components to install. % You may, for example, wish to omit {\DVIPSONE}, the Post\-Script printer driver, % if you will never need Post\-Script output. We recommend that you accept the defaults. By the way, do {\it not\/} attempt to install into a folder that has spaces in its path name --- {\TeX} itself does not like file names with spaces! If you like your current text editor or word processor then you can link it into the `TeX' menu in {\DVIWindo}, as explained in section~3.4.2. % explicit section ? % But the \yandytex\ System does include a full featured Windows editor of its own --- % developed by Alan Phillips --- called {\PFE}. WinEdt --- developed by Aleksander Simonic. The editor will be installed in the ÛWinEdtÛ subfolder of the main Û\yandyÛ folder. % The {\PFE} editor The editor comes with its own `help' file explaining its operation --- just hit the F1 function key to access it while in the editor. % while in {\PFE}. % We also include {\PFE} Note that you can always add system components later. Also, most choices made during installation can be modified from the `Preferences' menu in the {\DVIWindo} previewer (or by editing the \yandytex\ configuration file Ûdviwindo.iniÛ in the ÛwindowsÛ or ÛwinntÛ folder % directory using a plain ASCII text editor --- such as `Notepad,' `WordPad,' `WinEdt' or {\PFE}). % (in `Start{\down}Programs{\down}Accessories') We'll discuss next the questions that you will be asked % come up during installation. We recommend that you normally accept the default choices, unless there is some good reason not to do so. \subsub{Questions and Answers during Installation.} % TeX System Customization % You can chose between `Custom' and `Express' installation. If you chose `Express' installation, you will not be asked a lot of questions and the defaults will be used. Otherwise read on. When asked what font encoding (character layout) to use for text fonts, accept the default {\TEXNANSI} (ÛtexnansiÛ, also referred to as LY1 in {\LaTeX}) --- unless you are % both a \TeX pert and a `fontspert' and want to experiment. The chosen encoding will be used for all {\it text\/} fonts. % or you do not have {\ATM} installed. % If you are running on Windows ~NT {\it without\/} {\ATM}, % select `Windows ANSI' encoding instead. % This is required because TrueType fonts {\it cannot\/} be reencoded % `on the fly' --- the way {\DVIWindo} reencodes Type~1 fonts --- % and Windows insists on encoding text fonts as Windows ANSI. You will be asked where {\TeX} source files may be found. Now, you can, of course, run {\TeX} on files in {\it any\/} folder, by giving their full path, but it can be % is often convenient to give just a file name {\it without\/} the path in Û\inputÛ and Û\usepackageÛ macros. The installation already adds folders % the folders % directories with the {\LaTeXe} class files, and {\LaTeX} 2.09 style files, so you need not be concerned about those. During installation you are given % This just gives you an opportunity to enter {\it additional\/} folders. % directories. Give the full path of each folder % directory that you plan to use for % {\TeX} style files --- % and source files --- hit \ang{Enter} after each one. When you are done, click `No' when asked: `Specify another directory?'. Note that you can easily change this list of folders % directory list later by modifying the ÛTEXINPUTSÛ environment variable from {\DVIWindo}'s `Preferences{\down}Environment Variables' menu (or by editing the Ûdviwindo.iniÛ file). Actually, unless you are running {\TeX} {\it without\/} a format preloaded, you should modify the `format specific' variables ÛPLAINÛ for plain {\TeX}, ÛAMSTEXÛ for {\AMS}-{\TeX}, ÛLPLAINÛ for {\LaTeX} 2.09, or ÛLATEXÛ for {\LaTeXe} --- see section~3.2.1). Similarly, you will be asked where your graphics and image files ({\EPS}, {\TIFF}, {\BMP} and {\WMF}) % (if any) are to be searched for. Navigate to or type in the full path of each folder. % directory. When you are done, click `No' when asked: `Specify another directory?'. This list can be changed easily later by modifying the ÛPSPATHÛ environment variable from the {\DVIWindo}'s `Preferences{\down}Environment Variables' menu. % (or by editing the Ûdviwindo.iniÛ file) % Note that if you want {\TeX} to be able to read the `bounding box' in your EPS files then the folders % directories with those files need to be on the list searched by {\TeX} or {\LaTeX} {\it also\/}. % The installation program automatically takes care of this. % % If you add additional folders later you will have to do this manually. You will be asked whether you have {\TeX} font metric (Û.tfmÛ) files in another folder % directory that you would like to use with the system. Typically the answer is `No.' This list can be changed later by modifying the ÛTEXFONTSÛ environment variable % in Ûdviwindo.iniÛ from {\DVIWindo}'s `Preferences{\down}Environment Variables' menu. % (or by editing the Ûdviwindo.iniÛ file) (Actually % unless you are running {\TeX} without a format preloaded, --- as explained above --- you should modify the `format specific' variables for the dialect of {\TeX} being used). % ÛTEXNANSIÛ for TeX 'n ANSI encoding, % ÛANSINEWÛ for Windows ANSI encoding, and so on). %%% Does it ask about which ports have PS printers??? % Graphics File Formats, David C. Jay & John R. Levine % Windcrest/McGrawHill ISBN 0-8306-3059-7 You will also be asked whether \yandytex\ should write Û.dviÛ files in the same folder as the \TeX\ source file, or instead into a {\it common\/} working folder. % directory. {\TeX} users seem to be divided % about equally as to which of the two modes of operation they prefer. %% Send in your vote! Win a free vacation to Hawaii! If you can't decide, chose {\it not\/} to use a common working folder (so that the output files will be written back into the same place the source files came from). Here is the difference: If you run \TeX\ on Ûc:\books\chapter1.texÛ and chose the former (i.e. {\it no\/} common working folder) then the Û.dviÛ file will be Ûc:\books\chapter1.dviÛ. If you chose instead to have a common working folder % directory called, let's say, Ûc:\workingÛ, then the Û.dviÛ file corresponding to Ûc:\books\chapter1.texÛ will % instead be Ûc:\working\chapter1.dviÛ. An advantage of a common folder % directory is that it is easy to clean up and delete old Û.dviÛ files. % later. % optional ? A disadvantage is that files for different jobs will be mixed up in one place. The common working folder can be a folder on your hard drive (which is created by the installation program if it doesn't already exist), or it can be on a {\RAM} drive % (well, at least in Windows~95/98). (Windows~95/98). % % Is it impossible to have RAM drive in NT % % Files on a {\RAM} drive disappear when you power down your machine. % (use {\sc dos help} to find out what parameters to use when % you load Ûramdrive.sysÛ in your Ûconfig.sysÛ file). %% No RAM drives in Windows NT ??? %% No DOS Help in Windows 95 ??? If you forget which mode you chose, you can easily get frustrated, because you won't know where your Û.dviÛ files are going to! One side effect of this may be that your preview will not be updated when you re-{\TeX} a file --- since you may be looking at a ``stale'' version in the wrong folder, rather than the fresh version just created. In this case just see whether % or not % `Fonts{\down}Working Directory' is checked in {\DVIWindo}. `Special{\down}Working Directory' is checked in {\DVIWindo}. % You can temporarily change this selection by checking or unchecking % this menu item. You can change the selection permanently % later by changing the ÛWorkingDirectoryÛ entry in the Û[Window]Û section of Ûdviwindo.iniÛ --- or temporarily by toggling the check mark on % `Fonts{\down}Working Directory.' `Special{\down}Working Directory.' %%%%% Maybe explain the directory structure here ??? \subsect{Quick Tutorial} This section walks you through creation of a simple {\TeX} source file in the text editor, `compilation' of that file using {\TeX}, and finally viewing the typeset result on screen. % in {\DVIWindo}. If you did not already do so during installation, this may be a good time to create a folder % directory for `random' {\TeX} source files. % such as the one to be typed in and edited in this exercise. {\TeX} can, of course, read source files from any folder, % directory, but a common folder % directory for `miscellaneous' {\TeX} source files can make it easier for you to find them again later. % You can create a new folder % directory using the Windows Explorer, % (in systems with the new shell), or from `My Computer' using `File{\down}New{\down}Folder.' % or the File Manager (in systems without). % --- or even from the {\DOS} prompt using ÛmkdirÛ. For concreteness, let us suppose this new folder is called Ûc:\texinputÛ. %%% is this name used again later ??? % Now we are ready for a simple \TeX exercise. Now we are ready for a simple \TeX ercise. Launch {\DVIWindo} by double-clicking on the {\DVIWindo} icon on the desktop (or by selecting it from `Start{\down}Programs{\down}YandY21'). % => installation program YANDY20 ??? % from the % `Y and Y' % `{\sc YANDY2x}' % ??? % `{\sc YANDY2}' % ??? % program group reached via % from % `Start{\down}Programs.' % Start > Programs > YandY2x > DVIWINDO_2x You might want to resize {\DVIWindo}'s window at this point by dragging the right window frame to the left a bit. This will make it easier to switch between different windows just by clicking on an exposed part of a window. % Select `TeX{\down}PFE Editor' to call the {\PFE} editor. Select `TeX{\down}WinEdt' to call the editor. You will be presented with a File Open dialog box. The first time you do this, enter an exclamation mark (!) for `File Name' to tell the system that you do {\it not\/} wish to open an existing file. % --- instead asking it to create a new file. Click `OK.' The editor comes up. % The {\PFE} editor comes up. If it covers the full screen, change it to windowed mode by clicking on the double rectangle icon in the top right corner. Select `File{\down}New.' A new window % labelled `Untitled1' appears. %%%%%%%%%%%% editor changed !!! At this point, you may want to resize the overall % {\PFE} editor window to cover less of the screen. % (drag the right and bottom edges closer to the edges % of the `Untitled1' window). Then click on the editor window % labelled `Untitled1' and type something like `ÛHello World!Û,' followed by `Û\endÛ'. That is all you need if you are using Computer Modern fonts. If you are using Lucida Bright fonts % or \MathTime\ fonts, insert `Û\input lcdplainÛ' at the beginning of the file. % respectively If you are using \MathTime\ fonts insert instead `Û\input mtplainÛ. % (or `Û\input mtplainxÛ' if you also have the \MathTime\ Plus fonts). % Next, if you are using {\TEXNANSI} (LY1) encoding with non-CM fonts % then add `Û\input texnansiÛ' % after the above. (If you are using Windows {\ANSI} encoding % then add `Û\input ansiacceÛ' instead). Finally, select `File{\down}Save.' You will be presented with a `File Save' dialog. % box. Navigate to the folder % directory that you wish to use for {\TeX} input files (perhaps Ûc:\texinputÛ), enter {\tt hello.tex} for the File Name, and click `OK'. Now that the file has been saved, click on {\DVIWindo}'s window to give it the input focus again. Select `TeX{\down}plain TeX'. Use the File Open dialog box that appears to select the file that you have just saved. \yandytex\ will run in a window that disappears when it finishes (unless there was an error). Now select `TeX{\down}Preview' to see the typeset result. (If you don't see it right away, try `File{\down}Default Scale'). You can also open the DVI file directly from `File{\down}Open.' At this point click on the % {\PFE} editor window to get its attention again, and add Û$z=\sqrt{x^2+y^2}$Û just before the Û\endÛ. This time type Ctrl+S to save the modified file. Then type \ang{Alt-Tab} to return input focus to {\DVIWindo}'s window, % click on {\DVIWindo}'s window again (or and use the F5 function key to call plain {\TeX}. The preview will be automatically refreshed when {\TeX} has finished producing Ûhello.dviÛ from Ûhello.texÛ. You will notice how once you get going, there is little need to interact with % File Open dialog boxes. Also, most things in the editor can be accomplished using the tool bar instead of the pull down menus. And judicious use of `hot keys' % in {\DVIWindo} can speed up the edit-{\TeX}-preview cycle. % In the above, it took just three key strokes (Ctrl+S, \ang{Alt-Tab}, F5), to refresh the preview after making changes in the {\TeX} source file. % \yandytex\ is so fast that you can get almost instantaneous screen updates on short source files. % (such as this manual). There are some sample `Hello World' test files already set up for you to look at in the `texinput' subfolder of your `yandy' folder. Look for `ÛHello_CMÛ,' `ÛHello_LBÛ,' `ÛHello_MTÛ,' or `ÛHello_EMÛ' --- the last two letters in the name denote the font set for which the file is designed. You will find both `source' files (extension Û.texÛ) and corresponding Û.dviÛ files. These sample files are set up for {\LaTeXe}. You can open the Û.dviÛ files from `File{\down}Open'. The corresponding source files can be opened with the editor from the `TeX Menu' as described in the next section. % \section{Using the \yandytex\ System} \section{Using the \yandytexBold\ System} % % This section focuses on the `edit--{\TeX}--preview' cycle alluded to % in the introduction. % earlier. The heart of the system is {\DVIWindo}, the previewer. Your editor, {\TeX} itself, the printer drivers, and other programs are all called from here. % the previewer. % 's `TeX' menu. You call {\TeX} or {\LaTeX} from {\DVIWindo}'s `TeX' menu. Installation sets up `hot keys' that make this particularly easy --- just press F5 for plain {\TeX}, F6 for {\AMS} {\TeX}, F7 for {\LaTeX}~2.09, and F8 for {\LaTeXe}. The hot keys are listed in the menu itself for easy reference --- and of course, you can customize them --- as explained later. Note that you do not need to close the preview when you call {\TeX}. The preview is automatically refreshed when {\DVIWindo} notices that the Û.dviÛ file has been `re-compiled.' The editor is also called from {\DVIWindo}'s `TeX' menu. Installation sets up convenient hot keys. % for the {\PFE} editor --- Just press F9, and % {\PFE} the editor will pop up with the {\TeX} source file corresponding to the Û.dviÛ file % currently currently being viewed (see section~3.3.2 % customizing the `TeX' menu on how to link in your own editor instead). %% section? Of course, when you start, you may not be viewing a Û.dviÛ file. In this case you will be presented instead with a `File Open' dialog box so that you can select a {\TeX} source file for the editor to open. % Initially, you may not have a source file to open. If you want to start on a fresh file, just enter % ! (exclamation mark) an exclamation mark (!) instead of a file name. % some repetition of material in Tutorial ? % or `nul' If you are viewing a Û.dviÛ file and want to edit a file {\it other\/} than the corresponding source file, % If you want instead to select a different file, then hold down the `Shift' key while calling the editor --- the `File Open' dialog will pop up. % After editing the file and running {\TeX}, use `Tex{\down}Preview' to view the corresponding Û.dviÛ file. You won't need to use `Tex{\down}Preview' % once you get going, later on, since the previewer will already be `connected' to the appropriate Û.dviÛ file. % You may print either from the `File{\down}Print' dialog box or directly % from the {\DOS} command line. You print from the `File{\down}Print' dialog box in {\DVIWindo}. % If you have installed {\DVIPSONE}, then you can check the For Post\-Script output devices check the `Use DVIPSONE' box % for Post\-Script output devices (You {\it can\/} use Microsoft's or Adobe's Post\-Script printer drivers, but they do {\it not\/} have any of the advanced features of {\DVIPSONE} --- such as partial font downloading and on-the-fly font reencoding). For non-PS devices % Otherwise the standard Windows printer drivers will be used. % are used. Note that you can {\it also\/} use \yandytex\ and {\DVIPSONE} as `console applications' % or directly from the {\DOS} command line. from the command prompt. This may be useful in some cases % rare % were you may want if you want to process several files in batch mode, or gain direct control over processing options using command line flags. % and command line arguments. % For each application You can get a list of commonly used command line options by invoking either application with Û-?Û on the command line. For additional information refer to the Technical Addendum or the Ûreadme.txtÛ file in the corresponding application folder (i.e. the Û\yandytexÛ and Û\dvipsoneÛ subfolders) --- % directory --- these each give a list of command line options. You can add command line option passed to these programs when they are called from {\DVIWindo} using `Preferences{\down}Command Line.' \subsect{The Edit--\TeX--Preview Cycle} % % The following sections expand on the elements of this process. % The following expands on the edit--\TeX--preview cycle in \yandytex. This section focuses on the `edit--{\TeX}--preview' cycle alluded to earlier. % introduction. % If your monitor has enough screen resolution, you % most likely will find that the most efficient way to operate is to use overlapping --- or side-by-side --- windows. % (as opposed to running every application full screen). If both {\DVIWindo} and the editor window are visible, then you can switch between them simply by clicking on a visible part % corner of the window that you would like next to receive the input focus. % (By the way, for high quality display, it is a good idea to use as high a screen resolution as your video board supports. You can control the screen resolution from `Start > Settings > Control Panel > Display.') If your monitor has limited screen resolution, then you may instead wish to run {\DVIWindo} and the editor full screen. To switch between them in this case % simply use Windows' standard method: hold down the `Alt' key and press % `Tab' \ang{Tab} until you get to the desired window % (to step in reverse order, hold down the `Shift' key as well). Alternatively, you can use the `TeX' menu to transfer control to the editor. Installation creates entries that {\it switch\/} to a window (rather than {\it launching\/} a new copy of an application). % the editor). By convention such entries are marked with an initial `Û->Û' in the `TeX' menu. Like all other entries in the `TeX' menu, these may be associated with hot keys. % also. For example, to switch to the % {\PFE} editor window, hold down the `Ctrl' key and hit F9 (denoted C-F9 in the `TeX' menu). % \subsect{The {\tt dviwindo.ini} File} \subsect{The {\secttt dviwindo.ini} File} % Preferences and user customizations % for the system are saved in Ûdviwindo.iniÛ in your `windows' or `winnt' folder. % The Ûdviwindo.iniÛ file has several sections, including: \nlist \item Û[Window] Û\quad{\DVIWindo}'s preferences (`Preferences' menu); % in {\DVIWindo} % reversed order of the two following 95/Sep/27 \item Û[Environment] Û\quad The `environment variables;' \item Û[Applications]Û\quad Plain {\ASCII} representation of the `TeX' menu. % \item Û[Documents] Û\quad Names of the most recently used Û.dviÛ files; % \item Û[Registration]Û \endlist \noindent The environment variables tell various components of the \yandytex\ System where files are located, as well as general preferences you have expressed during installation. % The environment variables can be edited from {\DVIWindo}'s `Preferences{\down}Environment Variables' menu. % The Û[Environment]Û section is typically the only part of Ûdviwindo.iniÛ that you may want to make adjustments to. % Actually, if you have installed the \yandytex\ System as described in % section~2, then you may well never have to even % look at the [Environment] section. % of % at the Ûdviwindo.iniÛ. % file. % If you did not install it the standard way, then you may. % The gory details of the menu implementation are in the Ûreadme.txtÛ and % Ûnews.txtÛ files in the Û\dviwindoÛ directory. % Here, we will discuss the environment variables. % % Next, we will discuss the environment variables. % Anyway, Here follows a sample Û[Environment]Û section: % \hskip12bpÛc:\yandytex\latex2e;c:\yandytex\ams\amstexÛ \beginlines Û[Environment]Û ÛYANDYPATH=c:\yandyÛ ÛTEXFORMATS=c:\yandy\yandytex\fmtÛ ÛTEXPOOL=c:\yandy\yandytex\fmtÛ ÛPSFONTS=c:\psfonts;c:\winnt\fontsÛ ÛPSPATH=c:\eps;c:\tiff;c:\wmfÛ ÛVECPATH=c:\yandy\fonts\encodingÛ ÛPREPATH=c:\yandy\dvipsoneÛ ÛSUBPATH=c:\yandy\dvipsone\subÛ ÛTEXINPUTS=c:\yandy\texinput;c:\yandy\tex\base\\Û ÛAMSTEX=c:\yandy\texinput;c:\yandy\tex\base\\Û ÛLPLAIN=c:\yandy\texinput;c:\yandy\tex\latex209\\;c:\yandy\tex\base\\Û ÛLATEX=c:\yandy\texinput;c:\yandy\tex\latex\\;c:\yandy\tex\base\\Û ÛENCODING=texnansiÛ ÛTEXFONTS=c:\yandy\fonts\tfm;c:\yandy\fonts\Û ÛTEXNANSI=c:\yandy\fonts\tfm\texnansi\tfm\\;c:\yandy\fonts\tfm\nontext\Û ÛANSINEW=c:\yandy\fonts\tfm\ansinew\tfm\\;d:\yandy\fonts\tfm\nontext\Û \endlines % ÛTEXANSI=0Û % ÛDUMMY=1Û \noindent % These environment variables can also be changed % by editing Ûdviwindo.iniÛ using any plain {\ASCII} text editor % such as `Notepad,' `WordPad,' `WinEdt' or {\PFE}. % If you want to edit Ûdviwindo.iniÛ simply open it in some plain text editor like Notepad, Wordpad, WinEdt or {\PFE}. A `{\DVIWindo} {\sc ini}' icon is already set up ({\it not\/} the `{\DVIWindo}' icon itself) for this purpose. This launches `Notepad' and reads Ûdviwindo.iniÛ from the Windows folder. % % The environment variables are listed in the % Û[Environment]Û section. After making changes, select `File{\down}Save' and then `File{\down}Exit.' \tip % Advanced Feature: If a folder in a list of folders ends with a backslash (Û\Û), then {\TeX} will {\it also\/} search first level subfolders % subdirectories of that folder. % directory. If it ends with a {\it double\/} backslash (Û\\Û) then {\TeX} will search {\it all\/} subfolders % subdirectories recursively (Use these capabilities sparingly --- it takes extra time to search complex trees of folders). %% the above is repeated later If your Ûdviwindo.iniÛ file is missing entries for some of the environment variables, then the \yandytex\ System may not find all of the files it needs ({\it unless\/} you happen to have installed all system components in the standard folders). % directories). If a problem does arise, then we recommend that you edit your Ûdviwindo.iniÛ file. You'll know there's a problem if \TeX\ complains: \beginlines ÛSorry, I can't find that format; will try the default.Û, or perhaps Û! I can't find file Û `\angi{file\-name}.' \endlines \noindent If the corresponding files {\it do\/} exist, then the problem most likely is with the environment variables. % The same may be true when {\TeX} can't find font metric (Û.tfmÛ) files. % By the way, older versions of \yandytex\ % (as well as many other {\TeX} systems) % (as well as most of our competitors) % used {\DOS} environment variables instead of % an `ini' file for this purpose. % the Û[Environment]Û section of Ûdviwindo.iniÛ. % give forward reference to: % Sometimes it is convenient to change environment variables when working on % hmm, is this really a good idea ??? %%% autoexec.nt and config.nt are the defaults used %%% can set a command prompt up to use some other files... %% use bulleted list for following? \subsub{What the Environment Variables Mean} % \ulist \item ÛTEXINPUTSÛ\quad Where \TeX\ style- and source files may be found -- {\it unless\/} a `format specific' environment variables overrides this --- see below. % reference to same section This is {\it one\/} environment variable you may actually find yourself modifying as you add more folders % directories with {\TeX} style files. Installation sets this to a semicolon-separated list, e.g., \beginlines ÛTEXINPUTS=c:\texinput;c:\yandy\texinput;c:\yandy\tex\base\\Û \endlines % ÛTEXINPUTS=c:\texinput;c:\letters;c:\books;c:\yandytex\latexÛ \noindent The installation program puts folders with plain {\TeX} files and miscellaneous other useful files supplied with the system on this list and asks for additional folders during installation. % Note the Û\\Û at the end of the entry for the Û\tex\baseÛ subfolders. % subdirectory. This invokes recursive subfolder search. That is, files in this folder % directory and {\it all\/} subfolders below it are included. % (typically Ûc:\yandytex\latexÛ). %% used when ini-TeX is run \endlist %%% what about format specific `TEXINPUTS' ??? \noindent By the way, \yandytex\ always searches the current directory % folder first when looking for input files, so there is no need to add `Û.;Û' to the list of folders % directories in ÛTEXINPUTSÛ. % \endlist \tip % Advanced Feature: If you have an environment variable with the {\it same\/} name as the current `format' % being used % you are using, then {\it its\/} value will be used by {\TeX} {\it instead} of the value of ÛTEXINPUTSÛ. % Hence variables named % ÛPLAINÛ, ÛLPLAINÛ, ÛLATEXÛ, and ÛAMSTEXÛ % are used instead of ÛTEXINPUTSÛ when you use % plain {\TeX}, {\LaTeX} 2.09, {\LaTeXe}, and {\AMS} {\TeX} respectively. % This is particularly convenient when two `formats' (such as {\LaTeX}~2.09 and {\LaTeXe}) use different style files with the same name % but quite different content. (which otherwise could be quite confusing!). You can, for example, have `format specific' environment variables named: \ulist \item \quad ÛPLAIN Û\quad folders with \TeX\ source files for plain {\TeX}; \item \quad ÛAMSTEXÛ\quad folders with \TeX\ source files for {\AMS} {\TeX}; \item \quad ÛLPLAINÛ\quad folders with \TeX\ source files for {\LaTeX} 2.09; \item \quad ÛLATEX Û\quad folders with \TeX\ source files for {\LaTeXe}. \endlist \noindent The names derive from the names % is because of the corresponding format files: % are called Ûplain.fmtÛ, Ûamstex.fmtÛ, Ûlplain.fmtÛ, and Ûlatex.fmtÛ. % respectively. Note that these `format specific' environment variables must {\it also\/} list the folders % directories containing your own \TeX\ source files --- as in ÛTEXINPUTSÛ --- since the list is used {\it instead\/} of the default % list provided by ÛTEXINPUTSÛ, rather than being appended to that list. Also note that ini-{\TeX} {\it does\/} refer to ÛTEXINPUTSÛ, since no formats are pre\-loaded when it runs. So should you ever have to use ini-{\TeX}, make sure that all the folders you will be referring to are listed in ÛTEXINPUTSÛ (or alternatively that all files needed are in the current directory where you run ini-{\TeX}). %% ini TeX refers to TEXINPUTS ... \ulist \item ÛTEXFONTSÛ\quad Where \TeX\ Û.tfmÛ metric files may be found (actually, typically an `encoding specific' variable will be used in stead of ÛTEXFONTSÛ --- see below). % The installation adds references to the appropriate directories. % the Û\fontsÛ subfolder % subdirectory % to this list. % The Û\Û after ÛfontsÛ invokes one-level down subfolder % subdirectory % search. % (see below). % TEXFONTS=c:\yandy\fonts\tfm;c:\yandy\fonts\Û % not needed if all Û.tfmÛ files are in subdirectories % of the default ÛfontsÛ subdirectory. \endlist \noindent The first folder in the ÛTEXFONTSÛ list is where new Û.tfmÛ files created by `WriteTFM\ellipsis' and {\AFMtoTFM} are deposited --- see section~3.7.2. It may also be where the Ûtexfonts.mapÛ font name aliasing file is found --- see section~3.7.3. \tip % Advanced Feature: If you have an environment variable with the {\it same\/} name as the current text font encoding, then its value will be used % by {\TeX} {\it instead} of the value of ÛTEXFONTSÛ. % This makes it easy to switch font encoding from `Fonts{\down}Encoding' in {\DVIWindo}. The default installation, for example, sets up % You can, for example, have `encoding specific' environment variables named: \ulist \item \quad ÛTEXNANSI Û\quad folders with {\TFM} files for {\TEXNANSI} (LY1); \item \quad ÛANSINEWÛ\quad folders with {\TFM} files for Windows ANSI; \item \quad ÛTEX256Û\quad folders with {\TFM} files for Cork (T1); \item \quad ÛTEXTEXTÛ\quad folders with {\TFM} files for TeX Text (OT1). \item \quad ÛSTANDARDÛ\quad folders with {\TFM} files for Adobe Standard Encoding. \endlist \noindent The following optional environment variables are {\it only\/} needed if files do not end up in the default places: \ulist \item ÛTEXFORMATSÛ\quad Where \TeX\ format files may be found; not needed if all Û.fmtÛ files are in the default Û\fmtÛ subfolder. % subdirectory. \vskip .05in \item ÛTEXPOOLÛ\quad Where \TeX's `string pool' file may be found; not needed if the file Ûtex.poolÛ (used only by ini-\TeX) is in the Û\fmtÛ subfolder. % subdirectory. % or tex.pool ... \vskip .05in \item ÛYANDYPATHÛ\quad Where the \yandytex\ System is installed. Some system components use this to find other system files. \endlist \noindent {\DVIPSONE} needs the following environment variable: % needs to know where the Type~1 outline font files (Û.pfbÛ) are kept: \ulist \item ÛPSFONTSÛ\quad Where Post\-Script Type~1 outline font files (i.e. Û.pfbÛ files) may be found. % It is Set to a semicolon-separated list of folders. % directories. The installation procedure normally figures out (from Ûatm.iniÛ, Ûatmreg.atmÛ, the registry, or the `font' folder) where Û.pfbÛ files are kept --- typically it is Ûc:\psfontsÛ or Ûc:\winnt\fontsÛ. % or Ûc:\winnt\fontsÛ. %% what if it is NT does it set it up for c:\windows\fonts ??? % In systems without {\ATM} this may instead be the Û\fontsÛ % subfolder of the ÛwindowsÛ or ÛwinntÛ folder. % This environment variable may not be set correctly if, by mistake, you install the system {\it before\/} installing any of the fonts. \endlist \noindent The following is needed only if you want to call an editor directly from {\TeX} when it hits an error % (that is, when (and you respond % with the choice ÛeÛ to {\TeX}'s error prompt). by typing `ÛeÛ' at {\TeX}'s error prompt). This is not used much, since it is % typically usually more convenient to just go back to the editor window that is already open. \ulist \item ÛTEXEDITÛ\quad A command-line string used when calling an editor from {\TeX}. % when it hits an error. This string may contain: Û%dÛ (replaced with the line number), Û%sÛ (replaced with the \TeX\ source file name), and Û%lÛ (replaced with the \TeX\ Û.logÛ file name), e.g., \beginlines ÛTEXEDIT=c:\yandy\WinEdt\WinEdt.exe [Open('%s');SelLine(%d,8)]Û, or ÛTEXEDIT=c:\yandy\pfe\pfe32.exe /g %d %sÛ, or ÛTEXEDIT="c:\Program Files\eps90\bin\epsilon.exe" +%d %sÛ \endlines \endlist % NOT: ÛTEXEDIT=c:\epsilon\bin\epsilon.exe %s +%dÛ % TEXEDIT=c:\tools\cmds\vi +%d %s % You need to use Û%%Û in place of Û%Û in a {\DOS} batch file... \noindent You can call for graphics inclusions (Û.epsÛ, Û.tiffÛ, Û.bmpÛ, or Û.wmfÛ files) using their fully qualified names --- as long as you replace Û\Û with Û/Û in the file name so as to avoid confusing {\TeX}. You can give just the file names --- without path --- if you set up the following environment variable: \ulist \item ÛPSPATHÛ\quad Semicolon-separated list of folders % directories in which inserted {\EPS} (Û.epsÛ) files, Post\-Script headers, {\TIFF} (Û.tifÛ) files, {\BMP} (Û.bmpÛ) files, and Windows Meta\-Files (Û.wmfÛ) are searched for. The installation program asks for the folders in this list. % and adds to TEXINPUTS directories... \endlist \noindent Note that if your figure inclusion macros also make {\TeX} read the {\EPS} files to extract bounding box information, then the directory with {\EPS} should {\it also\/} be appended to your ÛTEXINPUTSÛ environment variable --- or rather the corresponding `format specific' environment variable. %% move following to technical addendum ??? % \TeX\ normally writes its output files in the current directory. If you % want to redirect them, then set the following environment variables: % \ulist % \item ÛTEXDVIÛ\quad Set only if you want \yandytex\ to redirect % Û.dviÛ file output. If defined, {\DVIWindo} looks for Û.dviÛ files % to `Preview' in this directory rather than in the `TeX' menu default. % \item ÛTEXLOGÛ\quad A directory for Û.logÛ files. % \item ÛTEXAUXÛ\quad A directory for Û.auxÛ files. % \endlist % advanced stuff ? %% flush following ? banish to Technical Addendum ??? % Sometimes it is convenient to redirect specific types of files % produced by {\TeX}. % % You can use the environment variables % ÛTEXDVIÛ, ÛTEXAUXÛ, and ÛTEXLOGÛ to redirect % Û.dviÛ, Û.auxÛ, and Û.logÛ files respectively % (If ÛTEXDVIÛ is set, {\DVIWindo} will look for Û.dviÛ % files in the specified directory). % following is somewhat optional - also maybe in an odd place. % advanced stuff ? Discussed earlier % Different {\TeX} `formats' typically work with different style files. % This may lead to conflicts between style files % that have the same % with the same names % but are % designed for different formats. % In this case, it is convenient to have a different list of directories % when different \TeX\ formats are used. % \tip % Advanced Feature: % If \yandytex\ finds an environment variable with a name equal to that of the % format selected on the command line, then it will use the value of % {\it that\/} variable instead of the default ÛTEXINPUTSÛ. % So you could, for example, have environment variables named: % moved earlier % \noindent % which list directories with style files for % plain {\TeX} (Ûplain.fmtÛ), \LaTeX\ 2.09 (Ûlplain.fmtÛ) and \LaTeXe\ % (Ûlatex.fmtÛ), respectively. % This is because % the corresponding format files are called % Ûplain.fmtÛ, Ûlplain.fmtÛ, and Ûlatex.fmtÛ, respectively. The variable ÛENCODINGÛ specifies the font encoding (character layout) for non-CM text fonts. This is initially set during installation and can be changed using `Fonts{\down}Encoding' in {\DVIWindo}. the default % on systems with {\ATM} is `ÛtexnansiÛ' --- for {\TEXNANSI} (LY1) encoding (see section~6 for detailed character layout): %% section? \beginlines ÛENCODING=texnansiÛ \endlines % \noindent % In a Windows NT system running without {\ATM} % the ÛENCODINGÛ environment variable should {\it not\/} be set % since % (i) TrueType fonts cannot be reencoded and (ii) TrueType text fonts are % set up for `Windows ANSI' encoding. % $In this case ÛTEXANSIÛ should be set to 1 as described % $next. % in the following. % The above refers to an encoding vector file Ûtexnansi.vecÛ in the % directory specified by ÛVECPATHÛ (see below). %% section? % % If you do use `texnansi' encoding, then you should also add a line % of the form Û\input texnansiÛ to your {\TeX} source file. % Do the above in more detail somewhere else? % The following will be set to Û1Û if you % {\it instead\/} % indicated during installation that you want % to use Windows {\ANSI} (ÛansinewÛ) encoding --- % as is appropriate for a Windows NT system without {\ATM}: % \beginlines % ÛTEXANSI=1Û % \endlines % \noindent % The above is required if you use plain text fonts with Windows {\ANSI} % encoding in {\DVIWindo}. % and other Windows applications. % Windows {\ANSI} (Ûansinew.vecÛ) is the default character layout used by % Windows applications. % Windows and % most % % If you do use `ansinew' encoding, then you should also add a line % of the form Û\input ansiacceÛ to your {\TeX} source file. % The environment variables ÛENCODINGÛ and ÛTEXANSIÛ are mutually % exclusive --- use one {\it or\/} the other, not both. % % Also note that the environment variable ÛTEXANSIÛ % has nothing to do with `texnansi' encoding --- % it's an unfortunate historical accident that the names are so similar. % Sorry about that! % of near coincidence in spelling\ellipsis % \ldots % % For additional details please refer to section~6, % `Font Encoding and Character Layout.' %% What to do if you change encoding ??? \noindent Note that if you change the ÛENCODINGÛ environment variable, TFM metric files will be taken from a different place as dictated by `encoding specific' environment variables. Installation sets up parallel trees of folders with TFM files for this purpose. % you must {\it also\/} change the Û.tfmÛ {\TeX} metric files to the ones % appropriate for that encoding (see section~3.7.1). % ??? The following optional environment variables are {\it only\/} needed if files do not end up in the standard places: \ulist \item ÛVECPATHÛ\quad Where encoding vector files may be found. The default is the Û\fonts\encodingÛ subfolder. % subdirectory. % {\DVIWindo} uses the ÛVECPATHÛ variable to find encoding vector files % when you select `Write TFM\ellipsis' or `Write AFM\ellipsis' in the `Fonts' % menu. % (See section on `Font Encoding' for additional details). %% section? % \endlist \endlist % What about Write All TFMs... ??? \noindent {\DVIWindo} uses the ÛVECPATHÛ variable to find the encoding vector specified by the ÛENCODINGÛ environment variable, % well isn't that just the same ??? we can no longer choose ... as well as encoding vector files needed when you select `Write TFM\ellipsis' or `Write AFM\ellipsis' in the `Fonts' menu. % and `Write All AFMs\ellipsis' and `Write All TFMs\ellipsis' ... % (See section on `Font Encoding' for additional details). %% section? % % {\DVIWindo} also uses ÛVECPATHÛ when it looks for the encoding vector % specified by the ÛENCODINGÛ environment variable. % \noindent % An encoding vector file is a plain {\ASCII} file that gives the mapping % from character codes (in the range 0--255) to glyph names. % % We recommend the `texnansi' encoding vector since it provides access to % all 228 glyphs in plain text fonts, yet matches most of the hard-wired % assumptions that {\TeX} makes about where accents and various special % characters appears in the character layout. \ulist \item ÛSUBPATHÛ\quad Where font substitution files may be found. The default is the Û\dvipsone\subÛ subfolder. % subdirectory. % (or its ÛsubÛ subdirectory) \endlist \noindent A font substitution file can, for example, be used to let {\DVIPSONE} know which fonts are printer resident (so it won't include them in the Post\-Script output). The standard substitution file (read when you do not explicitly specify a font substitution file on the command line) is called Ûstandard.subÛ and lists Times-Roman, Helvetica, Courier, % and Symbol, and Zapf Dingbats as printer resident. Refer to the Technical Addendum for more esoteric uses of font substitution files. % (see later for details). %% section? technical addendum ? % refer them to DVIPSONE manual ? \ulist \item ÛPREPATHÛ\quad Where {\DVIPSONE} % (and ÛPKtoPSÛ) preamble files may be found. The default is the Û\dvipsoneÛ subfolder. % subdirectory. \endlist % also for PKtoPS %%% dvipsone.bat ??? \noindent {\DVIWindo} adds the `Use DVIPSONE' checkbox to the `Print' dialog box only if it can find {\DVIPSONE}. % Ûdvipsone.exeÛ. % {\DVIPSONE}. {\DVIWindo} looks for {\DVIPSONE} along the % {\DOS} ÛPATHÛ (set in Ûautoexec.batÛ in Windows~95/98 and from `Control Panel{\down}System{\down}Environment' in Windows~NT). % Ûautoexec.ntÛ) % ??? and in the default folder. If this fails, it tries to find {\DVIPSONE} in the folder specified in ÛPREPATHÛ. % (as well as ÛVECPATHÛ). So if the `Use DVIPSONE' check box is missing, try setting ÛPREPATHÛ % (or ÛVECPATHÛ) to the folder % directory where {\DVIPSONE} may be found. % See below for a description of these environment variables. %% section? % {\DVIWindo} also uses ÛVECPATHÛ when it looks for the encoding vector % specified in the {\sc encoding} environment. % following is somewhat optional ? % Note that it is possible with some software to write ``scripts'' that can % edit Ûdviwindo.iniÛ; this may be more convenient than using % {\DOS} environment variables and Û.batÛ files. \subsub{The [Window] section of dviwindo.ini} % The other part of Ûdviwindo.iniÛ that may be of occasional interest is the Û[Window]Û section, which stores preferences and state information. % other useful information. % \noindent \TeX\ normally writes all of its output files in the `current directory.' When called from {\DVIWindo}, the current directory will be {\it either\/} % that {\TeX} has been asked to process \beginlines (i) the directory of the {\TeX} source file, {\it or\/} (ii) the common working directory, \endlines \noindent all depending on whether you elected to specify a working % common directory during installation (see installation instructions % for {\DVIWindo} --- section~2.4). %% check section ??? % % The working directory % folder % selected during installation is recorded % in the ÛWorkingDirectoryÛ entry in the Û[Window]Û % section of Ûdviwindo.iniÛ. % Note that this is % ({\it not\/} the Û[Environment]Û section). % and can be changed there. The working directory selected during installation is recorded in the ÛWorkingDirectoryÛ entry in the Û[Window]Û section. If you do not want to use a common working directory remove this line or comment it out using a semicolon (;). Conversely, to use e.g. Ûc:\workingÛ as a common working directory add \beginlines ÛWorkingDirectory=c:\workingÛ \endlines \noindent to the Û[Window]Û section. % You can also temporarily toggle the `Working Directory' option using % `Fonts{\down}Working Directory' `Special{\down}Working Directory' in {\DVIWindo}. If applications called from the `TeX Menu' cannot handle file names with backslash (\char92) then add \beginlines ÛDeslash=1Û \endlines \noindent to the Û[Window]Û section. This requests that {\DVIWindo} convert Û\Û to Û/Û on the command line before % when calling other applications. You can control command line arguments passed to {\yandytex}, {\DVIPSONE}, and {\AFMtoTFM} using `Preferences{\down}Command Line' in {\DVIWindo}. This information is recorded in the ÛWindowÛ section of Ûdviwindo.iniÛ. % also makes it possible to pass command line arguments to {\DVIPSONE}, % {\yandytex}, and {\AFMtoTFM} when called from {\DVIWindo}. The values associated with the keys ÛDVIPSONEÛ, ÛTeXÛ, and ÛAFMtoTFMÛ defined in the Û[Window]Û section record this information. For example: \beginlines ÛTeX=-w -jÛ % -j \endlines \noindent % tells {\yandytex} to truncate long file names to {\DOS} 8+3 % file name convention. tells {\yandytex} to show accented characters on screen and in the log file instead of coverting them to hexadecimal notation. % You can also use this line to change exactly {\it what\/} is called. For example, to call Ûdvipsone.batÛ, with command line argument Û-vÛ, instead of Ûdvipsone.exeÛ when printing use \beginlines % ÛDVIPSONE=dvipsone.bat -vÛ ÛDVIPSONE=c:\yandy\dvipsone\dvipsone.bat -vÛ \endlines % \noindent (this assumes % assuming % that Ûdvipsone.batÛ is somewhere on your path). % The Û[Applications]Û section of Ûdviwindo.iniÛ % contains the `TeX' menu and is discussed in the section % on {\DVIWindo} below. % section~3.3 % \subsect{\yandytexBold} \subsect{DVIWindo} % If you're viewing a Û.dviÛ file, and use the `TeX' menu (or a hot key) to `re-{\TeX}' the corresponding source file, you will find that the preview is automatically refreshed as soon as {\TeX} finishes running. The page number, zoom factor, and viewing position are all preserved (unless, of course, you happen to be looking at a page that disappeared because of changes in the source file). % If another window has the focus at this point, simply click on a visible part % corner of the {\DVIWindo} window to get its attention. Alternatively hit \ang{Alt-Tab} repeatedly. % until {\DVIWindo} has the focus again. % (if the number of pages has changed, this may not be true). % Alternatively, click on a visible corner of the {\DVIWindo} window, % or hit \ang{Alt-Tab} until you are there. % once or twice and 'll be % While {\DVIWindo} does not come with a traditional Windows Help file, % it does have Ûdvi_help.dviÛ --- a Û.dviÛ file with hypertext links % created by Dr. Donald P. Story. Installation sets up an icon for this file. % You can also call it from the `TeX' menu. {\DVIWindo} comes with a help file % (written in \TeX) that exploits {\DVIWindo}'s support for color and hypertext links. This file --- Ûdvi_help.dviÛ --- was kindly provided by Dr. Donald P. Story of the University of Akron. % {\DVIWindo} installation sets up an icon for this file. % Just double-click on this icon Just hit the F1 function key % (or select `TeX{\down}Help') (or select `Help{\down}Help') while in {\DVIWindo} to see the first page, which has an explanation of how to use the help file. %%% Or from the `Help' menu ??? \subsub{Mouse Tricks and Accelerator Keys} % Most operations in {\DVIWindo} are easily discovered % assimilated % discovered as you work with it, since they are listed as menu items. % accessed via menu items. There are, however, `mouse tricks' % and several accelerator keys (hot keys) % worth noting here, that may not be immediately apparent, since they do not appear in the menus, as well as accelerator keys (hot keys) that you may have missed. Three of the `mouse tricks' depend on defining a rectangular area. In each case, the top left corner is fixed when you first press the left mouse button. You extend the rectangle by dragging the mouse while holding the left mouse button --- the mouse controls the right bottom corner. The rectangle can be moved --- instead of resized --- if you {\it also\/} hold down the {\it right\/} mouse button. % you can reposition the whole rectangle without changing its shape. The final shape and position of the rectangle is the one in effect when you release the left mouse button. The % actual action taken when you define the rectangle depends on which combination of `Shift' and `Ctrl' keys are held down when you first press the left mouse button. \blist \item You can create a `Zoom In' rectangle by holding down the `Ctrl' key and using the mouse to define a rectangle as explained above. The aspect ratio of the rectangle in this case is constrained to be the same as that of {\DVIWindo}'s window. % that The rectangle % region shown % is what will be blown up to fit into the window when you finally release the left mouse button. % to zoom in Later, you can click the {\it right\/} mouse button to undo the `Zoom.' \item You can create a `Ruler' rectangle % in a similar fashion by holding down the `Shift' key instead. This is useful for measuring % horizontal and vertical distances. You may want to zoom in first if you want to make accurate % fine measurements. Go to `Preferences\ellipsis{\down}Ruler Units' to select the ruler units. (Note that this feature is disabled when the `Fonts Used' list is showing.) \item You can also create a `Copy' rectangle defining a rectangular region to be copied to the Windows clipboard by holding down {\it both\/} the `Shift' and `Ctrl' keys. % while defining a rectangle using the mouse. The material copied may be pasted into other Windows applications, and positioned, sized and clipped there. This is a convenient way to insert mathematics typeset using {\TeX} into typical {\sc wysiwyg}-type applications. % (Note that this feature is disabled when the `Fonts Used' list is showing.) \item You can reposition the page in the window simply by holding down the `Alt' key and the left mouse button. % and moving the mouse allows you to position the page on the screen. Just drag the page around by moving the mouse. \item You can refresh the display --- should it ever become corrupted --- % by double clicking on the window. by hitting the `Enter' key. % changed \item Space and Backspace move forward and backward a % one page, keeping the current zoom factor and position on the page. \item `PgDn' goes to the top of the next page. `PgUp' goes to the bottom of the previous. % page. \item The `Home' and `End' keys take you to the beginning and the end of the current page respectively. \item The `Ctrl-Home' and `Ctrl-End' keys take you to the beginning and the end of the file respectively % or use |<- and ->| (or use Û|<-Û and Û->|Û). \item You can move to a new page by typing in a page number --- using the top row of the keyboard --- and then hitting the \ang{Enter} key. % return. % \item The numeric keypad's Û+Û and Û-Û zoom in and out one step. % \item The numeric keypad's + and - zoom in and out one step. % respectively. \item Ctrl+R opens the `Find' dialog box; % Ctrl+S repeats the previous search. % You can close the `Find' dialog box after the first search, you can check a box to close the `Find' dialog box after the first search, yet continue using Ctrl+S, which repeats the previous search. % we don't say much about search in DVI files ... should we? \item \ang{Ins} % `Ins' (from the numerical keypad) closes the current file (if any) and opens the `File Open' dialog box. Note that % when you start, you can quickly go back to the file you last viewed, % when you last exited {\DVIWindo} last, by double clicking on the {\DVIWindo} icon, hitting \ang{Ins} and then \ang{Enter}. \item \ang{Del} % `Del' closes the view of the current Û.dviÛ file. \item \ang{Esc} % `Esc' pops you out of {\DVIWindo} --- unless some % modeless --- remove or explain dialog boxes are being shown, in which case these are removed instead. % first. \endlist %%%% Should we discuss here color fonts, DVI Fonts List etc ? %%%% Ctrl+F goes to `Show Fonts' %%%% Ctrl+X toggles `color font' %%%% Shift click on character while `DVI Fonts Used' shows %%%% look in dvi_help for more `mouse tricks' ??? \noindent These commands cover the bulk of day-to-day use of {\DVIWindo}. % For the other features of the program (such as controlling color and viewing % {\TIFF}s and {\EPS} previews), please see the Technical Addendum. %% Does the following eliminate the need for the `TeX Menu Manual' ? \subsub{Customizing the `TeX' Menu} % The `TeX' menu is the `control center' or `shell' from which {\TeX} and other applications are called. The installation of the \yandytex\ System sets up a useful % initial `TeX' menu, but you may want to add entries, or modify existing entries. % To do this, hold down the `Ctrl' key before selecting an item from the menu. You can then \ulist \item (i) edit and replace an existing entry (select `Replace'), \vskip .05in \item (ii) add a new entry {\it after\/} the item selected (select `Add'), \vskip .05in \item (iii) add a separator line after the item selected (select `Separator'), \vskip .05in \item (iv) delete the item selected (select `Delete'), or % or \vskip .05in \item (v) delete the item {\it after\/} the item selected (select `Delete Next'). \endlist \noindent The last mentioned capability is useful for removing menu separator lines, since separators themselves cannot be selected. % directly The menu is organized as a series of `key=value' pairs. The key is the `Menu Item Name' that appears in the `TeX' menu, while the value is the `Application Call Pattern' that will be executed in response to selection of that key from the menu. % The first menu item is hard-wired to `Preview' the Û.dviÛ file corresponding to the last file {\TeX} source file selected. % for editing or processing using {\TeX}. As indicated before, this menu item is rarely used, since in most cases that Û.dviÛ file is already being displayed. % Usage with Borde & Rokicki's TeX Help ... Each menu item may be associated with a `hot key.' Hot keys can be function keys (written F1--F12), or function keys with the `Ctrl' key also held down (written C-F1--C-F12). The hot key designation follows the menu item name, with a vertical bar ($\,$|$\,$) used as a separator. Note that F1 is hard-wired for `Help,' C-F1 for `Preview.' and Windows reserves F10 --- which is equivalent to `Alt,' and in some versions of Windows --- and some laptops --- F11 and F12 are % also not available. % % The default hot key for `Preview' is C-F1. % The `value' associated with a `key' The `Application Call Pattern' can be any command line that calls % a {\DOS} or Windows program. a Windows program, console application or batch file. % (or {\DOS} program). Obviously, such a facility would be of limited utility if only a {\it fixed\/} string could be used, but simple string replacements on the `value' part provide added power: % added flexibility: % First of all, Reference can be made to any environment variable using the notation Û%Û\angi{env var name}Û%Û. % Second, an Û*Û (asterisk) is replaced with the name of the currently open Û.dviÛ file --- {\it sans\/} extension, or path. Third, % a semicolon-separated list of directories followed by the pattern \angi{list of dirs}Û#Û\angi{file name} % a Û#Û (number sign) and a file name triggers a search. % for the file in the listed directories. If a file with name \angi{file name} is found in one of the folders % directories in the semicolon separated list, then the full path name of that file replaces the pattern. % The resulting full path then replaces the % list of directories, the Û#Û, and the original filename. This is handy, since it makes it easy, for example, to insert the full path name of the {\TeX} % is not always trivial to locate the {\TeX} source file corresponding to the currently open Û.dviÛ file. This is no mean task, since it can be in any one of the folders % directories listed in ÛTEXINPUTSÛ. % Following the above rules, it is clear that {\DVIWindo} will search for that file in the list of source folders if the notation Û%TEXINPUTS%#*.texÛ is used. % Since this is such a common construction, Û@.texÛ is accepted as a shorthand notation for Û%TEXINPUTS%#*.texÛ. %% big question: is TEXINPUTS replaced with format specific ??? The pattern Û"Û\angi{arg name}\char124\angi{default value}Û"Û is replaced by text you are prompted to supply when the pattern is activated. The string \angi{arg name} appears in the title bar of a dialog box to indicate what information is requested, and \angi{default value} (if present) is offered as the default value. % also \angi{dir}Û?Û\angi{.ext} Now let us suppose that you would like to use the `xyz' editor, which lives in the Ûc:\xyzdirÛ folder; % directory; you want it attached to hot key Ctrl+F5, and this editor takes Û-vÛ and the file name as arguments on the command line. If you want the new entry to appear % in the `TeX' menu after the one for `Notepad,' hold down the `Ctrl' key and click on `Notepad' in the `TeX' menu. Then enter ÛXYZ|C-F5Û for the `Menu Item Name' (key), and Ûc:\xyzdir\xyz.exe -v @.texÛ for the `Application Call Pattern' (value). Then click `Add.' %% redundant ??? A file name inserted in the application call pattern normally uses Û\Û (backslash) as separator. Some applications cannot handle file names with backslashes. Add `ÛDeslash=1Û' to the Û[Window]Û section of Ûdviwindo.iniÛ to force {\DVIWindo} to convert % backslash to slash on the command line. Û\Û to Û/Û on the command line. Typically {\TeX} `formats' are listed last in the `TeX' menu. This makes it easy % for ini-{\TeX} to append a new format when you create it. % Assuming Û[Applications]Û section is last in dviwindo.ini Of course, you can insert new formats anywhere in the menu simply using an application call pattern of the form: \beginlines Ûc:\yandy\yandytex\tex.bat +Û\angi{format file name}Û @.texÛ \endlines % Ûtex.bat +Û\angi{format file name}Û @.texÛ \noindent Note the use of `+' as an alternative to `\&' before the format name --- this prevents problems in Windows~NT where ampersand on the command line is interpreted by the system as a command separator. The above refers to the batch file Ûtex.batÛ created during installation. % of \yandytex. Calling a batch file from the `TeX' menu rather than calling an application directly offers the opportunity to control what happens before the application is run, and what happens after it terminates. Also note that {\PIF} files can control execution of % {\DOS} programs in Windows. % console applications batch files (and {\DOS} programs). {\PIF} files can be used, for example, to specify whether the application will run full screen or windowed. The installation procedure copies convenient {\PIF} files for {\DVIPSONE} and \yandytex. You can edit these, or create new {\PIF} files for other applications by right-clicking on the batch file and selecting `Properties.' % ??? Altogether then there are three ways to control execution of an application called from the `TeX' menu: \beginlines (i) in the `Application Call Pattern' itself, (ii) in a batch file called from the `TeX' menu, and (iii) by using a {\PIF} file with the same name as the batch file. \endlines \noindent % (or the batch file). % % flush reference to DOS box ??? % Finally, note that you can even select the fonts used in a windowed {\DOS} box by clicking on the `System Menu' of the box, and selecting `Fonts...'. Windows remembers the selection you have made for use in future {\DOS} boxes with the same title. If details of the `TeX' menu still appear a bit % seems mysterious, check out the entries created by the installation program to see how these work. % in practice. Just hold down the `Ctrl' key, click on a menu item, and after inspecting it, click `Cancel' (unless you actually want to change it!). \subsub{The [Applications] section of dviwindo.ini} % Note that while the `TeX' menu can be edited directly from {\DVIWindo}, it is also possible to alter it by editing the Û[Applications]Û section of the file `Ûdviwindo.iniÛ. This may be useful should the `TeX' menu ever get seriously corrupted. Each line in the Û[Applications]Û section is of the form `Ûkey=valueÛ.' A typical entry might be \beginlines ÛLaTeX 2e|F8=tex.bat +latex @.texÛ \endlines \noindent Note that `TeX' menu entries can % also be used to transfer focus to another window --- as opposed to launching a new Windows or console application. Use Û$Window(Û\angi{window title}Û)Û for this. To transfer to the `Notepad' window, for example, % you may use a key-value pair of the form % Û-> Notepad|C-F2=$Window(Notepad...)Û \beginlines Û-> Notepad|C-F2=$Window(...Notepad)Û \endlines \noindent The ellipses (Û...Û) indicate that the window title need not match the the given text in its entirety, but may have additional characters before `Notepad.' % initial part of the window title, which may contain additional characters. Conversely, if the ellipsis appears {\it after\/} the word `Notepad', then the given text need only match the initial part of the window title. This is handy because title bars often contain not only the application name, but also the name of an open file. % opened by that application. Of course, you get an error message when there is no such window. Here we have chosen to use Û->Û as the initial characters in the `key.' This is {\it not\/} in any way interpreted by {\DVIWindo}, but {\it is\/} a useful mnemonic device to mark entries in the `TeX' menu that merely transfer focus to an existing window --- as opposed to launching a new copy of the application. % additional features of `TeX' menu ??? % compare with TeX Menu manual ??? Can we flush that one now ??? \subsect{\yandytexBold} % You can run \TeX\ (or \LaTeX, or what you will) from the `TeX' menu in {\DVIWindo} by choosing the appropriate menu item using the mouse, % option. or by pressing the associated `hot key.' % function key You will also have batch files Ûtex.batÛ, Ûlatex209.batÛ, and Ûlatex.batÛ in the Û\yandytexÛ % or Û\utilÛ subfolder. % subdirectories. %%% check with final installation decision ??? As a test, type Ûc:\yandy\yandytex\tex -?Û at the command prompt (you would need to adjust this command if you installed in a different directory than the default Ûc:\yandyÛ). You should get a short command line summary from \yandytex. % If instead you get a `Bad command or file name' complaint, % from {\DOS}, % then copy Ûtex.batÛ and Ûlatex.batÛ % from your Û\yandytexÛ subdirectory %%%% where ??? %%%% and does it install the correct file ??? % to a directory that {\it is\/} on your ÛPATHÛ. % (if necessary, create a directory called Ûc:\batÛ, % and add that to the ÛPATHÛ statement in Ûautoexec.batÛ). To make it more convenient to use these batch files, you may want to add the folder % directory % they are in to your ÛPATHÛ --- as defined in Ûautoexec.batÛ in Windows~95/98, and from `Control Panel{\down}System{\down}Environment' in Windows~NT. Alternatively, copy the batch files to a folder % directory that is already on your ÛPATHÛ. % (such as the Windows folder). % directory). % but do not delete the original versions since these are called from menu... %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Note that \yandytex\ is {\it exactly\/} the same as the standard \TeX\ described in {\sl The \TeX book} when it comes to the {\it language\/} implemented (except that it is version 3.14159, while the book describes version 3.0). \yandytex, however, does have quite a few added capabilities such as dynamic memory allocations, more detailed log file output, % in certain situations, capabilities for dealing with `foreign' language keyboards, and other extensions controlled by command line flags. Use Û-?Û on the command line to list commonly used command line options. Please refer to the Technical Addendum (or Ûreadme.txtÛ in Û\yandytexÛ subfolder and Ûcommflag.txtÛ in Û\doc-miscÛ subfolder) % subdirectory) %%% is there such a file ??? for additional extensions and optional command line arguments. %%% discuss keyboard.txt ??? If {\TeX} hits an error while processing your source file, it will stop and ask you for a response. Type `Û?Û' % at this point to see a list of options available to you at that point. Typically it's easiest just to hit \ang{Enter} and let {\TeX} continue. If you start to see too many errors (sometimes a single mistake triggers an avalanche of error messages), type `ÛxÛ' instead in order to escape. If you have set up the environment variable ÛTEXEDITÛ you also have the option of using `ÛeÛ' to call your editor. %% refer to previous section? %% section? % `Please type another file name' When {\TeX} is looking for a file that it can't find, it will ask you to `ÛPlease type another file nameÛ.' % ask you for a new file name. If the file does not exist and there is no appropriate substitute, then one option you have is to type ÛnulÛ. {\TeX} will then read an empty file --- which in some cases may be appropriate (or at least keep it going a bit longer). % If you want to stop processing instead, type Ctrl+Z. This will cause {\TeX} to perform an `Emergency Exit.' This is a handy trick to know, since otherwise you may find yourself at some time stuck in an annoying --- seemingly endless --- loop with {\TeX} asking you again and again for a file name\ellipsis The window in which {\TeX} is running when {\TeX} is called from {\DVIWindo} will persist if an error occurs. %%% check tex.bat as installed %% once we have the batch file fixed up ??? This is so that you can read the error information at your leisure. To dismiss the Window % when you are through looking at it, type any character while that window has the focus. % to make it disappear. % to make the window disappear. In rare cases the {\TeX} window disappears before one can tell what the problem is. In this case temporarily check % `Fonts{\down}Pause WinExe' `Special{\down}Pause WinExe' in {\DVIWindo} before calling {\TeX}. You may find % `Fonts{\down}Show WinExe' `Special{\down}Show WinExe' useful as well --- it shows you exactly how {\DVIWindo} is calling {\TeX}. You may also wish to look at the Û.logÛ file for more detailed error output. The Û.logÛ file is a plain {\ASCII} text file with the same name as the output Û.dviÛ file, but extension Û.logÛ. {\TeX} writes the Û.logÛ file in the same place as the Û.dviÛ file. % unless you redirected output... % (or in the location specified by the ÛTEXLOGÛ environment variable). %% see section 2.7 ???? If you would like to use certain command-line options every time {\TeX} % }\yandytex\ is called from {\DVIWindo}, use `Preferences{\down}Command Line.' % then add a line to the % an entry % Û[Window]Û section of Ûdviwindo.iniÛ of the form % ÛTeX=Û\angi{command line options}. Curiously, % Confusingly, {\TeX} itself interprets the command line, and to {\TeX} anything starting with Û\Û (backslash) is considered to be a {\TeX} `control sequence.' To avoid problems with % {\DOS} file names that have backslashes, \yandytex\ % automatically converts backslashes to slashes in file names % (and format names) and format names. % on the command line. % (unless you use the command line flag Û-dÛ). % You can also ask {\DVIWindo} to do the translation. % Deslash=1 [Window] section In Windows~95/98, files with long names also have short names constructed by omitting parts of the name and replacing it with \char158. One can use either the long or the abbreviated name to access a file. These `tilde' characters in short file names could, however, % potentially create havoc when interpreted by {\TeX}, so \yandytex\ transparently replaces them with something benign. % else. Note that {\TeX} itself {\it cannot\/} deal with file names that contain spaces. If you do need to use such file names, enclose them in double quotes (Û"Û). However, we do {\it not\/} recommend using names --- or paths --- that contain spaces. For additional details please refer to Technical Addendum (or the Ûreadme.txtÛ file Û\yandytexÛ folder and Ûcommflag.txtÛ in Û\doc-miscÛ subfolder) % subdirectory) % directory). % following redundant ??? You can also use \yandytex\ from the % {\DOS} command prompt by typing % ÛtexÛ \angi{filename} Ûc:\yandy\yandytex\texÛ \angi{filename} and pressing \ang{Enter}. % (You may need to enter the full path, e.g. Ûc:\yandy\yandytex\texÛ % if the batch file is not on your ÛPATHÛ). Use Û-?Û instead of a filename to see a usage summary of the most common command line options that \yandytex\ accepts. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Uncheck Working Directory when running ini-TeX ???? %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \subsub{Making new {\TeX} formats --- running ini-{\TeX}} % A `format' file (like Ûplain.fmtÛ) is a kind of dump of {\TeX}'s state of mind after reading the definition for a particular dialect of {\TeX} (such as plain {\TeX}). It is typically faster to load such a format file than to read the {\TeX} source code defining the format (although, these days, the time taken to load these files is quite short). \yandytex\ comes with ready made `format' files for plain {\TeX}, {\AMS}-{\TeX}, {\LaTeX} 2.09 and {\LaTeXe}. Consequently, you do not normally have to create new `formats' However, should you ever need to create new formats, run `ini-{\TeX}.' The preferred way % Probably the easiest way to create a new format is to run {\yandytex} using Û-iÛ on the command line from the command prompt (see below). You can also create formats directly from the `TeX' menu by selecting the `ini TeX' menu item. For example, to create the \LaTeX\ 2.09 format file, you could select `ini TeX' % ÛiniTeXÛ from the `TeX' menu and type ÛLaTeX 2.09Û for the `TeX' menu name (adding any hot key desired following a vertical bar as separator). Click `OK.' Then type ÛlplainÛ\ang{Enter} for the source file name in the field that pops up. Click `OK.' The required files Ûlplain.texÛ, Ûlfonts.texÛ, and Ûlatex.texÛ are in the Û\tex\latex209Û subfolder. % The required {\TeX} source files defining this format % are in the Û\latexÛ subfolder % subdirectory % of the Û\texÛ subfolder, % subdirectory, % and this folder either should be the current folder, % or it should be be on the list of folders % directories Clearly that folder should be listed in the ÛTEXINPUTSÛ environment variable so that {\TeX} can find the files if this approach is used, since ini-{\TeX} ignores `format specific' environment variables, and always refers to ÛTEXINPUTSÛ. % One convenient approach is to temporarily redefine the % `Working Directory' to be the directory with the source files, % by {\it unchecking\/} `Fonts{\down}Working Directory' % if it happens to be currently checked. %%% Mention change of Working Directory check mark here ??? Note that with some formats you need to explicitly type Û\dumpÛ when {\TeX} returns to the '*' prompt, while other formats may already include that command in the source code. In some cases (like {\LaTeXe}) creation of new format files may be more involved --- e.g. requiring two runs of {\TeX}. % You may find it easier to handle this from the command prompt. This is easier from the command prompt. % Note that `ini-{\TeX}' is nothing more than `{\TeX}' with the command line flag Û-iÛ. To create a new format for \LaTeXe, using this approach, switch to the folder that has all of the {\LaTeXe} base files % (typically Ûc:\yandy\tex\latexÛ). % (typically Ûc:\yandy\tex\latex\baseÛ). (typically Ûc:\yandy\tex\latex\unpackedÛ). These files may be the latest versions downloaded from {\CTAN} ({\LaTeXe} is presently updated every 6 months). % First run {\TeX} ({\it not\/} ini-{\TeX}) % or \LaTeXe) on the file Ûunpack.insÛ (which in turn reads Ûunpack.dtxÛ and other files). For example: %% need for recent version of docstrip.tex ??? \beginlines Ûcd c:\yandy\tex\latexÛ % Ûtex -v unpack.insÛ Ûc:\yandy\yandytex\tex -v unpack.insÛ \endlines % \noindent % If Ûtex.batÛ is not on your ÛPATHÛ you need to give the % fully qualified name Ûc:\yandy\yandytex\texÛ instead. % You will also need to adjust the folders if you installed % in other than the standard Û\yandyÛ folder. % \noindent After a minute or so, two or three hundred files will have been created. % At that point, run ini-{\TeX} on the file Ûlatex.ltxÛ. Then move the resulting Ûlatex.fmtÛ format file to the folder % directory specified in the environment variable ÛTEXFORMATSÛ. For example: \beginlines % Ûtex -v -i latex.ltxÛ Ûc:\yandy\yandytex\tex -v -i latex.ltxÛ Ûmove latex.fmt c:\yandy\yandytex\fmtÛ \endlines \noindent Also make sure that the other new files created by the `unpacking' process reside in a folder listed in % ÛTEXINPUTSÛ --- or rather the `format specific' environment variable ÛLATEXÛ. This happens automatically if you `unpack' the packed distribution % from CTAN % in Ûc:\yandy\tex\latexÛ. % in Ûc:\yandy\tex\latex\baseÛ. in Ûc:\yandy\tex\latex\unpackedÛ. % the following should really be more general and appear elsewhere ??? Finally, to add a {\it new\/} format file to the `TeX' menu, select the menu, hold down the `Ctrl' key and click on an entry in the bottom portion of the menu (for example, the one for % ÛLaTeXÛ). %% ? {\LaTeX} 2.09. A dialog box will pop up. Make the changes necessary to make your new format file work (e.g. replace Û+lplainÛ with Û+latexÛ), being sure to give the `key' a unique name, and to associate it with a unique function key (if you wish to use that handy shortcut), and then click on `Add.' Refer to section~3.3.2 on customizing the `TeX' menu for additional details. Equivalently, you can edit the Û[Applications]Û section of Ûdviwindo.iniÛ directly using `Notepad,' `WordPad,' `WinEdt' or {\PFE}. %%% give section number ??? % not needed for existing formats. \subsub{`Foreign' Language Keyboards --- Accented Characters} % If you are a typical mono-glottal English speaker you can ignore this! % spelling ??? Many languages use accented characters, composite characters, or special characters. There is, of course, a standard notation in {\TeX} to access such characters. For example, Û\"aÛ yields `\"a', Û\c cÛ yields `\c c', and Û\aeÛ yields `\ae.' But it is more convenient to represent these characters using a {\it single\/} character code in the file, as we do for `ordinary' alphabetic characters. With {\yandytex} you {\it can\/} type these characters directly from the keyboard and use the resulting {\TeX} source file as is. % There are three cases to consider: \nlist \item Normal text fonts (i.e. {\it not\/} Computer Modern) --- font encoding matches keyboard character codes; \item Normal text fonts (i.e. {\it not\/} Computer Modern) --- font encoding does {\it not\/} match keyboard character codes; \item Computer Modern fonts. \endlist \noindent In case (1) all that needs to be done is to tell {\TeX} about the font encoding. This is the case e.g. if you use a Windows editor to create the source file, and set up the fonts for {\TEXNANSI} (LY1) or Windows {\ANSI} encoding. For plain {\TeX} and {\LaTeX}~2.09, add Û\input texnansiÛ, when using TeX 'n {\ANSI} encoding. For Windows {\ANSI} encoding, use Û\input ansiacceÛ instead. % With {\LaTeXe} instead use Û\usepackage[LY1]{fontenc}Û (for {\TEXNANSI}) or Û\usepackage[ansinew]{texnasni}Û (for Windows ANSI). Conveniently, alphabetic characters and the 58 `standard' accented characters have the {\it same\/} character codes in {\TEXNANSI}, Windows ANSI, ISO Latin~1, and even Cork (T1) encoding! In case (2) character codes need to be translated from those generated by the keyboard to those used in the font. This is the case e.g. if you use a {\DOS} editor (which may e.g. use {\DOS} code page 850) % , or perhaps {\DOS} code page 437 and set up the fonts for TeX 'n {\ANSI} or Windows {\ANSI} encoding. The translation can be accomplished by {\yandytex} itself by specifying a translation table using \beginlines Û-x=Û \endlines % where does it look ??? need full path ??? \noindent on the command line. % argument with \yandytex. % The translation table is read into {\TeX}'s Ûxchr[]Û table. % The inverse of this --- the Ûxord[]Û table --- is used to % translate incoming characters before {\TeX} starts to analyze them. It is then as if the file had been entered using the encoding of the font, not that of the keyboard. Use Ûdos850wn.mapÛ to translate from {\DOS} code page 850 to Windows {\ANSI} % Use Ûdos437wn.mapÛ to translate from {\DOS} code page 437. (Additional sample Û.mapÛ files are provided in the Û\yandytex\keyboardÛ subfolder). In case (3) character codes need to be {\it expanded\/} into standard {\TeX} notation, since Computer Modern text fonts do {\it not\/} have ready-made accented characters. If you are using {\LaTeXe} then this can be taken care of using Û\usepackage[dos850]{inputenc}Û. This can also be done by {\yandytex} by specifying a keyboard character expansion table using \beginlines Û-k=Û \endlines % where does it look ??? need full path ??? \noindent on the command line. % argument with \yandytex. Use Ûdos1252.keyÛ for an editor set up for Windows {\ANSI} % Use Ûdos850.keyÛ for {\DOS} code page 850. (Additional sample Û.keyÛ files are provided in the Û\yandytex\keyboardÛ subfolder). For additional details please refer to the file Ûkeyboard.txtÛ in the Û\yandytex\keyboardÛ subfolder. % ??? right place % Sample translation tables Û*.mapÛ and % sample keyboard expansion tables Û*.keyÛ % are provided in this subfolder as well. % Avoiding hexadecimal notation in output from TeX: When TeX outputs information on screen or in the log file, it uses hexadecimal notation (e.g. Û^^cfÛ) for character codes above 126 and below 32. This can make it hard to read text containing accented, composite, or special characters in error messages. Use the Û-wÛ command line flag to instead have these characters printed `as is' (i.e. without conversion to hexadecimal). This by itself works well if your source file was made using a {\DOS} editor. If your source file was made using a Windows editor, then use in addition the command line flag Û-jÛ to translate from Windows {\ANSI} back to {\DOS} code page 850. The ability to use full `8 bit' character encoding makes it possible to set up proper hyphenation tables for languages using accented characters. Hyphenation tables for many languages are available from {\CTAN} and national {\TeX} user's groups (see the `language' subfolder of the `{\CTAN}' folder on the CD). New formats must be created using ini-{\TeX} (see section~3.4.1) when new hyphenation patterns are to be used. In {\LaTeXe} you may find that the `babel' package provides a good mechanism for supporting multiple languages in the same document. %%% but is beyond the scope of this introductory manual ??? %%% see Technical Addendum ??? %%% hyphenation issues ??? %%% say more ??? give detailed example ??? \subsect{DVIPSONE} % {\DVIPSONE} is the special Post\-Script printer driver. It is simple to use: Just open the `File{\down}Print' menu in {\DVIWindo}, make sure the `Use DVIPSONE' check box is checked, click on `OK' % and press \ang{Enter} (Of course, you can change the entries in the dialog box if you wish). You can control what `port' you are printing to by first using `File{\down}Print Setup.' {\DVIPSONE} assumes that all of the fonts (the actual Û.pfbÛ font files) that your \TeX\ job uses may be found % are in the folder pointed to by ÛPSFONTSÛ. % This is typically Ûc:\psfontsÛ when using {\ATM}. In Windows~NT without {\ATM} it may be the Û\fontsÛ subfolder of the ÛwinntÛ folder. % or the Û\systemÛ subfolder. % normally set up during installation... %% This may be Ûc:\windows\fontsÛ or Ûc:\windows\systemÛ ??? If you have a set of command-line flags and arguments for {\DVIPSONE} that you use all the time, then you may want to set these up using `Preferences{\down}Command Line' in {\DVIWindo}. % then you can add an entry to the Û[Window]Û section of % Ûdviwindo.iniÛ of the form % ÛDVIPSONE=Û\angi{command line options}, % which specifies command line options to be passed to {\DVIPSONE} when % called from {\DVIWindo}. % % (Alternatively, you can create a Ûdvipsone.cmdÛ file in your % ÛDVIPSONEÛ directory containing the command line options --- % please refer to the Ûreadme.txtÛ file for details). % If you want to produce a Post\-Script file instead of sending output directly % to a printer, then select a printer connected to the port {\sc file:} % If you don't yet have a printer connected to {\sc file:}, double click % on `Printers' in the Windows control panel to `Install' a new printer % driver on that port, or to `Connect' an existing on to {\sc file:}. % (of course, you won't use that actual printer driver, but... You can also tell {\DVIWindo} which printer ports have % are attached to Post\-Script devices attached. For the ports listed, the `Use DVIPSONE' check box will be automatically checked as default (and it will {\it not\/} be checked for other ports). % (like ÛCOM2:Û say). To enable this feature, in the Û[Window]Û section of Ûdviwindo.iniÛ, add e.g. a line of the form % ÛUseDVIPSONEÛ line in reflect your printer port. % If you have problems printing (i.e., no output), you may need to edit the % ÛUseDVIPSONEÛ line in Ûdviwindo.iniÛ to reflect your printer port. % While \beginlines ÛUseDVIPSONE=LPT1:;FILE:Û \endlines \noindent which means that you normally want to use {\DVIPSONE} for a printer on ÛLPT1:Û, as well as when `printing to file' (but not when printing to other ports --- like ÛCOM2:Û say). If you {\it never\/} want the `Use DVIPSONE' box checked, then use instead ÛUseDVIPSONE=BOGUS:Û (or uninstall \DVIPSONE). The window in which {\DVIPSONE} is running when it is called from {\DVIWindo} will persist if an error occurs. %% once we have the batch file fixed up ??? This is so that you can read the error information at your leisure. To dismiss the Window type any character while that window has the focus. % to make it disappear. In rare cases the {\DVIPSONE} window disappears before one can tell what the problem is. In this case temporarily check % `Fonts{\down}Pause WinExe' `Special{\down}Pause WinExe' in {\DVIWindo} before calling {\DVIPSONE}. You may also find % `Fonts{\down}Show WinExe' `Special{\down}Show WinExe' useful --- it shows you exactly how {\DVIWindo} is calling {\DVIPSONE}. % By the way, {\DVIPSONE} will not be able to print % if you have something like a `print monitor' % permanently connected to your printer port. % move to problem section ??? % \noindent will work for systems with parallel-port connections, ÛLPT1Û % will need to be changed to ÛCOM1Û \ellipsis\ ÛCOM4Û if you have a % serial-port connection. % page size setting ??? % duplex mode setting ??? \subsub{Printing to File} % {\DVIPSONE} normally is used to print directly to some printer port. To create a Post\-Script file instead --- to send to a service bureau, say --- click the `Print to File' check box in the printer dialog (or choose a printer connected to the `port' {\sc file:}). Then, when you print, you will be asked for a file name to use. % for the output. % This can be a handy way of feeding {\PS} files to Acrobat Distiller's ``watched folder.'' % Is the following still needed ??? % If you don't yet have a printer connected to {\sc file:}, double click % on `Printers' in the Windows Control Panel to `Install' a new printer % driver on that `port,' or to `Connect' an existing one to {\sc file:}. % % (of course, you won't use that actual printer driver, but... % You may need to `Install' a printer from the Windows Control Panel % (in the `Main' program group) and `Connect' it to the `virtual port' % called ÛFILE:Û. % following somewhat optional If you then decide to {\it print\/} the Post\-Script file locally after all (perhaps to check that everything is {\sc ok}) you can just use the % {\DOS} {\sc copy} command. {\sc copy} command from the command prompt. But you must then take into account the fact that Post\-Script printers (on serial ports and parallel ports at least) expect to receive a Ctrl+D (character code 4) % ({\ASCII} 4) at the end of each job. % (to reset their virtual memory). The Ctrl+D is an `end of job' signal and resets the printer's virtual memory. % in the printer. {\DVIPSONE} automatically adds this character when it sends its output {\it directly\/} to a printer, but control characters designed for controlling a % serial communications link are not valid % strictly in a Post\-Script file, so the Ctrl+D is omitted when `printing to file.' % does not contain this character. % whether from {\DVIWindo} or from {\DOS}.) % You can add the Ctrl+D back in again as follows: You can re-append the dropped Ctrl+D again as follows: \beginlines Ûcopy book.ps+c:\yandy\ps\controld.ps lpt1:Û \endlines % Ûcopy book.ps+c:\yandy\dvipsone\controld.txt lpt1:Û % Ûcopy book.ps+c:\dvipsone\controld.txt lpt1:Û \noindent The file Ûcontrold.psÛ contains nothing but a Ctrl+D character. % For convenience you may wish to create a simple one-line batch file, Ûsend.batÛ say, which contains the following: % above line, but where the filename \angi{book} % ? % is replaced with Û%1Û, referring to the argument % given to the batch file. % The batch file takes one argument, \beginlines Ûcopy %1+c:\yandy\ps\controld.ps lpt1:Û \endlines % Ûcopy %1.ps+c:\yandy\dvipsone\controld.txt lpt1:Û \noindent The single argument is the name of the PS file. % {\it sans\/} extension --- % but with a path specification, if the file is not in the current directory. %% flush following ??? UGH SERIAL PORTS ! potential problems 98/Apr/15 % If you (still) have a serial connection to the printer, % use the {\sc print} command. % In that case you may also want to use the utility {\MODEX}, % to set the baud rate of your serial port to a higher value % then the maximum 19,200 baud rate provided for by {\DOS}; % this can greatly reduce print times % ({\MODEX} will not work in Windows~NT because it accesses % serial port hardware directly). % Just make sure to change the baud rate on the printer {\it first\/} % (using front panel controls or specific Post\-Script commands for your % type of printer). % Finally, if you have a serial line that (still) does not support hardware % flow control, use the utility {\SERIAL} % supplied with {\DVIPSONE} % ({\SERIAL} will not work in Windows~NT because it accesses hardware directly). Note that you can also use {\DVIPSONE} directly from % {\DOS} the command line by typing e.g. \beginlines % Ûdvipsone -v -d=lpt1Û \angi{filename} Ûc:\yandy\dvipsone\dvipsone -v -d=lpt1Û \angi{filename} \endlines \noindent and pressing \ang{Enter}. % If the Û\dvipsoneÛ subfolder is not on your ÛPATHÛ % you will need to use a fully qualified file name: % such as % Ûc:\yandy\dvipsone\dvipsoneÛ. % Use Û-?Û on the command line to get a brief usage summary. Please refer to the Technical Addendum (or Ûreadme.txtÛ in the Û\dvipsoneÛ subfolder and Ûcommflag.txtÛ in the Û\doc-miscÛ subfolder) % subdirectory) % subdirectory %%% or in ÛdocÛ subdirectory of that for additional details. % omit % eliminate % the Û-dÛ command-line option which specifies the destination. %%% flushed the font substitution nonsense from here... % Besides font management, the only other tricks you're likely to need % on a daily basis are figure location and page selection. % \subsub{Figure-file location} % % Has this now been covered better elsewhere ??? installation % % just add the command-line parameter Û-i=c:\tex\figs\psÛ % (or put it in Ûdvipsone.cmdÛ). \subsect{Graphics, EPS, TIFF, BMP, WMF, Color, and Hypertext} % % \subsub{Inserting Encapsulated Post\-Script (EPS) Files} % The \yandytex\ System is compatible with figure insertion methods % scheme used by the `graphicx' (and `graphics') packages in {\LaTeXe}. % Just check that there are files in the graphics There should be files called Ûgraphics.cfgÛ and Ûcolor.cfgÛ in the graphics package folder (typically Ûc:\yandy\tex\latex\graphicsÛ) containing the single line \beginlines Û\ExecuteOptions{dvipsone}Û \endlines \noindent This is to tell the graphics package what `driver' you are using. To invoke the graphicx package in {\LaTeXe}, use \beginlines Û\usepackage{graphicx}Û \endlines \noindent % to load the package, Then, to insert the {\EPS} file Ûmyart.epsÛ use \beginlines Û\includegraphics{myart.eps}Û \endlines \noindent If you specify a full path for the file, use Û/Û instead of Û\Û to prevent {\TeX} % from trying to from interpreting parts of the file name as control sequences. The figure can also be scaled using, for example, \beginlines Û\includegraphics[scale=0.5]{myart.eps}Û \endlines \noindent Additional options are available. For details % please refer to Ûgrfguide.texÛ in the `graphics' package folder % directory (a printed version can be obtained by copying the Post\-Script file Ûgrfguide.psÛ to a PS printer port). % We now supply unpacked files % As with most {\LaTeXe} `packages' you first have to % `unpack' the graphics package. You can do this by running {\TeX} % on the file Ûgraphics.insÛ in the Û\tex\latex\graphicsÛ % subfolder. Temporarily uncheck the `Fonts{\down}Working Directory' % --- if it is checked --- so as to force {\TeX} to write the % files created back into the same directory. %% above may now not be relevant anymore ??? The \yandytex\ System is also compatible with the two most common % higher-level Post\-Script figure inclusion macro files used in % {\LaTeX} 2.09 and plain {\TeX}, namely plain {\TeX} and {\LaTeX} 2.09, namely Ûepsf.texÛ and Ûpsfig.styÛ % (as well as several others, see below). %% section? (actually, for reasons explained below, use Ûepsfsafe.texÛ and Ûpsfigfx.styÛ instead). We'll briefly describe Ûepsf.texÛ here. Given a file named, for example, Ûmyart.epsÛ, to include it in a \LaTeX\ 2.09 file, type: % Û% Û this line must appear after the Û\documentclassÛ line and before \beginlines Û\documentstyle[epsf]{Û\angi{main documentstyle}Û}Û % (for \LaTeX\ 2.09) % or \endlines \noindent While the `epsf' style was % originally designed for {\LaTeX} 2.09, for backward compatibility it is {\it also\/} available in the {\LaTeXe} graphics package, e.g. \beginlines Û\documentclass{Û\angi{main document class}Û}Û Û\usepackage{epsfig}Û % %Û (for \LaTeXe); \endlines % don't need the [dvipsone] option right ??? % Û\usepackage[dvipsone]{epsfig}Û % %Û (for \LaTeXe); % was Û\usepackage[dvipsone]{graphics,epsfig}Û % %Û (for \LaTeXe); % don't need {graphics}, since invoked by epsfig (David Carlisle) \noindent In either case, follow this with \beginlines Û\begin{document}Û \ellipsis Û\begin{figure}Û Û\epsfig{file=myart.eps}Û Û\caption{My Caption Goes Here}Û Û\end{figure}Û \ellipsis Û\end{document}Û \endlines % Û\epsfig{myart.eps}Û % Û\epsf{myart.eps}Û % \noindent For other uses of Post\-Script with \TeX, please consult your % local \TeX\ Wizard. % \noindent % If you specify a full path for the file, use / instead of \char92\ to % prevent {\TeX} % from trying to % from interpreting the file name as a control sequence. \noindent Note that {\DVIWindo} will display a preview in (i) {\TIFF}, (ii) Windows Meta\-File ({\WMF}), or (iii) {\EPSI} form associated with an {\EPS} file. If you do not obtain a preview, check the application that created the {\EPS} file; you may have disabled the generation of previews. % it may have an option that disables generation of a preview. % in the {\EPS} file. % it probably did not follow the specifications correctly. % You can also add a preview to an {\EPS} file that does not have one using a PS % Post\-Script interpreter such as Transverter Pro\registered\ from TechPool Software, or GhostScript. But the details are beyond this introductory manual. \tip % Advanced Feature: If you do not use the extension Û.epsÛ in the call to insert the file, {\DVIWindo} will look for a file with extension Û.epsÛ for printing, but try and find a corresponding file with extension Û.tifÛ for preview. This is another way to `add a preview' to an {\EPS} file that does not have one. % You should know that Ûepsf.texÛ reads the {\EPS} file to find the Post\-Script comment that defines the bounding box for the figure in order to figure out how much space to allocate on the page. This may not work as expected if the {\EPS} file contains a preview in {\TIFF} or {\WMF} format --- yet, previews are obviously useful. % because {\DVIWindo} shows previews on screen. For this reason, use % Please use % refer to the file Ûepsfsafe.texÛ {\it instead\/} of Ûepsf.texÛ. It contains a simple fix to the bounding box reading code to deal properly with previews. % Other style files provide alternative high level interfaces for figure inclusion. One popular one is Ûpsfig.styÛ. It has a similar problem with previews in {\EPS} files. Use Ûpsfigfx.styÛ instead. % Please refer to the Technical Addendum % or the file Ûpsfigfix.txtÛ % until Technical Addendum is finished % for information on how to modify % the official % Ûpsfig.styÛ. % so it works properly. Note that at the lowest level, {\DVIWindo} and {\DVIPSONE} support twelve % more than ten different schemes for figure inclusion (see Technical Addendum). This is necessary because there is no standardization --- every printer driver and previewer uses a different scheme! We recommend using high level interfaces like the \LaTeXe\ graphics package, Ûepsf.texÛ or Ûpsfig.styÛ whenever possible to avoid running into problems. % at the low level. % If your Post\-Script art files are in Ûc:\epsÛ, % % Ûc:\tex\figs\psÛ, % make sure that the environment variable ÛPSPATHÛ is % set accordingly: ÛPSPATH=c:\epsÛ. % ÛPSPATH=c:\tex\figs\psÛ. % The same goes for inserted {\TIFF} and Windows Meta\-File images. % \subsub{Including {\dsc TIFF} and Windows Meta\-File Images} \subsub{Including {\dsc TIFF}, {\dsc BMP} and {\dsc WMF} Images} % In addition to inclusion of images in {\EPS} form, {\DVIWindo} and {\DVIPSONE} provide support for insertion of images in {\TIFF} format. For images (rectangular arrays of gray levels or color tones), {\TIFF} provides a natural format --- typically much more compact than the equivalent {\EPS} file. Also, there is no need in this case for a separate `preview,' since {\DVIWindo} can show the {\TIFF} file directly . % (although this can be a bit slow for {\it very\/} large {\TIFF} images --- % so you may want to disable this feature by unchecking % `Preferences{\down}Show Previews'). One disadvantage of the {\TIFF} file format is that it is a complicated, compact binary form that {\TeX} itself cannot read. So it is not possible for figure insertion macros to % directly determine the image dimensions directly from the image file (the way they do with {\EPS} files) --- you have to supply them. % by hand. You can obtain the required information % required number of columns and rows in the image using the utility {\TIFFTAGS}, which % is supplied with {\DVIWindo}. may be found in the Û\utilÛ subfolder. % Look for the tags `ImageWidth' and `ImageLength' --- ignore the rest. This shows the image width and height (for more details use Û-vÛ on the {\TIFFTAGS} command line). % will be shown at the end of the listing. % output produced. The low level interface for insertion of an image in {\TIFF} format is Û\special{insertimage: Û\angi{TIFF filename}Û}Û. Refer to the file Ûtifftest.texÛ for sample macros that use this interface. % % is this file included ??? % % Û\special{insertimage: Û\ang{filename} \ang{width} \ang{height} Û}Û. % % The \ang{width} and \ang{height} arguments after the {\TIFF} file % name are optional. % You can also optionally specify width and height after the % {\TIFF} % file name: You can specify scaling: \beginlines % Û\special{insertimage: Û\angi{TIFF filename} \angi{width} \angi{height}Û}Û. Û\special{insertimage: Û\angi{TIFF filename} ÛscaledÛ \angi{x-scale} \angi{y-scale}Û}Û. \endlines \noindent If only one scale-factor is specified, it is used for both directions (i.e. the figure will be scaled isotropically). An alternative form of this command is: \beginlines Û\special{insertimage: Û\angi{TIFF filename} \angi{width} \angi{height}Û}Û. \endlines \noindent The units for width and height are {\TeX}'s `scaled points,' of which there are 65536 per printer's point --- of which in turn there are 72.27 per inch (these are the units used by {\TeX} in its internal calculations). If height is omitted (or set to 0), then the image is scaled isotropically --- that is, the height is computed from the width using the aspect ratio specified in the image file. If both height and width are omitted (or set to 0), then the `natural size' is used --- if specified in the file. You can include Windows Bitmap files (\BMP) using the same mechanism. {\BMP} files are much simpler than {\TIFF} files but correspondingly less flexible. % this is a bit abbreviated, the file may not have a natural size... % flush the following to make space ... % A third optional argument --- after width and height --- specifies which % image to use in the rare case that a {\TIFF} file contains more than one. % The default is to use the first image in the file. {\DVIWindo} also provides for inclusion of images in Windows Meta\-File (\WMF) format. % (However, {\DVIPSONE} cannot use them). {\DVIWindo} can even use files saved from the Windows clipboard, {\it provided\/} they contain a placeable % Windows Meta\-file (i.e. a format listed as `Picture' in the `Display' menu of the Clipboard Viewer). % Enhanced MetaFile % Clipboard Viewer: Display {\bf Note:} Unlike {\DVIWindo}, {\DVIPSONE} % , on the other hand, does {\it not\/} support Windows Meta\-Files, since such files are basically just recordings of a sequence of Windows Graphical User Interface ({\sc gui}) calls, and thus require Windows for interpretation. The low level interface for insertion of an image in {\WMF} form is Û\special{insertmf: Û\angi{WMF filename}Û}Û. % % One form for insertion of WMF files using scale factors to control size is Optionally they can be scaled: \beginlines Û\special{insertmf: Û\angi{WMF filename} ÛscaledÛ \angi{x-scale} \angi{y-scale}Û}Û. % Û\special{insertmf: Û\angi{WMF filename} \angi{x-scale} \angi{y-scale}Û}Û. \endlines \noindent The image will be scaled isotropically if you specify a single scale factor. If you specify two scale factors, the first will be used to scale the image in the {\lbmi x}-direction, while the second will be used to scale it in the {\lbmi y}-direction. % This provides for anisotropic scaling. % An alternate form for insertion of WMF files is: % much like the one used for {\TIFF} image insertion) is: \beginlines Û\special{insertmf: Û\angi{WMF filename} 0 0 \angi{width} \angi{height}Û}Û. \endlines \noindent The utility {\WMFSPY} can be used to extract basic information about a `placeable' {\WMF} file, such as the coordinates of the corner of the `window' in which it is drawn, and the units of those coordinates. This can be useful in reserving space on the page for the {\WMF} (although there is actually no {\it guarantee} that the figure lies entirely within the window specified in the {\WMF} header). % of the file). \subsub{Color} % {\DVIWindo} and {\DVIPSONE} both support a % simple simple and widely accepted scheme for color supported under \LaTeXe. If you are using \LaTeXe, then please use the `color' package. %% maybe move this to Technical Addendum ??? If you for some reason you do need a low-level interface (e.g. you are using plain {\TeX}) then read on. The low level interface is Û\special{color Û\angi{color spec}Û}Û. % also allows color: with colon as alternative form You can specify color using: (i) gray level, (ii) {\sc rgb} (red, green, and blue), or % components, or (iii) {\sc cmyk} (cyan, magenta, yellow, and black) components: \beginlines Û\special{color gray }Û. Û\special{color rgb }Û. Û\special{color cmyk }Û. \endlines \noindent In each case the numbers should lie in the 0.0 to 1.0 range. % in each case. {\sc rgb} is more appropriate % convenient when specifying color for a display screen (additive color system), while {\sc cmyk} provides better control when printing (a `subtractive' color system). % % Unfortunately, we cannot go into a deeper discussion of % color issues in this introductory manual. It is also possible to `push' (save) the current color state, and to later `pop' (restore) it again. %% and these can be combined In the following, for example, the word `blue' will appear blue --- both on screen and on a color printer --- while the surrounding text will appear in black, as usual. \beginlines ÛJust once in aÛ Û\special{color push}%Û Û\special{color rgb 0 0 1}%Û ÛblueÛ Û\special{color pop}%Û Ûmoon.Û \endlines %% too much space between lines ??? \noindent Note the use of Û%Û at the end of each line containing Û\special{..}Û to prevent the Û\special{..}Û % it from inserting spurious white space --- or having other unwanted side effects. By the way, you can combine color commands, although the only combination that makes much sense is ÛpushÛ followed by a color specification. % (it is generally a good rule to end each line in a {\TeX} macro % definition with Û%Û to prevent spurious white space from % being introduced). % Note that Both {\DVIWindo} and {\DVIPSONE} go to some considerable trouble to correctly deal with color changes that extend across page breaks. They determine the state of the color push down stack at page breaks in prescan of the Û.dviÛ file in order to make it possible to preview of pages in arbitrary order later on (and to print selected page ranges). For display in {\DVIWindo}, % just make sure that `Fonts{\down}Color Fonts' is {\it not\/} checked, since that takes precedence. % in order to avoid interference with % this alternate % use of color to distinguish different fonts. On a black and white printer, by the way, color will be simulated using gray levels. And on bi-level devices like laser printers, gray levels in turn are simulated using halftones. So `colored text' will tend to look `choppy' on such a device. If you use colored text, make sure to push the color state and switch to black when setting headers and footnotes; afterward pop the color state again (Note: this happens automatically if you use the {\LaTeXe} color package). % David Carlisle The reason this has to be done is that {\TeX} may work on headers and footers at unexpected times --- possibly in the middle of a paragraph in which you have % temporarily changed the color! % For similar reasons, % serious color work may require modifications to {\TeX}'s Û\outputÛ % routine to avoid problems at the point that {\TeX} decides to % typeset a complete page % for the same reason % (Unfortunately {\TeX} itself does not support color in % the same way it supports fonts). %% give more details, why use cmyk instead of rgb ??? If you need to control the color of bi-level (monochrome) inserted images in {\TIFF} format then use the `figurecolor' Û\special{..}Û described in the Technical Addendum. A complete treatment of issues relating to use of color in publications is beyond the domain of this introductory manual. %%% color separations ? %%% except see notes relating to separation and trapping later here ??? \subsub{Hypertext Links} % {\DVIWindo} provides support for hypertext links. You can establish rectangular `buttons' that are sensitive to clicking with the left mouse button, % the user can click on, using \beginlines Û\special{button: Û\angi{width} \angi{height} \angi{action}Û}Û. \endlines \noindent The units for width and height are {\TeX}'s `scaled points.' % of which there are 65536 per printer's point --- of which in turn % there are 72.27 per inch % (these are the units used by {\TeX} in its internal calculations). Note that the button is not automatically made visible. You can draw the user's attention to the button by drawing a colored rule % rectangle of the same shape and size, or by coloring the text over the sensitive area of the button (see Ûhyper.texÛ for examples). %%% make sure file included ??? In overlaying text on a rule defining the button area, you may find {\TeX}'s Û\rlapÛ control sequence of use. % use \rlap ??? The \angi{action} most commonly specified is simply the name of a `mark' that is defined elsewhere in the same file using \beginlines Û\special{mark: Û\angi{label}Û}Û \endlines \noindent (If \angi{label} contains white space, use double quotes to delimit it). % both in the mark and where it is called from ... % One can return from a hypertext jump % to a `mark' by clicking the {\it right\/} mouse button. A stack of return points is maintained. % (shallow) The \angi{action} %% ? % {\it action\/} can instead be of the form % the token \beginlines Ûfile: Û\angi{file name} % followed by the name of another Û.dviÛ file. \endlines \noindent If the user clicks on such a button, {\DVIWindo} opens the specified Û.dviÛ file for viewing. % Finally, the % \angi{action} %% ? % {\it action\/} can be of the form % the token \beginlines Ûlaunch: Û\angi{command line} \endlines \noindent % followed by the command line used to call an arbitrary % Windows program or console application. This can be used to start up another Windows application, console applications or batch file in response to a simple mouse click. % Note that {\DVIWindo} does {\it not\/} wait for the other application to be terminated before continuing. %%%%% New 1995/Aug/14 Use commas to separate multiple \angi{actions} in a single hypertext button Û\specialÛ. If the name of a `mark' is included, it should come first. At most one name of a `mark' may appear. Similarly, Ûfile:Û may appear at most once and it should follow the name of a `mark,' if any. One or more Ûlaunch:Û \angi{actions} may appear at the end of the list. %%% Need to talk about automatic translation to pdfmark by DVIPSONE Note that {\DVIPSONE} automatically translates hypertext links to appropriate `ÛpdfmarksÛ' for Acrobat Distiller. Hence hypertext links that work in {\DVIWindo} will also work in Acrobat Reader when viewing the corresponding {\PDF} file. Hypertext buttons can even refer to {\sc url}s on the World Wide Web ({\WWW}). While these % at the moment ... do {\it not\/} work in {\DVIWindo}, they {\it are\/} translated into links that work in the Acrobat Reader. % resulting Acrobat {\PDF} file when viewed in % In addition, {\DVIPSONE} also provides a way of communicating information to Acrobat Distiller via Û\special{PDF: ...}Û. Specifically, \beginlines Û\special{PDF: Title ...}Û Û\special{PDF: Author ...}Û Û\special{PDF: Subject ...}Û Û\special{PDF: Keywords ... , ... , ...}Û \endlines \noindent These set up the information shown in the Acrobat Reader when the user selects `File{\down}Document Information{\down}General.' In addition, \beginlines Û\special{PDF: BBox }Û \endlines \noindent can be used to set up a `crop box' that clips the image % to a specified bounding box (given in the Post\-Script default user coordinate system). Finally \beginlines Û\special{PDF: Base ...}Û \endlines \noindent can be used to set up a base {\sc url} for hypertext links to {\WWW} % World Wide Web pages. % See Ûhypr2pdf.txtÛ in the Û\doc-miscÛ subfolder % subdirectory for additional details. The {\LaTeXe} `hyperref' and `backref' packages can generate appropriate hypertext links for use with {\DVIWindo} and {\DVIPSONE}. You just need to let them know which `driver' you are using. \subsub{Device Independent Rotation and Scaling} % % More appropriate for DVIWindo discussion? % {\DVIPSONE} supports a set of Û\specialÛ's for device independent coordinate system transformations. So does {\DVIWindo} --- but only in Windows~NT. These commands have the form % \beginlines Û\special{CTM: Û \angi{transformation}Û}Û. % \endlines Here `{\CTM}' stands for coordinate transformation matrix, in analogy with Post\-Script terminology. The \angi{transformation} may be rotation, scaling, translation, or arbitrary linear transformation: \beginlines Û\special{CTM: rotate }Û Û\special{CTM: scale }Û Û\special{CTM: translate }Û Û\special{CTM: concat }Û \endlines \noindent Rotation, scaling and other % arbitrary linear transformations are with respect to {\TeX}'s current point. That is, {\TeX}'s current point when mapped to the page {\it after\/} the change in transformation is the same as what it was when mapped to the page {\it before\/}. There are also alternate `asterisk' forms % with an asterisk (*) after --- Ûrotate*Û, Ûscale*Û, and Ûconcat*Û --- which perform the inverse operations. Finally, it is possible to save the current {\CTM} using ÛpushÛ, and to restore it using ÛpopÛ. % Note that ÛpopÛ {\it also\/} resets the current point on the page to whatever {\TeX}'s current point maps to under the restored {\CTM}. % Finally, ÛpopallÛ restores the default {\CTM} and resets the stack. {\DVIPSONE} also supports the use of raw Post\-Script for coordinate transformation --- {\it provided\/} the code is created in a form suitable for {\DVIPSONE}. In {\LaTeXe}, this means that a Ûgraphics.cfgÛ file has been set up for this purpose % see section ??? (containing just Û\ExecuteOption{dvipsone}Û). Alternatively the `graphics' package can be given the ÛdvipsoneÛ option to tell it that % you are using {\DVIPSONE} is used as the `driver.' For backward compatibility, {\DVIWindo} translates such raw Post-Script coordinate transformation intended for {\DVIPSONE} into the corresponding {\CTM} action. So in Windows~NT rotation and scaling requested via the `graphics' package will be obeyed when displaying typeset material on screen, as well as when printing to non-PS devices from {\DVIWindo}. % This applies, for example, to the Û\scaleboxÛ and Û\rotateboxÛ commands available in the `graphics' package. See Ûctm.txtÛ in the Û\doc-miscÛ subfolder % subdirectory for additional details. \subsect{Fonts} % If you will never use any fonts other than the Computer Modern set, then you don't need to read this section. However, there are thousands and thousands of fonts out there (about 90,000 in Adobe Type~1 format alone!), and many of them are very nice looking. So\ellipsis % \TeX\ was originally written to use 128-character fonts; however, most fonts % today have spaces for 256 characters. Eventually, \TeX\ was revised to use % the upper half of the range as well. \subsub{Font Encoding and Character Layout} % Inside a % {\TeX} source file, characters are represented by numbers % most % typically in the range from 0--255. % Most Electronic communication systems (such as email software) are set up to depend % {\ASCII} mostly on character codes in the range from 32 to 126. Many of these 94 so-called {\ASCII} character codes are mapped to the same glyphs % on most systems % every (upper- and lowercase alphabets, numerals, and punctuation) by most programs on most platforms. Unfortunately, other character code assignments can vary widely on different operating systems or different applications. % correspond to different glyphs on different systems. % and there are even some differences in the 32--127 range. When we put on our typesetter's hat, all we care about is that a particular keystroke --- or {\TeX} control sequence --- produces the desired glyph --- preferably the {\it same\/} glyph in whatever text font we use. In addition we would like access to {\it all\/} glyphs in a font, not just those in a platform-specific encoding. Finally, we may also want to be able to use a character layout that matches the hard-wired assumptions in plain {\TeX} and {\LaTeX} 2.09 (inherited from the Computer Modern text fonts). % layout). % like Windows {\ANSI} or Macintosh standard roman encoding. Unfortunately, achieving all of those objectives has been far from simple. \yandy\ has changed all that with `on the fly' reencoding. {\it You\/} can decide what characters will appear in what positions in all your text fonts and so ensure that all fonts are perfectly consistent. You can also gain access to any `unencoded' glyphs that may be in a text font, yet not be normally accessible in Windows {\it or\/} on the Macintosh. % (Windows {\ANSI} encoding lacks 15, % now 13 in Windows 98 and NT 5.0 and the Macintosh standard roman encoding lacks 21 of the `standard' 228 glyphs found in most % Type~1 text fonts). % ASE lacks 23 + 58 ... The mapping from character codes (in the range 0--255) to glyph names that you choose is given in a plain {\ASCII} file called an `encoding vector file.' % is a plain ASCII file that gives the mapping from % character codes (in the range 0--255) to glyph names. % % We recommend the `texnansi' encoding vector since it provides access to % all 228 glyphs in plain text fonts, yet matches most of the hard-wired % assumptions that {\TeX} makes about where accents and various special % characters appears in the character layout. % Several commonly used encoding vector files (extension Û.vecÛ) may be found % have been provided % in the Û\dvipsoneÛ folder. % directory. in the Û\fonts\encodingÛ subfolder. % subdirectory. % or the ÛvecÛ subdirectory... % Unless you have some special reason to do otherwise... We recommend that if you are using fonts in Type~1 format % on {\ATM} compatible systems you use the ÛtexnansiÛ ({\TEXNANSI}) encoding --- unless there is some good reason to do otherwise. This \beginlines (i) provides access to 228 `standard' glyphs found in text fonts, (ii) matches ISO Latin~1 (and Cork) in the 160--255 range, (iii) puts the lower 128 characters where \TeX\ expects to find them, (iv) provides access to f-ligatures (`fi,' `fl,' `ff,' `ffi,' and `ffl') (v) avoids `white space' control character codes. \endlines \noindent (Some other software has trouble with `white space' `control characters' with codes 0, 9, 10, 13 or 32). See section~6 at the end of this manual for detailed character layout in {\TEXNANSI} encoding. %% section? % % If you are using a system that is {\it not\/} {\ATM} compatible % (e.g. Windows~NT 3.51) then use Windows ANSI encoding instead. The {\TEXNANSI} encoding % option % feature was probably selected during installation, since it is the default. % (unless you are on Windows~NT without {\ATM}). % in which case the default is to set things up for Windows ANSI). If you opted {\it not\/} to select % include it then --- and you want to switch to it now --- then use the `Fonts{\down}Encoding' menu item in {\DVIWindo}. % then open the file Ûdviwindo.iniÛ, % and add a line of the form % %%% is this still relevant ??? % This sets the ÛENCODINGÛ environment variable to refer to an encoding vector file Ûtexnansi.vecÛ in the folder % directory specified by ÛVECPATHÛ. % (see below). above ? %% section? If you use {\TEXNANSI} (Ûtexnansi.vecÛ) encoding in plain {\TeX} or in {\LaTeX}~2.09, then you should also add the line % of the form `Û\input texnansiÛ' to your {\TeX} source file. % This refers to a {\TeX} macro file called Ûtexnansi.texÛ, which may be found in the Û\texinputÛ subfolder. For {\LaTeXe} use instead Û\usepackage[LY1]{fontenc}Û. % repetition ??? % \noindent % The above is required if you use plain text fonts with Windows {\ANSI} % encoding in {\DVIWindo}. % and other Windows applications. % Windows {\ANSI} (Ûansinew.vecÛ) is the default character layout used by % Windows applications. % Windows and % most If you use Windows {\ANSI} (Ûansinew.vecÛ) encoding with plain {\TeX} or {\LaTeX}~2.09 then you should add a line of the form `Û\input ansiacceÛ' to your {\TeX} source file % (The exact position in your source file where this statement appears may be important, since this file has to make `quoteleft' and `quoteright' active --- see comments at the beginning of the Ûansiacce.texÛ file for details). % % For additional details please refer to the section `Font Encoding % and Character Layout.' This refers to a {\TeX} macro file called Ûansiacce.texÛ, which may be found in the Û\texinputÛ subfolder. For {\LaTeXe} use Û\usepackage[ansinew]{texnansi}Û instead. % Note that if you decide to change encoding {\it after\/} installation, % then you {\it also\/} need to switch {\TeX} metric files (Û.tfmÛ). % % Suitable Û.tfmÛ files are already provided in % ÛtexnansiÛ, ÛansinewÛ, and ÛcorkÛ % ÛstandardÛ % subfolders of the Û\fonts\tfm...Û folders for % Lucida Bright and \MathTime. % % You can use the batch file ÛencodtfmÛ in the ÛutilÛ % folder to switch to differently encoding Û.tfmÛ files % for the Lucida Bright, Times Roman, Helvetica and Courier fonts. % $For other fonts you will have to create new Û.tfmÛ files % using `WriteTFM...'. %% should set up batch file to change encoding (copying TFM files) ??? %%%% warning about ` and ' becoming `active' ? %%%% where to find texnansi.tex and ansiacce.tex ??? %%%% \usepackage[ansinew]{inputenc} ??? %%%% \buildcomposites \usecomposites ??? %% refer to `onthefly.txt' for details ? % Note that To repeat: if you change the encoding setting in {\DVIWindo}, you must {\it also\/} % change the Û.tfmÛ {\TeX} metric files to the ones % appropriate for that encoding {\it and\/} change the {\TeX} source files that are Û\inputÛ to tell {\TeX} about the character layout being used. It is definitely {\it not\/} sufficient to just change the ÛENCODINGÛ environment variable. % All three of the following % --- \beginlines (i) the ÛENCODINGÛ environment variable, (ii) the encoding of the Û.tfmÛ files for the text fonts, (iii) and what {\TeX} is told via an encoding source file, \endlines \noindent need to agree on the assumed encoding, otherwise you may miss special characters, ligatures and accented characters in non-CM fonts. In the \yandytex\ system, (ii) above is already automatically controlled by setting (i), so all that remains for you to do is deal with (iii). Note that Computer Modern (CM) fonts are not affected by the setting of the encoding variable, because they are not treated as text fonts by Windows and {\ATM}. \subsub{Installing and Using Fonts} % To use a Type~1 font, first install the font. % In systems using {\ATM}, % compatible systems, add the font to your system using the {\ATM} Control Panel. % (select ÛFile{\down}InstallÛ). % (select ÛFile{\down}Install New FontÛ). Select `Programs{\down}Adobe{\down}ATM.' % Adobe Type Manager from `Start.' % (or `Programs{\down}Main{\down}ATM' ). % In Windows~2000 --- without the {\ATM} font manager --- you can install fonts by dragging the fonts (Û.pfmÛ files) to the Û\fontsÛ subfolder of the ÛwinntÛ folder. % Alternatively, you can install them from `Fonts' in the `Control Panel' % by selecting `File{\down}Install New Font.' % In this process they are converted to TrueType format. % After installating a font, % you may want to check the font and its character layout using `Fonts{\down}Show Font' in {\DVIWindo}. %%% give more details ??? already done earlier Second, copy or create the proper Û.tfmÛ file. Font sets designed for use with {\TeX} typically already come with Û.tfmÛ files, which may be found on the font CD. % (or have already been copied during installation). % are copied during font installation. % Actually, % Note that In the case of the `Lucida Bright + Lucida New Math' and the {\MathTime} font sets, appropriate Û.tfmÛ files are % were already setup during {\TeX} System installation. % % redundant now ? % % If you later change the encoding that you are using % you will have to copy the appropriate Û.tfmÛ from % subfolders of Û\fonts\tfm-lbÛ or Û\fonts\tfm-mtÛ % (or the font diskette) to Û\fonts\tfm-lbÛ or Û\fonts\tfm-mtÛ. % In each case, There are already subfolders set up with Û.tfmÛ files for (i) {\TEXNANSI} encoding (ÛtexnansiÛ); (ii) `Windows ANSI' (ÛansinewÛ); (iii) `Cork encoding' (ÛcorkÛ); and (iv) Adobe Standard Encoding. % (ÛstandardÛ). % and Adobe StandardEncoding ??? % Use Ûencodtfm.batÛ to set up the appropriate Û.tfmÛ files % (see section~3.7.1) In the above case there is no need to create new Û.tfmÛ files. % If you {\it do} need to create a Û.tfmÛ file for a new font you have installed, % Then, to create the Û.tfmÛ file that {\TeX} needs, % From {\DVIWindo}'s menu, select `Font{\down}Write TFM\ellipsis' from {\DVIWindo} (or simply press Ctrl+M). % not `Enter'... Then % double-click on the desired font and the `style' select the desired font and `style' (regular, bold, italic, or bold italic). {\DVIWindo} will first write a human readable plain {\ASCII} `Adobe Font Metric' (\AFM) file in the Ûc:\yandy\fonts\afmÛ subfolder. % right place ??? % (or its ÛAFMÛ subdirectory). It then calls the {\AFMtoTFM} utility. The resulting Û.tfmÛ file will % automatically be placed in the {\it first\/} folder % directory pointed to by the ÛTEXFONTSÛ environment variable --- or rather the `encoding specific' environment variable, if one is defined. % (typically Ûc:\yandy\fonts\tfmÛ). {\DVIWindo} will advise you what the font file name is. Make a note of it, because it % this is the name you will use to refer to the font in {\TeX}. For example, if you made a Û.tfmÛ file for the Times-Roman font (regular style), then the Û.tfmÛ file name would be Ûtir.tfmÛ. You can then refer to the font by that name in % plain {\TeX}: \beginlines Û\font\myfont=tir at 12.345ptÛ Û{\myfont This will appear in Times-Roman at 12.345pt}Û \endlines % You can create the Û.tfmÛ file either directly from {\DVIWindo}'s menu % or from the {\DOS} command line. \noindent % Before using `Write TFM' make sure that the environment variables % ÛTEXFONTSÛ and ÛVECPATHÛ are set up correctly, and that % {\AFMtoTFM} is accessible from {\DVIWindo}. % To avoid confusion, it is best to do all four styles (regular, bold, italic, bold italic) of a given `face' at the same time. % Note however that Some faces --- such as Symbol --- come in just one style. % {\DVIWindo} will issue a warning if you select a non-existent style. % Normally {\DVIWindo} doesn't offer up a style that does not exist. % But should you get a warning about a `missing style' just click `Cancel.' % It will no longer allow selection of non-existent styles. If you have many Û.tfmÛ files to create, then you may want to take advantage of % the features of `Write All TFMs\ellipsis.' This allows you to select various subsets of all installed fonts. You can select Type~1 fonts, or TrueType fonts, and you can select text fonts or symbol/decorative/math/pi fonts. Finally, you can check a box to process `New Fonts Only' (i.e. those for which no Û.tfmÛ file exists yet). Note that {\TFM} files are `encoding sensitive.' New {\TFM} files have to be created when you change the encoding vector used for `on the fly' reencoding of text fonts. `Write All TFMs...' is particularly handy in this situation. Metric files for different encodings are kept in different directory subtrees so that they do not conflict with one another. % New Û.tfmÛ files are deposited into the first directory in the % list of directories in the ÛTEXFONTSÛ environment variable, % by the way. %% redundant %% where do the new TFMs end up ??? % de-emphasize following --- less important now If you % already have the {\AFM} % Adobe Font Metrics file of a font, then you can also create the Û.tfmÛ file from the % {\DOS} command prompt using the {\AFMtoTFM} utility. % In some rare cases This provides detailed control of the conversion, which in some cases may be useful. % Most quality fonts come with {\AFM} files, although font installation using {\ATM} does {\it not\/} copy these files to the hard disk. Look in the font folders on the CD % diskette for {\AFM} files ({\AFM} files for fonts in the Adobe library may {\it also\/} be found on Ûftp.adobe.comÛ and the Type On Call ({\sc toc}) CD-ROM --- although it may take some poking around to locate them). % `hidden' `system' files in odd directory structure % to find it % and no longer on ftp.adobe.com % In any case, to use {\AFMtoTFM} for a text font, type % From the {\DOS} command line % in the directory where you keep your Û.afmÛ files, % Ûafmtotfm -c texnansiÛ \ang{filename}, \beginlines % Ûafmtotfm -vadx -c=texnansiÛ \angi{AFM filename}, Ûc:\yandy\util\afmtotfm -vadx -c=texnansiÛ \angi{AFM filename}, \endlines \noindent from the command line. % (The {\AFMtoTFM} utility is in the Û\utilÛ subfolder --- % if this is not on your ÛPATHÛ you may have to give the full % path in the above call). Copy the resulting Û.tfmÛ file to one of the folders % the first folder % directories listed in the ÛTEXFONTSÛ environment variable --- or rather the `encoding specific' environment variable ÛTEXNASNIÛ. The above command line arguments tell ÛafmtotfmÛ what encoding vector to use, and to set up the f-ligatures, as well as many useful `pseudo ligatures' (such as Û---Û becomes ÛemdashÛ). Run {\AFMtoTFM} with Û-?Û on the command line to see other % commonly used command line options. Do {\it not\/} run `Write TFM\ellipsis' or {\AFMtoTFM} on {\it math\/} fonts. % --- math fonts, symbol fonts, decorative fonts. % Doing so will gain you nothing but confusion. Math fonts use a fixed encoding, so there is no need to use anything but the Û.tfmÛ file that originally came with the font. % Also, math fonts require additional fields in the {\TFM} file --- which {\AFMtoTFM} {\it can\/} insert --- but {\it only\/} if it has an {\AFM} file specially prepared with additional typesetting information added in `Comments' (in font sets from {\yandy}, such special {\AFM} files have the % basic font name extended with the letters `tex'). % see \fonts\afm subfolder ... %%% following is repetitious % Note also that non-text fonts --- math fonts, symbol fonts, % decorative fonts --- are designed to be used with {\it fixed\/} % encoding and are not touched by `on the fly' reencoding in {\DVIWindo} % and {\DVIPSONE}. Pulling in a few new fonts for casual use is easily accomplished using the method illustrated above. Systematically replacing the traditional Computer Modern (CM) fonts with other fonts is a more involved matter and requires non-trivial {\TeX} macro source files. These are supplied for plain {\TeX} and {\LaTeX}~2.09 in the Û\texinputÛ subfolder % when you purchase end user licenses for the `Lucida Bright + Lucida New Math' and the \MathTime\ font set. Support for these font sets under {\LaTeXe} is also available in the Û\tex\latex\required\psnfssÛ subfolder. These files may also be found in the font folders on the CD. % diskettes % (or in the {\PSNFSS} folder % directory % on the font diskette --- or {\CTAN}). % Additional details on using % either the `Lucida Bright + Lucida New Math' font set or the \MathTime\ font set are given in sections~3.7.4 and 3.7.5. %% absolute section reference %% give forward reference to sections discussion LB+LNM and MT %% section? % lucida.dtx/lucida.ins mathtime.dtx/mathtime.ins There are literally thousands of text fonts in Type~1 or TrueType form that can now be used with {\TeX}. Unfortunately, there are relatively few {\it math\/} fonts, and only those specially designed for use with {\TeX} are useful % a small fraction of those can be used with {\TeX}, because of idiosyncratic demands that {\TeX} makes. % on math fonts. As a result % , at the moment, there isn't much available beyond: \beginlines (i) Computer Modern math, (ii) Lucida New Math, (iii) \MathTime, and (iv) European Modern. \endlines % and the old Lucida Math. %% European Modern ??? \subsub{Font Name Aliasing} % The font names for the Computer Modern fonts are standardized across all platforms and all {\TeX} implementations. Names for other fonts are not --- different {\TeX} systems use different names. % for fonts The \yandytex\ System by default simply uses the actual font file names. Take the `Times-Roman' font again, for example. The actual character outline programs are in the file Ûtir_____.pfbÛ, while Windows metric information may be found in % the file Ûtir_____.pfmÛ. These are the two files that {\ATM} copies to your hard disk when you install the font. The metric information in human readable plain {\ASCII} format may be found in the file Ûtir_____.afmÛ, while the {\TeX} metric information in compact binary form is in Ûtir.tfmÛ (note that for ease of use in {\TeX}, the Û.tfmÛ file name need not have the trailing underscores). % {\it not\/} extend the basic name with % The file Ûtir.tfmÛ is constructed using `Write TFM...' from {\DVIWindo}'s `Font' menu (see previous section). It can also be made using the {\AFMtoTFM} utility, or just copied from the \MathTime\ font folder on the CD. % diskette The relationship between the font file name (which is how you refer to the font in \TeX) and the Post\-Script FontName may most easily be ascertained by looking in the documentation that came with the font set, or in the font's {\AFM} file. % that came with the font. The {\AFM} file is a human readable plain {\ASCII} file that you can open in any editor, including `Notepad,' `WordPad,' `WinEdt' or {\PFE}. % You could also use the {\sc decode} utility on the Û.pfmÛ file. % If there is no {\AFM} file, % % (all quality fonts should come with {\AFM} files), % then use the utility {\PFBtoPFA} to convert the font's Û.pfbÛ file to % Û.pfaÛ format. You can then open the Û.pfaÛ file and look for % `FontName' in the first few lines. % % or look at the %!PS-Adobe comment line .... In any case, when you refer to the Times-Roman font in \yandytex, you use the name ÛtirÛ. % For example, Û\font\myfont=tir at 12.345ptÛ. Other {\TeX} systems may use other names for fonts. % The \yandytex\ System provides There is a convenient mechanism for dealing with this. If you set up a file called Ûtexfonts.mapÛ in one of the folders % directories listed in ÛTEXFONTSÛ --- or rather the corresponding `encoding specific' environment variable --- % (i.e. where your Û.tfmÛ files are kept --- % typically Ûc:\yandy\fonts\tfmÛ), then \yandytex, {\DVIWindo} and {\DVIPSONE} all refer to that file for font name aliases when they can't find the font under the name specified in the % Û.dviÛ file. source file. For example, Karl Berry has been assigning short names to fonts in an attempt to standardize font naming. If your source file uses `Karl Berry' names, then take the file Ûtexfonts.kbÛ supplied with \yandytex, and rename it Ûtexfonts.mapÛ. % As another example, note that Blue Sky Research's Textures\trademark\ uses its own unique set of short names for fonts. If you have a {\TeX} source file made up for Textures, then take the file Ûtexfonts.bsrÛ supplied with \yandytex, and rename it Ûtexfonts.mapÛ. You can, of course, also make up your {\it own\/} font name aliasing file. Each line in such a file contains two entries: the actual font file name, followed by the name used to refer to the font in {\TeX} (note order!). Lines starting with semicolon (or percent) are treated as comments. % names are limited to 32 characters ... \subsub{Using Lucida Bright + Lucida New Math fonts} % % Use the Ûinstall.batÛ batch file on the diskette to copy % the appropriate Û.tfmÛ and Û.texÛ files to your hard disk. % \yandytex\ System release 2.1 already has the needed Û.tfmÛ and Û.texÛ files in place, so you {\it don't\/} need to run the Ûinstall.batÛ batch file in the folder on the CD. % to install these. Simply install the fonts themselves using {\ATM} (or by dragging the Û.pfmÛ files to the ÛfontsÛ folder, if you are not using the {\ATM}font manager). Please refer to the instructions that come with the font set for additional details if needed. If you use plain {\TeX} or {\AMS}-{\TeX}, simply add a line of the form Û\input lcdplainÛ to your source file. With {\LaTeX}~2.09, use instead Û\input lcdlatexÛ --- or Û\input lcdltexpÛ % depending on whether if you have the `Lucida Bright Expert' font set as well. These files are already loaded in the Û\texinputÛ subfolder. % If you want to access the symbols normally defined by Ûamssym.texÛ, add Û\input amssymlb.texÛ. % (typically Ûc:\yandy\texinputÛ). % The required files are all supplied with the font set. For {\LaTeXe}, you can use % the Ûlucida.dtxÛ and Ûlucida.insÛ files Ûlucidabr.styÛ with the LY1 option from the {\PSNFSS} folder. % You could run {\TeX} on Ûlucida.insÛ, which will unpack % Ûlucida.dtxÛ into several files. % Make sure that ÛTEXINPUTSÛ includes the folder % directory % containing these new files % (or, move the files to a folder % directory % listed in ÛTEXINPUTSÛ). % Actually, these files have already been unpacked in the Û\psnfssÛ % subfolder of the Û\tex\latexÛ folder. % Just add Û\usepackage{lucidabr}Û to your source file between the Û\documentclassÛ and the Û\begin{document}Û. % In each case, You also need to account for the fact that {\TeX} makes assumptions about font encoding. If you use {\TEXNANSI} encoding with plain {\TeX} or {\LaTeX}~2.09, add a line of the form Û\input texnansiÛ (For Windows {\ANSI} use instead Û\input ansiacceÛ). % With {\LaTeXe}, use Û\usepackage[LY1]{fontenc}Û (for Windows {\ANSI} use instead Û\usepackage[ansinew]{texnansi}Û). \beginlines Û\usepackage[LY1]{fontenc} % specify text font encodingÛ Û\usepackage[LY1]{lucidabr} % switch text and math fontsÛ \endlines \noindent For sample usage, see Ûhello_LB.texÛ in Ûc:\yandy\texinputÛ. % which refers to Ûlucidabry.styÛ. % For ``options'' taken by the ÛlucidabrÛ package see Ûlboption.txtÛ in Û\doc-miscÛ. % For additional details please refer to the documentation % that comes with the font set. %%%% warning about ` and ' becoming `active' ? % \subsub{Using \MathTime\ + Times, Helvetica, and Courier fonts} \subsub{Using \MathTimeBold\ + Times, Helvetica \& Courier fonts} % With this font set, you receive a % special version of {\ATM} that includes the Times-Roman, Helvetica, and Courier font families. These text fonts are automatically installed when you install {\ATM}. On Windows~2000 without the {\ATM} font manager, install these fonts from the ÛpsfontsÛ folder in the {\ATM} folder on the CD % diskette using the method for installation of Type~1 fonts described earlier. % Make sure to install this version of {\ATM}. % needed for working with \MathTime. % Note that you will have to run the Ûprepare.batÛ batch file % on the diskette in a temporary folder % directory % on your hard disk before installing the math font from there using {\ATM} % (or Windows control panel). % more detail ? % batch files before using {\ATM} to install the fonts. % However, \yandytex\ System release 2.1 already has the needed Û.tfmÛ and Û.texÛ files in place, so you {\it don't\/} need to run the Ûtexttune.batÛ or Ûprepare.batÛ batch files on the CD folder. % diskette or % Please refer to the instructions that come with the font set for other details. % You also should run the Ûtexttune.batÛ file to select % proper Û.tfmÛ and Û.texÛ files. % Please refer to the instructions that come with the font set for details. If you use plain {\TeX} or {\AMS}-{\TeX}, simply add a line of the form Û\input mtplainÛ to your source file --- use Û\input mtplainxÛ if you also have the \MathTime\ Plus font set. For {\LaTeX}~2.09, use instead Û\input mtlatexÛ --- use Û\input mtltplusÛ if you also have the \MathTime\ Plus font set. % (there is no support for \MathTime\ Plus under {\LaTeX}~2.09 % because of limitations of font support and bugs in Û\boldmathÛ). These files % Ûmtplain.texÛ and Ûmtlatex .texÛ refer in turn to Ûmtmacs.texÛ or Ûmtplus.texÛ. % All of these files are already loaded in the Û\texinputÛ subfolder. % These macro files are supplied with the font set. With {\LaTeXe}, use % Ûmathtimy.dtxÛ and Ûmathtimy.insÛ files % Ûmathtimy.styÛ (or Ûmathtime.styÛ file with LY1 option (in the {\PSNFSS} folder). % directory. % You could run {\TeX} on Ûmathtimy.insÛ, which would unpack % Ûmathtimy.dtxÛ into several files. % Then repeat this process with Ûpsfontsy.insÛ and Ûpsfontsy.dtxÛ and % Ûyandytex.insÛ and Ûyandytex.dtxÛ % Actually, all of these files have already been unpacked in the Û\psnfssÛ % subfolder of the Û\tex\latexÛ subfolder. %% actually yyadd subfolder ??? % (Actually, we recommend instead using Ûmathtimy.insÛ % and Ûmathtimy.dtxÛ supplied with the font set). % % Make sure that ÛTEXINPUTSÛ includes the folder containing these files. % (or, move the files to a folder listed in ÛTEXINPUTSÛ). Add Û\usepackage{mathtime}Û to your source file to switch the math fonts. % (just make sure you do not have an ancient version of Ûmathtime.styÛ % lying around from pre-{\LaTeXe} days!). Note that the above {\it only\/} switches the math fonts; to also gain access to Times-Roman, Helvetica, and Courier for text % you need to run {\TeX} on Ûpsfontsy.insÛ to unpack Ûpsfontsy.dtxÛ, % and run {\TeX} on Ûyandytex.insÛ to unpack Ûyandytex.dtxÛ. % Before you `unpack' Ûpsfonts.dtxÛ, though, insert the contents of % Ûyandyext.texÛ in the indicated place. % Again, all of these files have already been unpacked for you % in the Û\psnfssÛ subfolder of the Û\tex\latexÛ subfolder. you need to % Then also add Û\usepackage{times}Û. % to switch the text fonts as well. % Finally, You also need to account for the fact that {\TeX} makes assumptions about font encoding. If you use {\TEXNANSI} encoding with plain {\TeX} or {\LaTeX}~2.09, add a line of the form Û\input texnansiÛ (For Windows {\ANSI} use instead Û\input ansiacceÛ). With {\LaTeXe}, use Û\usepackage[LY1]{fontenc}Û (for Windows {\ANSI} use instead Û\usepackage[ansinew]{texnansi}Û). \beginlines Û\usepackage[LY1]{fontenc} % specify text font encodingÛ Û\usepackage[LY1,mtbold]{mathtime} % switch math fontsÛ Û\usepackage{times} % switch text fontsÛ \endlines \noindent (omit the ÛmtboldÛ option if you do not have \MathTime\ Plus). For sample usage, see Ûhello_MT.texÛ in Ûc:\yandy\texinputÛ. % which refers to Ûmathtime.styÛ. % For ``options'' taken by the ÛmathtimeÛ package see Ûmtoption.txtÛ in Û\doc-miscÛ. % For additional details please refer to the documentation % that comes with the font set. %%%% warning about ` and ' becoming `active' ? %%%% warning about instability of PSNFSS \subsect{Advanced Topics} % The \yandytex\ System features several additional capabilities that we do not have space to cover in detail % ? in this introductory manual. % Refer to the separate Technical Addendum for details. %% possibly flush the following ??? % These manuals provide more detail --- % while lacking coverage of recently introduced features % such as `on the fly' font encoding, % and the new more standardized treatment of color. % The \yandytex\ System Manual you are reading now --- % while less detailed --- % is more up to date than the manuals for the individual system components. {\DVIWindo}, {\DVIPSONE}, and {\yandytex} % also each also have Ûreadme.txtÛ files that are copied % from the installation diskettes to their Û\docÛ subfolders % respective folders % directories during installation. Also look for any Ûnews.txtÛ files, which deal with new features, as well as work-arounds for bugs in other people's software. Complete lists of command line options may be found in Ûcommflag.txtÛ in Û\doc-miscÛ. % In this section we will touch upon a few of the more advanced topics. In the following we touch upon a few advanced topics. \subsub{Page Imposition and Direct to Plate} % Post\-Script output produced by {\DVIPSONE} follows Adobe's recommendations for Document Structuring Convention % Comments (\DSC). In addition, the output is completely {\it page independent\/} --- unlike output from many % virtually all Windows and Macintosh applications. This makes it easy to extract pages and re-arrange them without destroying the integrity of the Post\-Script job. The utility {\TWOUP} (see section~5.1) % absolute section reference exploits this % in order to make booklets ready for saddle back stapling (such as the manual you are now reading!). This also makes it easier for page imposition software to do its job. Page imposition is the process of placing all the pages in a signature together and writing them onto a single piece of film. This saves the cost of manually stripping up individual pages. Several companies provide page imposition software, including Adobe. % PREPS, see below... % and some damn company in Montreal, Quebec ... Some of these systems require specification of `filters,' mostly aimed at dealing with Post\-Script output that is {\it not\/} page independent. % These are typically not required for output from {\DVIPSONE}. % ScenicSoft, Inc. in Everett (Washington) ScenicSoft, Inc. (Everett, WA) offers a system called Preps\registered\ that is known to be compatible with output from {\DVIPSONE} {\it without\/} use of any % special `filters.' % Some page imposition software tends to be expensive, % and usual is something a service bureau might own. An additional cost-saving step is to print `direct to plate' --- bypassing the need for film. This obviously requires page imposition as an initial step. While it saves the intermediate production of film, it also increases the cost of mistakes. % Direct to plate technology shows a font in its true form. % thinness of Computer Modern % cost of mistakes. \subsub{Color Separation and Color Trapping} % color separation Quark % In order to print a document using colored text or inserted illustrations that use color, it has to be separated into its `process color' components. This involves taking one Post\-Script file calling for color and breaking it down into four `single color' or `black and white' Post\-Script files, one for each of the % four process colors (cyan, magenta, yellow and black). Several color separation systems are on the market, including Publisher's Prism\registered\ by InSight Systems % in Vienna (Virginia). (Vienna, VA). These typically operate by modifying the basic Post\-Script operators. The preamble of {\DVIPSONE} has been set up to allow this. Color separation software tends to be fairly expensive, and usually is something a service bureau might use. If you are on a budget, % , and willing to do a bit of work, you can used Quark XPress to separate your Post\-Script file. To do this, you need to output each page % that needs separation as a separate {\EPS} file, which is then imported into Quark XPress --- somewhat tedious, but effective. An important concern when using color is `trapping,' a geometric correction that should be applied to make the appearance of the printed result less sensitive to % a method used to deal with the lack of inevitable small % slight % imprecise mis-alignment of the four plates when printing. % of the four process colors will never be {\it perfectly\/} aligned. While some aspects of trapping could be handled in the {\TeX} source file --- or in the Post\-Script output from {\DVIPSONE} --- complete solutions are complex. The best bet is to use commercially available trapping systems. Several companies provide trapping software, including Adobe and Insight Systems. % also TeX issues - page breaks, footnotes, problems, cautions. \subsub{Adobe Acrobat PDF} % % Currently The best platform-independent format for distributing documents is Adobe Acrobat PDF. % lets stick our neck out! Free Acrobat readers for Windows, Macintosh, and Unix are available from Adobe % (from their {\FTP} site Ûftp.adobe.comÛ). at Ûhttp://www.adobe.com/readstep.htmlÛ. % readstep.html ??? % If you have Acrobat Exchange, You may be able to use the Acrobat PDFWriter from {\DVIWindo} just like an ordinary printer driver. But this is {\it not\/} recommended, % however, since the PDFWriter is limited in its capabilities, and since it includes {\it complete\/} fonts, which means your {\PDF} file contains copyrighted material that cannot be distributed. The best approach is to `Print to File' using {\DVIPSONE} % (which uses partial font downloading), and run the resulting PS % Post\-Script file through Acrobat Distiller. You can even `Print to File' into Distiller's `watched directory' to have it automatically convert the file when it is deposited. % (included in Acrobat 4.0). % with `Make Font Subsets' checked. % If you do this, use Û-kÛ and Û-*2Û and Û-*cÛ command line % options with {\DVIPSONE}. In Acrobat 3.0 or 4.0 use `Distiller{\down}Job Options' and select the `Font Embedding' tab. Check `Embed All Fonts' and `Subset fonts below.' Set this to 99\% (not the default 35\%). % But {\it first\/} add a file (perhaps called Ûsafe.psÛ) % containing the line % \beginlines % Û<< /SubsetFonts true /MaxSubsetPct 99 >> setdistillerparamsÛ % \endlines % \noindent % to the Distiller's ÛstartupÛ folder. % directory. You then can create compact PDF files that can be viewed (as well as printed) on all platforms listed above --- with % practically the same quality as the original. % (Because of problems with the current version of the Macintosh % Acrobat reader, you may want to use the Û-PÛ command line flag % with {\DVIPSONE} to suppress partial font downloading). For best results, use the Û-kÛ command line flag with {\DVIPSONE} and let Distiller find the fonts itself. Also use the Û-*2Û command line flag to avoid problems in Acrobat Reader with certain `control characters.' If you are using color, add the Û-*cÛ command line flag also (so that {\DVIPSONE} will use the `colorimage' PS operator). % See Ûacrofix.txtÛ in the Û\doc-miscÛ subfolder % subdirectory for up-to-date details. As explained in the section on {\DVIPSONE}, hypertext links are automatically translated to Acrobat ÛpdfmarksÛ by {\DVIPSONE}. Please refer to Ûacrobat.txtÛ regarding font licensing issues that arise when distributing {\PDF} files containing fonts. % well, there ARE a few bugs in this, but... % say more about automatic translation of hypertext jumps to pdfmarks %%% warn about font licensing issues ??? \subsub{Multiple Master Fonts} % Adobe Type Manager % ~3.0 and later supports installation of Multiple Master ({\sc mm}) fonts and the creation of new `instances.' A Multiple Master font is a parameterized font, with up to four control parameters, such as weight, width, and % design size. % optical size. You select an instance of an {\sc mm} font by choosing particular values for these parameters. You can use {\sc mm} instances just like `ordinary' Type~1 fonts after they are created by {\ATM}. % Since There are no {\AFM} files for {\sc mm} fonts --- % you have to use `Write TFM...' from {\DVIWindo} to create suitable Û.tfmÛ files. Just be careful to match the file names with the instances you are interested in using --- make a note of the file names reported by {\DVIWindo}. % In Windows~95, {\DVIPSONE} modifies the PS ÛfindfontÛ operator to automatically create font instances as required, and makes a note to include the corresponding {\sc mm} base font. % {\DVIPSONE} can also automatically download the required `{\sc pss}' stub for each font instance. Each base font called for is included (only once, of course). {\DVIPSONE} supports partial font downloading for {\sc mm} fonts, which can significantly reduce PS file size. {\sc mm} text fonts are reencoded `on the fly,' just like `ordinary' text fonts. See Ûmasters.txtÛ in the Û\doc-miscÛ subfolder % subdirectory for additional details. %% say more ? % Acrobat PDF, hypertext, font inclusion % service bureau's, fonts, preflight, adding previews % transfer on clipboard % fax output \section{Problems} % % refer to `readme.txt' and `news.txt' files ??? % Of the problems that will occur in using this software, the vast majority will prove to be related to \TeX\ itself. Unfortunately, we at \yandy\ cannot provide technical support for \TeX\ questions. % You'll have to ask your local guru, We're sorry about this --- but our relationship to \TeX\ is exactly like that of a seller of compilers to any other computer language: We'll support our product, but not the language itself. If you need help, you can read one of many books on \TeX, % we can give a list ... or send a message to the Ûcomp.text.texÛ news group on the InterNet. % or contact the \TeX\ Users' Group % (\TUG). % currently located in San Francisco... % {\TUG} can supply a list of \TeX perts that will be happy to help % (for a fee). % :=) We also maintain a list of `TeXperts' on our web site Ûhttp://www.YandY.comÛ. Click on `Resources.' % Our web site also has additional support files and a frequently asked question (FAQ) listing. % we can also supply a list of experts... % \subsect{Post\-Script Problems} \subsect{Post\-Script Problems and Verbatim Post\-Script} % Another area in which \yandy's ability to help is limited is with Post\-Script code that doesn't % quite do what you expect. % If you are a Post\-Script programmer and are inserting verbatim Post\-Script code into \TeX\ Û\specialÛs, please refer first to the Technical Addendum and Ûverbatim.txtÛ % on the {\DVIPSONE} diskette). in the Û\doc-miscÛ folder. % directory). %% is that where it is ??? % until the Technical Addendum is done % see the relevant section of the Technical Manual. If you are simply trying to use some off-the-shelf Post\-Script code (like rotation or figure inclusion macros), please check the macro package to ensure that it can work with {\DVIPSONE}. % In the case of {\LaTeXe}, just make sure you tell the `graphics' % package that the driver is {\DVIPSONE}, using % Ûgraphics.cfgÛ and Ûcolor.cfgÛ files If you are using the `graphics' or `graphicx' package in \LaTeXe, make sure you have Ûgraphics.cfgÛ and Ûcolor.cfgÛ files containing Û\ExecuteOption{dvipsone}Û % (or specify the Û[dvipsone]Û % (or Û[dviwindo]Û) % option in the Û\usepackageÛ command). (these files are normally already installed for you). % in Ûc:\yandy\tex\latex\graphicsÛ). Beyond that, unfortunately, there is generally % absolutely no standardization of the \TeX/Post\-Script interface, so what works perfectly well in {\DVIPSONE} is quite likely to produce unexpected results when used with say, Tomas Rokicki's {\DVIPS} and {\it vice versa} % (For instance, rotation is counterclockwise in {\DVIPSONE} and clockwise in {\DVIPS}). % ÛdvipsÛ. % (This particular problem can be dealt with by changing 90 to 270, % and 270 to 90, in Ûrotate.styÛ). Because we recognize that figure-inclusion macros are the most widely used (and useful) of the `Post\-Script' Û\specialÛs, we have written {\DVIWindo} and {\DVIPSONE} so they understand literally a {\it dozen\/} % more than ten different figure-inclusion calls. Thus, if you have been using {\sc dvips}, {\sc dvi2ps} (either by Senn, Li, or von Bechtolsheim), {\sc dvitops}, {\sc dvilaser/ps}\trademark, {\sc dvialw}, Textures\trademark, or either Oz\-\TeX\ or Psprint by Andrew Trevorrow, you will find that the same \TeX\ code will work with {\DVIPSONE}. If you have been using some other system, then you will % almost certainly have most likely have to either alter your macros or change your % \TeX\ source files. % Fortunately, if you use higher level interfaces --- like the \LaTeXe\ graphicx or graphics packages, Ûepsf.texÛ or Ûpsfig.styÛ --- there generally won't be any problems. If you are using Timothy Van Zandt's PSTricks, make sure to use the modified Ûpstricks.proÛ and Ûpst-show.proÛ % (PS prologs) % (Post\-Script prologs) and Ûpstricks.conÛ (a {\TeX} configuration source file) supplied (Û.proÛ files are in the Û\psÛ subfolder % subdirectory and Û.conÛ files in the Û\texinputÛ subfolder). % subdirectory). % These files have been tuned for use with {\DVIPSONE}. Note that neither {\DVIWindo} nor Windows includes a Post\-Script interpreter, so output produced by `Post\-Script' trickery will generally {\it not\/} be shown in {\DVIWindo}. % as it will print on a Post\-Script device. To preview output of this form, `print to file' using {\DVIPSONE}, then preview the resulting PS file using Transverter Pro\registered\ from InSight Systems, or GhostScript. % or Acrobat Reader after converting to {\PDF} format using Distiller. % Yet another alternative is to generate a Post\-Script file using {\DVIPSONE}, pass it through Acrobat Distiller and view the resulting {\PDF} file using Acrobat Reader. The exceptions to the above statement are PS rotation and scaling commands emitted by the {\LaTeXe} graphics package, which {\it are\/} recognized by DVIWindo % and translated to equivalent CTM \specials and used to control on screen output --- but only when running in Windows~NT. Note that some simple graphics are more easily produced % prepared % done using {\sc tpic} Û\specialÛs. {\sc tpic} is device independent and is supported by both {\DVIPSONE} and {\DVIWindo} (as well as some other drivers) --- so you will be able to see the results on screen as well as on the printed page. {\sc tpic} Û\specialÛs are produced, for example, by the {\LaTeX} ÛeepicÛ/ÛepicÛ package. Refer to the Technical Addendum (or Ûtpicspec.txtÛ) for details, and Ûtpictest.texÛ for examples. % sample usage. % PSFrag? XY-Pic? % should refer to Ûtpicspec.txtÛ instead ? % refer to tpic... file ??? \subsect{Some Previewing Problems} % If nothing shows when you open a Û.dviÛ file, it may be because somehow you have zoomed in on an area off the printed page. Try to use `File{\down}Default Scale' to reset the scale to something more reasonable. %% What if nothing appears on screen when you launch DVIWindo? If {\DVIWindo} does not show up on screen when you launch it, then the screen position and scale recorded in Ûdviwindo.iniÛ may have been corrupted somehow. % but it does show up in the Task Manager list... Read Ûdviwindo.iniÛ into a plain {\ASCII} text editor and comment out all lines referring to `Size' and `Mapping' (by adding a semicolon (;) at the beginning of the line). %% comment out Size, Mapping, NotFirstSize, NotFirstMapping ? If you get grey blocks, colored fonts, or other strange things when you are not expecting them, then your `Preferences' may have gotten warped in some peculiar way. Use `File{\down}Factory Defaults' to temporarily reset preferences to their `out of the box' states. If your `rules' (rectangular blocks such as division lines) look `too thick' at normal scale, or appear outlined as opposed to filled when magnified, then make sure to check % `Fonts{\down}Fill Rules.' `Special{\down}Fill Rules.' % If text in printed output looks ragged and not really black, then % check that you do {\it not\/} have `Fonts{\down}Color Fonts' checked. %% this no longer works this way, right ??? If you have problems interfacing the \yandytex\ System with other % people's software, please check the Ûnews.txtÛ and Ûreadme.txtÛ in the Û\docÛ subfolder of % that came with the particular system component you are having problems with. Sometimes there may be late-breaking news on bugs in the latest releases of other people's software. % various applications. If the text color looks wrong, try unchecking `Fonts{\down}Color Fonts.' % \subsect{Memory Problems} \subsect{Memory Problems and Sharing Violations} % If you get a memory allocation error % every time when you attempt to run \yandytex, then you probably have too little {\it free\/} extended {\RAM} (a very rare problem these days). \yandytex\ needs at least 2~Meg of free extended {\RAM} when it runs --- more for ini-{\TeX}, when using many fonts, or when using complex formats. % If you don't have much {\RAM}, % but do have a lot of hard disk space, % you should set up a large permanent swap file. % % In the `Main' program group, choose `Control Panel,' then `386 Enhanced,' % then `Virtual Memory.' % Then make the largest permanent swap file you can % (You may need to defragment your hard disk first, since otherwise % the size of the permanent swap file may be limited by available % contiguous space on your hard disk). % Click on `Start' and then select `Settings{\down}Control Panel' % Double click on `System,' then select the `Performance' tab. % Under advanced settings, click on `Virtual Memory'. If you get intermittent allocation errors, % then you are probably running \TeX\ % from inside Windows and then you may have too many other windows open --- or you've been using ill-behaved programs that don't return all the system resources they use upon termination. In the first case, simply close some windows; in the second, there is nothing to do but exit and relaunch Windows. % --- although there is a shareware program called % Hogs that can reallocate system resources. Sharing violations and `Ûpermission deniedÛ' errors % and sharing violations % and errors related to stack overflow ? are usually caused by attempting to open a file already open in another application. Unfortunately some applications keep files open % that % you are working on (perhaps in an attempt to try and prevent other applications from modifying them). % % flush the following maybe ? % % Ghostscript is a big offender; if you have opened Ûtest.psÛ in % Ghost\-script and try to rerun {\DVIPSONE} on Ûtest.dviÛ, you will get a % ÛSharing violationÛ message. If you are using Ghostscript to debug % Post\-Script code, note that you must close Ghostscript every time there's % an error before you can recreate a Û.psÛ file with the same name. % Some Windows editors like Write and Micro\-Soft Word prevent other programs from using files they have open. Others, like `Notepad,' `WinEdt,' {\PFE}, and Epsilon, do not present such problems. You may also on rare occasions get a benign sharing violation error if {\DVIWindo} happens to refresh the display just at the {\it exact\/} moment that {\TeX} is trying to write a new Û.dviÛ file. \subsect{Environment and Preferences Problems} % If {\DVIWindo} begins to behave strangely, it may be that the file Ûdviwindo.iniÛ (in the Û\windowsÛ folder) file has become corrupted. First try using `File{\down}Factory Defaults.' If this does not help, exit {\DVIWindo}, make a backup copy of Ûdviwindo.iniÛ, then remove the whole Û[Window]Û section from Ûdviwindo.iniÛ. % rename Ûdviwindo.iniÛ to, say, % Ûdviwindo.ibkÛ (you will need this later), and relaunch. % If {\DVIWindo} cannot find its Û.iniÛ file upon launch, % then % it will build a new one. {\DVIWindo} will rebuild the Û[Window]Û section next time it is launched. If you can't find the Û.dviÛ file you created, check whether there is an environment variable called ÛTEXDVIÛ. Remove it. If you want all Û.dviÛ files to be written into a common directory, then add a ÛWorkingDirectoryÛ entry to the Û[Window]Û section of Ûdviwindo.iniÛ. % WorkingDirectory=nul special case? % discuss confusion when viewing If your preview doesn't seem to change after you edit and re-{\TeX} a file, then maybe you have {\it two\/} copies of the Û.dviÛ file in two different places and you are looking at one, while {\TeX} is writing the other! In this case you won't see {\DVIWindo} refreshing the screen. Some problems will occur simply because the environment variables have been set up incorrectly --- or more typically because you've changed something without changing these variables. % If, for instance, \TeX\ complains that it can't find a {\it file} the first thing to do is to look at the environment variables in Ûdviwindo.iniÛ --- particularly ÛTEXINPUTSÛ (or rather the corresponding `format specific' environment variable). If \TeX\ complains that it can't find a {\it font\/} the first thing to do is to look at the environment variables in Ûdviwindo.iniÛ --- particularly ÛTEXFONTSÛ (or rather the corresponding `encoding specific' environment variable). This sort of thing often happens when you start using a new macro package --- \AmSLaTeX, say --- and you forget that you have to include the relevant folder in your ÛTEXINPUTSÛ variable (or rather the appropriate `format specific' ÛLATEXÛ variable). Another environment problem occurs when {\DVIWindo} can't find {\DVIPSONE}. In this case the `Use DVIPSONE' check box is greyed out in the `Print' dialog box. To solve this problem, set the environment variable ÛPREPATHÛ % (or ÛVECPATHÛ) to point to the {\DVIPSONE} folder. % directory. %% also discuss problems due to `format specific' TEXINPUTS... % If changes you make to ÛTEXINPUTSÛ have no effect on what % folders % directories % {\TeX} searches then you may have `format specific' % environment variables that override ÛTEXINPUTSÛ % (e.g. ÛLATEXÛ is used for {\LaTeXe} instead). Sometimes you want files output by {\TeX} to appear in the same directory as the source file that {\TeX} is reading, even though you have set up a ÛWorkingDirectoryÛ. This happens particularly when creating new `formats.' In this case you may want to temporarily uncheck % `Fonts{\down}Working Directory.' `Special{\down}Working Directory.' %%% expand on temporary changing Working Directory ??? %%% particularly when running ini-{\TeX} ??? \subsect{Font Problems} % \subsect{Font Problems and Encoding Problems} % Use `Fonts{\down}Show Font' to check out the installed fonts % that you have installed, and to see their character layout (You can also use the Windows applet `Character Map' --- in the `Accessories' group. % i.e. `Start{\down}Programs{\down}Accessories'). % in the `Accessories' group --- if installed). % --- for a similar purpose If a font does not show up in the list of fonts presented, then it is not properly installed, or not `activated' in ATM, or the font's Û.pfbÛ or Û.pfmÛ files are corrupted, or the font is not {\ATM} compatible. % (even if it {\it is\/} listed in the `[Fonts]' section of % Ûatm.iniÛ or Ûwin.iniÛ). %% merely being listed in {\ATM} control panel is not sufficient... If `Write TFM\ellipsis' or `Write All TFM\ellipsis' fail, check that the environment variables ÛTEXFONTSÛ and ÛVECPATHÛ are set up correctly, and that the {\AFMtoTFM} utility is accessible from {\DVIWindo} (i.e. in the Û\utilÛ subfolder, in the Û\dviwindoÛ folder, or in the folder specified by ÛPREPATHÛ). % or ÛVECPATHÛ). %%% check ??? where is it really ??? Please make absolutely certain that your font files are true {\ATM} compatible fonts in Adobe Type~1 format. There are many share- and freeware fonts that, simply, will not work with {\ATM}. There are others that will work with some Post\-Script interpreters --- but not on, say, Linotronic RIPs, so when you go to make your final copy at the service bureau to give the printer you might discover that a font or two has been `Couriered out' throughout the book! (PS interpreters use the Courier font when they can't select a font) If you want to check that fonts % are used as expected appear exactly where you had planned in your document, select `Fonts{\down}DVI File Fonts' and check `Fonts{\down}Color Fonts.' Fonts are then color coded, which makes it easier to see where changes in font selection occur. You can also click on a font in the list of fonts and have all occurrences of that font shown in reverse video. Conversely you can `Shift-Click' on a character in the window and have all characters using that font appear % switched to in reverse video. \tip % Advanced Feature: For a real blast, `Ctrl-Shift-Click' on a character, to get its full pedigree, including character code, and advance width (This only works while `DVI File Fonts' is checked). % discuss command line flag in DVIWindo ? % Astronomical and phonetic symbols fonts have proven especially difficult. % If you do decide to use an `iffy' font, test it thoroughly on every device % you might need to image it on before you are completely committed to it. % If the font is a valid Type~1 font and still doesn't work, please inform \yandy. By the way, Windows does {\it not\/} like it if % operate well when you have TrueType and Type~1 fonts of the same name installed. % Further, please note that some TrueType versions of the Computer Modern fonts % have incorrect metrics % and incorrect flag settingsd. % (in extreme cases, all characters in a font have the same width!). % Also, some TrueType versions of the Computer Modern fonts are incorrectly labelled as being `text' fonts (e.g. they have a Type 3.1 `cmap'). This in essence requests Windows to reencoded the fonts to `Windows {\ANSI}' encoding, which is not possible since TrueType fonts cannot be reencoded. Confusion ensues (particularly in the Acrobat Reader), when this happens. Make sure to first uninstall {\it and\/} remove all such fonts! % On rare occasions, {\ATM} `Quick Load Cache' % of font information % gets confused. % (particularly if you have many fonts, and `Remove' % and `Add' the same font repeatedly after making changes). % In this case, %, exit Windows, % delete the file Ûatmfonts.qlcÛ in the Û\psfontsÛ folder, % directory % exit Windows and relaunch Windows % (note that not all versions of {\ATM} use such a cache file). % {\ATM} will rebuild this file (which may take some time % since it has to read all Û.pfbÛ and Û.pfmÛ files % listed in Ûatm.iniÛ). % in order to do this In the case of {\ATM}~4.0 the `registry' file Ûatmreg.atmÛ may get confused. You can dump it out using the Ûatmregan.exeÛ utility to check it. Often removing and reinstalling fonts corrects such problems. %% may not be relevant to recent versions of ATM ??? % Font problems related to encoding or character layout % can usually be traced to mismatched Û.pfbÛ, % Û.pfmÛ, and Û.tfmÛ files. You can use the utility {\DECODE} % (described in section~5.2) %% absolute explicit section ? % to attempt to determine which encoding each of the different font files uses. \subsect{Printing and Application Calling Problems} {\DVIPSONE} will not be able to print if you have something like a `print monitor' permanently connected to your printer port. Check the Ûrun=...Û and Ûload=...Û lines of the Û[Windows]Û section of Ûwin.iniÛ. To print to a networked PostScript printer using {\DVIPSONE}, there must be a {\sc unc} or ``share'' name available (basically you must be able to print by ÛCOPYÛ-ing a file from the command prompt to a suitable `port'). % See Ûnetprint.txtÛ in Û\doc-miscÛ. For problems with network printers refer to the files Ûnetwork.txtÛ and Ûnetprint.txtÛ in Û\doc-miscÛ. If you can't figure out what goes wrong when {\DVIWindo} calls {\TeX}, {\DVIPSONE} or some other program, then temporarily check `Show WinExe' in the `Fonts' menu. This forces {\DVIWindo} to show you exactly how it is calling that program. If the window of the program called goes away too quickly to see what went wrong, temporarily check `Pause WinExe' in the `Fonts' menu. This will force \yandytex, {\DVIPSONE} and {\AFMtoTFM} to pause and show command line arguments when starting --- and then again to pause when they are done. %% is there a better place for this ??? \section{Utilities} % Several useful % {\DOS} command line utilities are supplied with the \yandytex\ System. Most of these are needed only in unusual situations. % however. These utilities give a usage summary when invoked with Û-?Û on the command line. % Some of these utilities are in the {\DVIPSONE} folder % directory % and some in the {\DVIWindo} folder. % directory. The utilities are in the Û\utilÛ subfolder. \subsect{Twoup} % {\TWOUP} takes advantage of the fact that the Post\-Script produced by {\DVIPSONE} is not only resolution-independent and {\DSC} compliant, but {\it also\/} completely page independent. % therefore completely page independent) It puts two (or more) logical pages on each physical sheet of paper. Fitting the % logical pages on the paper in the most space-efficient manner may, however, take some trial and error. %%%%%% rewrite the following using -x=.. twice --- DONE {\TWOUP} normally % {\it automatically\/} reduces the logical page to fit `two up' on the paper; if you wish to override this, use the command flag Û-M=1Û . This sets the magnification to 1 (You can specify {\it relative\/} magnification using % lower-case Û-m=...Û instead of Û-M...Û). % which case the magnification specified is {\it relative\/} to the default % rather than {\it absolute\/}). % Then, however, After deciding on the magnification, you will have to adjust the margins in order to fit both pages nicely side-by-side on the paper. % For a standard book size, run For this manual, first of all in \TeX, we set Û\hsize=26pcÛ, Û\vsize=502ptÛ, % 41 * 12 + topskip, which is 10pt ? and then used {\DVIPSONE} to make a Post\-Script file. % you might want to run {\DVIPSONE} with the flag Û-x=32Û, moving every % page to the right by 32 pts, and We then used {\TWOUP} with the flags Û-M=1Û, Û-d=lpt1Û, Û-y=-80Û, % with Û-x=-90Û, and again Û-x=70Û, with Û-x=-82Û, and again Û-x=78Û, which moves every page down by 80 pts, every left page left by -82 pts, and every right page right by 78 pts. % right page to the right and left page to the left by 82 pts and % all pages up 17 pts. % For this manual, we used Ûdvipsone -x=112 manualÛ followed by Ûtwoup % -m=1.545454124 -y=-109 -g -d=top.psÛ and Ûtwoup -m=1.545454124 -y=-109 -h % -d=bot.psÛ % (in \TeX, we set Û\hsize=26pcÛ, Û\vsize=502ptÛ, % Û\hoffset=-3pcÛ, and Û\voffset=-2.5pcÛ). % Then we send Ûtop.psÛ to % our printer, take the output pages and place them in the input tray, and % print Ûbot.psÛ. % Then we send Ûtop.psÛ to our printer, take the output pages and place % them in the input tray, and print Ûbot.psÛ. For % printing on an HP LJ 4M Plus printer, we also use the flags Û-vzgrÛ on the first run of {\TWOUP}, take output pages and place them face {\it up\/} in the input tray, and then run {\TWOUP} again with flags Û-vzhÛ. For printing on a QMS PS 815 MR printer we leave out the ÛrÛ in Û-vzgrÛ and place the pages facing {\it down}. In either case, the result is, as you see, a correctly ordered manual printed on both sides of 8\onehalf"\times11" paper. % $8{1\over2}\times11$ paper. %%% remove DECODE ? %%% remove SERIAL ? % \subsect{Serial} % % If you have an older Post\-Script printer connected to a serial port that does % not use hardware flow control, you may have to use software flow control with % {\SERIAL}. % % This utility may also be useful if you need to read information sent back % over the serial port by the Post\-Script interpreter in the printer. % Example: % Ûserial -d=COM1Û \angi{filename}. % % Note: {\SERIAL} cannot be used in Windows~NT % since it directly accesses the serial port hardware. % DOWNLOAD \subsect{TIFFTAGS and WMFSPY} % {\TIFFTAGS} can be used to dump out the `tags' in a `Tagged Image File Format' ({\TIFF}) file. If you use the Û-vÛ command line flag you will get all tags, including number of rows and columns, bits per sample, samples per pixel and so on. Without the Û-vÛ on the command line, {\TIFFTAGS} shows only basic size information. This is useful in reserving space in a {\TeX} document for a figure % to be inserted using the Û\special{insertimage: ...}Û syntax). {\WMFSPY} can be used to recover the header information in a placeable Windows Meta File ({\WMF}). This is useful in reserving space in a {\TeX} document for a figure % to be inserted using the Û\special{insertmf: ...}Û syntax). %%% remove PKtoPS ? \subsect{PKTOPS} % {\PKtoPS} creates a Type 3 % (bitmapped) Post\-Script PS font file from a Û.pkÛ bitmapped font. %% define ? This is not particularly recommended, since you must either create the Post\-Script font from a high-resolution Û.pkÛ file (1000 dpi or better), or live with low-resolution fonts mixed in among your outline fonts. However, some fonts exist only in Û.pkÛ form. Example: Ûpktops manfntÛ. This creates a file called Ûmanfnt.psÛ in the current folder. % directory. Note that {\DVIWindo} {\it cannot\/} display Type 3 fonts. If you use a lot of them, you will want to turn off `Complain Missing Fonts' and `Complain Bad Encoding' in the `Preferences\ellipsis' menu. % FMP ad ? \newpage %%%%%%%%%%%%%%%%%%%%%%% TeX n ANSI %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % \font\lbr=lbr at 20pt % \font\lbr=lbr at 19pt \font\lbrx=lbrx at 18pt \section{TeX 'n ANSI encoding (character layout)} %%%% move Lslash ??? \lbrx \vskip .1in % \vskip .05in \settabs 18 \columns % was .11in for 19pt \+&&0&1&2&3&4&5&6&7&8&9&A&B&C&D&E&F\cr \vskip .25in % \+0&&\char000&\char001&\char002&\char003&\char004&\char005&\char006&\char007&\char008&\char009&\char010&\char011&\char012&\char013&\char014&\char015\cr % \+0&&.&.&.&.&.&\char005&\char006&\char007&.&\char009&.&\char011&\char012&\char013&\char014&\char015\cr % \+0&&&&&&&\char005&\char006&\char007&&\char009&&\char011&\char012&\char013&\char014&\char015\cr \+0&&&\char001&&&\char004&\char005&\char006&\char007&\char008&&&\char011&\char12&&\char014&\char015\cr % \+0&&&&&&\char009&\char005&\char006&\char007&\char013&&&\char011&\char012&&\char014&\char015\cr \vskip .125in \+1&&\char016&\char017&\char018&\char019&\char020&\char021&\char022&\char023&\char024&\char025&\char026&\char027&\char028&\char029&\char030&\char031\cr \vskip .125in \+2&&\char032&\char033&\char034&\char035&\char036&\char037&\char038&\char039&\char040&\char041&\char042&\char043&\char044&\char045&\char046&\char047\cr \vskip .125in \+3&&\char048&\char049&\char050&\char051&\char052&\char053&\char054&\char055&\char056&\char057&\char058&\char059&\char060&\char061&\char062&\char063\cr \vskip .125in \+4&&\char064&\char065&\char066&\char067&\char068&\char069&\char070&\char071&\char072&\char073&\char074&\char075&\char076&\char077&\char078&\char079\cr \vskip .125in \+5&&\char080&\char081&\char082&\char083&\char084&\char085&\char086&\char087&\char088&\char089&\char090&\char091&\char092&\char093&\char094&\char095\cr \vskip .125in \+6&&\char096&\char097&\char098&\char099&\char100&\char101&\char102&\char103&\char104&\char105&\char106&\char107&\char108&\char109&\char110&\char111\cr \vskip .125in % \+7&&\char112&\char113&\char114&\char115&\char116&\char117&\char118&\char119&\char120&\char121&\char122&\char123&\char124&\char125&\char126&\char127\cr \+7&&\char112&\char113&\char114&\char115&\char116&\char117&\char118&\char119&\char120&\char121&\char122&\char123&\char124&\char125&\char126&&\cr \vskip .125in % \bye \+8&&\char128&\char129&\char130&\char131&\char132&\char133&\char134&\char135&\char136&\char137&\char138&\char139&\char140&\char141&\char142&\char143\cr \vskip .125in \+9&&\char144&\char145&\char146&\char147&\char148&\char149&\char150&\char151&\char152&\char153&\char154&\char155&\char156&\char157&\char158&\char159\cr \vskip .125in \+A&&\char160&\char161&\char162&\char163&\char164&\char165&\char166&\char167&\char168&\char169&\char170&\char171&\char172&\char173&\char174&\char175\cr \vskip .125in \+B&&\char176&\char177&\char178&\char179&\char180&\char181&\char182&\char183&\char184&\char185&\char186&\char187&\char188&\char189&\char190&\char191\cr \vskip .125in \+C&&\char192&\char193&\char194&\char195&\char196&\char197&\char198&\char199&\char200&\char201&\char202&\char203&\char204&\char205&\char206&\char207\cr \vskip .125in \+D&&\char208&\char209&\char210&\char211&\char212&\char213&\char214&\char215&\char216&\char217&\char218&\char219&\char220&\char221&\char222&\char223\cr \vskip .125in \+E&&\char224&\char225&\char226&\char227&\char228&\char229&\char230&\char231&\char232&\char233&\char234&\char235&\char236&\char237&\char238&\char239\cr \vskip .125in \+F&&\char240&\char241&\char242&\char243&\char244&\char245&\char246&\char247&\char248&\char249&\char250&\char251&\char252&\char253&\char254&\char255\cr %%%%%%%%%%%%%%%%%%%%%%% TeX n ANSI %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \newpage % ? \rm \markbothsame{} % get rid of headers ? % \blankpage % \blankpage % \newpage % \ifodd\pageno\immediate\write16{Odd page \number\pageno}\blankpage % \else\immediate\write16{Even page \number\pageno}\fi \newcount\pagemod \loop \pagemod=\count0 \advance\pagemod by 2 \divide\pagemod by 4 \multiply\pagemod by 4 \advance\pagemod by -\count0 \advance\pagemod by -2 \ifnum\pagemod<0 \immediate\write16{Blank page \number\pageno} \blankpage \repeat %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Document TOC starts %%%%%%%%%%%%%%%%%%%%%%%% % \bye % \centerline{{\titlef\let\sixrm\eighttitle\yandytex\ System}} % \vskip7pt \tocsect{1}{Introduction}{1} \tocsub{1.1}{Necessary Legal Stuff}{2} \tocsub{1.2}{Conventions}{2} \tocsub{1.3}{Requirements}{3} \tocsect{2}{Installation}{4} % \tocsub{2.1}{ATM compatible Systems --- Installing Fonts}{4} % \tocsub{2.1}{Systems with ATM --- Installing Fonts}{4} \tocsub{2.1}{Installing fonts with ATM}{4} % \tocsub{2.2}{Systems without ATM --- Conversion to TrueType}{5} % \tocsub{2.2}{Systems without ATM --- Windows~2000}{5} \tocsub{2.2}{Installing fonts without ATM}{5} \tocsub{2.3}{Fonts Supplied with the System}{5} % 6 \tocsub{2.4}{Installing the Y\hbox to.35\p@ {\hss \sixbf \&\hss }Y\ TeX\ System Itself }{6} % \tocsubsub{2.4/1}{Quesions and Answers during Installation}{7} \tocsub{2.5}{Quick Tutorial}{8} \tocsect{3}{Using the Y\hbox to.35\p@ {\hss \sixbf \&\hss }Y\ TeX\ System}{10} \tocsub{3.1}{The Edit--T\kern -.1667em\lower .5ex\hbox {E}\kern -.125emX--Preview Cycle}{11} \tocsub{3.2}{The {\secttt dviwindo.ini} File}{11} \tocsubsub{3.2.1}{What the Environment Variables Mean}{13} % \tocsubsub{3.2.2}{The [Window] section of {\secttt dviwindo.ini}}{16} \tocsub{3.3}{DVIWindo}{17} \tocsubsub{3.3.1}{Mouse Tricks and Accelerator Keys}{18} \tocsubsub{3.3.2}{Customizing the `TeX' Menu}{19} % \tocsubsub{3.3.3}{The [Applications] section of {\secttt dviwindo.ini}}{21} \tocsub{3.4}{Y\hbox to.35\p@ {\hss \sixbf \&\hss }Y\ TeX}{22} % \tocsubsub{3.4.1}{Making new T\kern -.1667em\lower .5ex\hbox {E}\kern -.125emX formats --- running ini-T\kern -.1667em\lower .5ex\hbox {E}\kern -.125emX}{23} % \tocsubsub{3.4.2}{`Foreign Language Keyboards --- Accented Characters}{25} \tocsub{3.5}{DVIPSONE}{27} % 26 % \tocsubsub{3.5.1}{Printing to File}{27} % \tocsubsub{3.5.2}{Selecting more than one page range to print}{27} flushed \tocsub{3.6}{Graphics, EPS, TIFF, BMP, WMF, Color, and Hypertext}{29} % \tocsubsub{3.6.1}{Including {\dsc TIFF} and Windows Meta\-File Images}{30} \tocsubsub{3.6.1}{Including {\dsc TIFF}, {\dsc BMP} and {\dsc WMF} Images}{31} % \tocsubsub{3.6.2}{Color}{31} % \tocsubsub{3.6.3}{Hypertext Links}{33} % \tocsubsub{3.6.3}{Device Independent Rotation and Scaling}{34} \tocsub{3.7}{Fonts}{36} \tocsubsub{3.7.1}{Font Encoding and Character Layout}{36} \tocsubsub{3.7.2}{Installing and Using Fonts}{38} \tocsubsub{3.7.3}{Font Name Aliasing}{40} % 40 \tocsubsub{3.7.4}{Using Lucida Bright + Lucida New Math fonts}{41} % 41 \tocsubsub{3.7.5}{Using {\tibi Math\-T\kern -2pt\i me}\ + Times, Helvetica \& Courier fonts}{42} \tocsub{3.8}{Advanced Topics}{43} % \tocsubsub{3.8.1}{Page Imposition and Direct to Plate}{42} % \tocsubsub{3.8.2}{Color Separation and Color Trapping}{43} % \tocsubsub{3.8.3}{Adobe Acrobat PDF}{43} % \tocsubsub{3.8.4}{Multiple Master Fonts}{44} \tocsect{4}{Problems}{45} % 45 \tocsub{4.1}{Post\-Script Problems and Verbatim Post\-Script}{46} \tocsub{4.2}{Previewing Problems}{47} \tocsub{4.3}{Memory Problems and Sharing Violations}{47} % 47 \tocsub{4.4}{Environment and Preferences Problems}{48} \tocsub{4.5}{Font Problems}{49} \tocsub{4.6}{Printing and Application Calling Problems}{50} \tocsect{5}{Utilities}{50} % \tocsub{5.1}{Twoup}{50} % \tocsub{5.2}{Decode}{51} % \tocsub{5.4}{TIFFTAGS and WMFSPY}{52} % \tocsub{5.4}{PKTOPS}{52} % \tocsub{5.5}{Font Manipulation Package (Advertisement)}{52} \tocsect{6}{TeX 'n ANSI encoding (character layout)}{53} \vfill \eject \bye %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % The following may be a bit long ...99/July/26 \subsect{Decode} % {\DECODE} reaches inside Û.pfbÛ, % Û.pfaÛ, Û.pfmÛ, and Û.tfmÛ files to see what encoding is in use. For instance, to check whether or not Times-Roman is set up properly to use the % ÛtexnansiÛ {\TEXNANSI} encoding, run the following commands: % (in the Û\psfontsÛ directory, or wherever you keep your Û.pfbÛ files) % (in the Û\psfonts\pfmÛ subdirectory or equivalent) % (in the Û\yandytex\tfmÛ subdirectory, or wherever you keep your Û.tfmÛ files) \beginlines Ûdecode c:\psfonts\tirÛ Û Û The resulting text should end with the two lines: ÛAdobe Standard EncodingÛ Û(which means ATM will reencode to Windows ANSI!)Û \endlines \beginlines Ûdecode c:\psfonts\pfm\tirÛ Û Û This should indicate Windows {\ANSI} encoding, ending with: ÛHence probably Windows {\ANSI} if a plain text fontÛ ÛEncodingScheme (based on flags): MS Windows ANSIÛ \endlines \beginlines Ûdecode c:\yandy\fonts\tfm-ps\tirÛ Û Û This should indicate {\TEXNANSI} encoding: ÛClaims to use `TeX typewriter and Windows ANSI' coding schemeÛ ÛClaims to use `texnansi' encoding vectorÛ \endlines % Ûdecode c:\yandytex\tfm\tirÛ \noindent (in the above, substitute the folders % directories you use for Û.pfbÛ, Û.pfmÛ, and Û.tfmÛ files respectively). The result of the last test will be different, of course, if you use some encoding other than {\TEXNANSI}. % ÛtexnansiÛ. The above is the usual result for Type~1 {\it text\/} fonts. If you have a font (like Symbol or Zapf Dingbats) that is {\it not\/} a text font, then you may want to have access to the Û.afmÛ file, as follows: \beginlines Ûdecode -a=c:\psfonts\afm\zd c:\psfonts\zdÛ Û Û Result should be: ÛEncoding seems to match that in AFM fileÛ \endlines \beginlines Ûdecode -a=c:\psfonts\afm\zd c:\psfonts\pfm\zdÛ Û Û Result should indicate `FontSpecific' encoding, ending with: ÛHence probably Font Specific unless its a text fontÛ ÛEncodingScheme (based on flags): FontSpecificÛ \endlines \noindent Because of the wild differences in the kind of information in the different types of font files, % each type of file, {\DECODE} may sometimes be unable to express an opinion. If you have doubts about the kind of encodings in the various files, reinstall the fonts from their original disk, and recreate the Û.tfmÛ file (In rare cases you may {\it also\/} need to delete {\ATM}'s `Quick Load Cache' file Ûatmfonts.qlcÛ in the Û\psfontsÛ folder). % directory). % in order purge old metrics). %% flush following ??? highly optional % \subsub{Page selection} \subsub{Selecting more than one page range to print} % % Page selection You can select a subrange of pages when printing from {\DVIWindo}, % You can, however, select but only one range at a time: % It is, however, not possible to select more than one range at a time; you have to print each subrange separately. % Well, if the pages are in a single range (380--399, say), you can fill in % {\DVIWindo}'s `Print' dialog box. % If you have several ranges, then you can do this several times. % % However, there are % three % some possibilities: % \nlist % \item Type several long command lines, being very, very careful not to make % any typos. % \item Create a batch file to contain the various long command lines. % \item Use Ûdvipsone.cmdÛ, an auxiliary file that can contain command-line % parameters and arguments. However, you must then be careful to delete (or % comment out) the page-selection commands after you're done, lest every job be % limited to those pages. \endlist You can select more than one subrange if you use {\DVIPSONE} directly from the command line. % {\DOS} prompt. % The page-selection commands for {\DVIPSONE} are Û-b=Û\angi{starting page number} Û-e=Û\angi{ending page number}, where the page number refers to Û\count0Û, the register plain \TeX\ and \LaTeX\ use to create page numbers, or alternatively Û-B=Û\angi{starting page number} Û-E=Û\angi{ending page number}, where the page number refers to the physical count within the Û.dviÛ file. You cannot mix lower- and uppercase page-selection commands. The command line arguments Û-b=...Û and Û-e=...Û may appear several times to specify several different page ranges % (If you use a batch file to call {\DVIPSONE}, you will be restricted to ten command line arguments). %%% flush this detail ? % Selection of pages when printing many subranges can get a bit involved, % however, especially since {\DOS} limits the length of the command line % to 128 bytes. % So what do you do if you want to print 20 miscellaneous pages of a % 400-page Û.dviÛ file? % One method is to create a file called % Ûdvipsone.cmdÛ in the Û\dvipsoneÛ directory. % This file is read by {\DVIPSONE} when it starts and scanned for additional % command line arguments. % You can enter the full command line into this file. % Just make sure to delete the file again afterwards. % % (or it will be interpreted every time you call {\DVIPSONE}. %%% remove Font Manipulation Package for the moment ? \subsect{Font Manipulation Package (Advertisement)} % % If you cannot get the results you want with {\AFMtoTFM} --- or If you have special needs not met by simply reencoding a font --- such as making new fonts by combining glyphs from two existing fonts % like a desire to typeset in a non-Latin alphabet --- then you may find it convenient to purchase {\yandy}'s Font Manipulation Package (\FMP), which contains command line % {\DOS} utilities for modifying Type~1 font files without damaging their `hinting' --- which is crucial to quality rendering. The {\FMP} includes utilities for inserting characters from one font in another, for adding new accented characters, for adjusting character side-bearings and advance widths, for applying arbitrary linear transformation to glyphs, % and more\dots and more\ellipsis % \section{Acknowledgments} % % Frederick Bartlett produced the first draft. % Jordan Backler, Clovis Tondo, Donald P. Story, Paul Anagnostopolous, % Ronald Westman, provided valuable feedback. \newpage % following is somewhat optional (was end of environment var section) % Changing environment variables using batch file: % Sometimes it is convenient to change environment variables when working on % different projects. This may be done using a batch file. % A batch file, however, cannot modify Ûdviwindo.iniÛ. % In this case, do {\it not\/} list the environment variables you want to be % able to change in the `[Environment]' section of Ûdviwindo.iniÛ, % so that corresponding {\DOS} environment variable will be used instead. % download, modex \subsub{Font substitution file} % % In most cases you % do not need to Typically you need not worry about font substitution in {\DVIPSONE}. The standard substitution file is called Ûstandard.subÛ. It simply ensures that fonts already present on your printer will not be downloaded as part of the Post\-Script file. If the fonts resident on your printer do not match the basic 13 --- namely the Times-Roman, Helvetica, Courier and Symbol families --- % (if you have more or less), then you may want to edit Ûstandard.subÛ or, better, create your own substitution file. You can tell {\DVIPSONE} to use a different substitution file using Û-s=mysub.subÛ on the command line. % By the way, any such command line arguments that you want to always have {\DVIPSONE} use can be placed in a Ûdvipsone.cmdÛ file in your ÛDVIPSONEÛ folder. % directory. % If {\DVIPSONE} is called from {\DVIWindo} then an alternative is, as indicated before, to add a ÛDVIPSONE=...Û entry to the `Û[Window]Û' section of Ûdviwindo.iniÛ. Printer-resident fonts are entered in the substitution file as follows: \beginlines Ûtir Times-Roman *force* *reside*Û \endlines \noindent The standard 13 fonts are given in Ûstandard.subÛ; if your printer includes additional fonts, you will have to add additional lines. The first element in each line is the % {\DOS} filename, less underscores and extensions; the second element is the Post\-Script FontName (note that this is {\it not\/} the `Face Name' used in Windows menus!), the last two elements Û*force* *reside*Û tell {\DVIPSONE} not to download the font, but rather to assume that it is present on the printer. % more general put this elsewhere ? % also mention can call for more than one font substitution file Note that if you claim a font is resident and turn out to be wrong, all instances of that font in your document will be ``Couriered out''; any time a Post\-Script device is asked for a font it can't find it blithely substitutes the Courier font. % (even though it is very difficult to imagine a situation in % which this would be the right thing to do). You can ask {\DVIPSONE} to check whether all the required fonts are present on the printing device by using the command line flag Û-*sÛ. If any fonts are missing, it then list the missing fonts on an error page instead of printing the job. Several other useful font substitution files may be found in the Û\subÛ subfolder % subdirectory of the Û\dvipsoneÛ folder. % directory. % If your file uses, say, Ûmsbm6Û and you only have Ûmsbm7Û and % Ûmsmb10Û, then you'll have to create substitution lines in % Ûstandard.subÛ (or whatever substitution file you're using). % In this case, the line would be, % simply % \beginlines % Ûmsbm6 msbm7Û % \endlines % \noindent or you can use Ûamsfonts.subÛ --- or add it to your Û.subÛ % file; it contains this line and many others. % flush the following ? A word of warning, though --- if you have previously modified % edited your fonts in order to get around encoding % these problems (using, for example, the Ûencode.batÛ batch file), you will have a fair amount of work to do in order to make your setup % system compatible with this new feature. Of course, you {\it can\/} continue to use the modified fonts, just remember that they will not be reencoded `on the fly' to the encoding specified by the % environment variable ÛENCODINGÛ. % If you {\it do\/} want to convert them to the `new way' of doing things, % have edited font files, replace the font files with their original versions --- making sure to change {\it both\/} the Û.pfbÛ and Û.pfmÛ files back. % (If the Û.pfbÛ and Û.pfmÛ files do not match, then {\ATM} will % probably refuse to display the font.) % maybe flush this \subsub{Font Downloading} % {\DVIPSONE} is a Post\-Script printer driver unique in several respects. For example, it is the only printer driver using `partial font downloading,' which greatly reduces the size of the file sent to the printer and also greatly reduces the amount of virtual memory used on the printer. % Because of {\DVIPSONE}'s partial font downloading, there will usually not be any need to download fonts to your printer's virtual memory. Downloading fonts is sometimes called ``permanent'' downloading because the downloaded font can then be used in more than one job. However, if the printer is reinitialized, the ``permanently'' downloaded fonts disappear. % and will have to be downloaded again. % do we want to waste a lot of space on this ? Adobe provides downloading utilities with their Type~1 fonts. ÛpcsendÛ works % well from the % {\DOS} command line; there is also a Windows program, Adobe Font Downloader. In addition, ÛdownloadÛ is provided with {\DVIPSONE}. No matter which you use, however, {\it you\/} must manually edit your font substitution file to ensure that your printer and {\DVIPSONE} agree on which fonts are downloaded. It is extremely easy to get them out of sync --- and you won't find out they're out of sync until you start seeing Courier all over your print job. % FLUSH THIS ??? \subsub{Upgrade Blues} % If you previously used \yandy's utilities to reencode your Û.pfbÛ, Û.pfmÛ files % (and thus your Û.pfmÛ and Û.tfmÛ files), and Û.tfmÛ files, then you will have to either undo the reencoding or (which is likely to be {\it much\/} easier) reinstall the fonts from the original diskettes. Remember that only the Û.afmÛ file has {\it all\/} the metric information. % If you no longer have the original Û.afmÛ file, you will shortly learn % why you were advised to keep a backup copy. % % (However, Adobe says that ``in a few weeks'' [as of June 1995] Û.afmÛ % files will be available on their ftp site: % Ûftp.adobe.com/pub/adobe/FontsÛ.) If you do not have the {\AFM} file, you can recreate it % to recreate an Û.afmÛ file, you can using {\TFMtoAFM} or {\PFMtoAFM} % ÛtfmtoafmÛ or ÛpfmtoafmÛ (which give different character bounding box sizes, no composite-character information, and no unencoded character information, but do give the kerning information). If you have the `Font Manipulation Package' (see later) %% section? you can also use {\PFAtoAFM} (which gives % reasonably accurate character bounding box sizes, composite-character information, and unencoded character information, though no kerning information). In this case you can replace the `CharMetrics' section of an Û.afmÛ file made using {\TFMtoAFM} or {\PFMtoAFM} with the more accurate one made using {\PFAtoAFM}. % Combine the resulting files into a single Û.afmÛ % file, reencode it to StandardEncoding, and In any case create new Û.pfmÛ and Û.tfmÛ files using {\AFMtoPFM} and {\AFMtoTFM}. Note that The Û.pfmÛ file should be created with Û-c=ansinewÛ; the Û.tfmÛ file should be created with an encoding vector of your choice (for example `texnansi'). {\bf Important}: Do not simply copy over your old Û.pfbÛ and Û.pfmÛ file with the new one. First, remove the old font using Adobe Type Manager's {\ATM} Control Panel. Place the newly restored Û.pfbÛ and Û.pfmÛ files in some temporary folder % directory and install the font from there using {\ATM}. % Then copy the new Û.pfmÛ into your ÛpfmÛ folder % directory % and add the font through the {\ATM} Control Panel. % In some cases you will need in addition to exit Windows, delete the file Ûatmfonts.qlcÛ in your ÛpsfontsÛ folder, % directory, and relaunch Windows to have {\ATM} reconstruct its `Quick Load Cache.' {\bf Important}: {\TeX} format files contain `frozen' {\TFM} files. If a format contains a {\TFM} file for a font, {\TeX} will never notice that you may have changed it on the disk. This can lead to mysterious problems, for which recreation of the format file is the solution. You can check which {\TFM} files {\TeX} is reading by using the command line flag Û-ZÛ with \yandytex. The log file then will show all {\TFM} files read. % following was in `Problems' section % following seems highly optional... Another easy way to get \TeX\ confused is to port someone else's files to your system and attempt to duplicate the original file and folder % directory structure and environment on your machine. If you have set up ÛTEXAUXÛ to point to a single folder % directory and the original setup assumes that Û.auxÛ files will be distributed throughout a tree of folders, % directory tree, you have the makings of a nice snafu. The solution to such a case is to turn off ÛTEXAUXÛ (that is, simply delete it from % --- or comment it out in Ûdviwindo.iniÛ). % following seems somewhat optional (like SysSeg) \subsect{Cleanup} % {\CLEANUP} allows you to conveniently close all {\DOS} windows you have kept open (so that, for instance, you can see the results of a \TeX\ run). To keep {\DOS} windows open, simply {\it uncheck\/} the box `Close Window on Exit' in the {\PIF} Editor. % except F1 is used for Help, C-F1 for Preview and F10 = Alt ??? %%%%%%%%%%%% Acknowledgements %%%%%%%%%%%% sure to discuss all questions that installation program may ask %%%%%%%%%%%% compare with present stack of hand-outs - eliminate of possible %%%%%%%%%%%% compare list of env vars with envvars.txt - eliminate of possible %%%%%%%%%%%% discuss more on DOS / memory issues ? (dos.txt) %%%%%%%%%%%% LaTeX 2e package contents? %%%%%%%%%%%% Tech support info ??? tech-help@YandY.com %%%%%%%%%%%% more on help file? %%%%%%%%%%%% more on color ??? %%%%%%%%%%%% describe text search in DVI files ??? %%%%%%%%%%%% discuss encoding vector/texnansi in one place %%%%%%%%%%%% explain where utilities may be found %%%%%%%%%%%% asking DVIPSONE to print landscape, to check fonts, etc % avoid font substitution file discussion % avoid dviwindo.fnt discussion %%%%%% discuss character layout / font encoding in ONE place? %%%%%% \ => / ??? %%%%%% trademarks mark %%%%%% DVIWindo `readme.txt' gives complete list of what can appear %%%%%% in [Window] section of dviwindo.ini ??? %%%%%% `texmenu.txt' described what can be in the [Applications] section ??? %%%%%% DVIPSONE `readme.txt' gives complete list of command line options ??? %%%%%% add an Advanced topics section: page imposition, color separation, PDF %%%%%% using the fonts \input mtplain, \input mtlatex %%%%%% using the fonts in LaTeX 2e %%%%%% ^Z emergency stop in TeX, x in response to errror %%%%%% discuss multiple masters %%%%%% list of what text files to consult? %%%%%% eliminate repetition ? %%%%%% show texnansi encoding --- use gxrg ? explain more details? %%%%%% consistency of notation Û typewriter mode versus \sc versus ... %%%%%% consistency in .) versus ). at end of parenthetical comment ... %%%%%% share.exe ? vshare.exe %%%%%% dvipsone -v -d=lpt1 -m=1.25 -x=72 -y=72 manual.dvi OLD %% for QMS printer use -vzg, for HP LJ IV use -vzgr in following: %%%%%%% twoup -vzgr -d=lpt1 -M=1 -y=-80 -x=-90 -x=70 manual %%%%%%% twoup -vzh -d=lpt1 -M=1 -y=-80 -x=-90 -x=70 manual %% as of 1996 March, use %% for QMS printer use -vzg, for HP LJ IV use -vzgr in following: %%%%%%% twoup -vzgr -d=lpt1 -M=1 -y=-80 -x=-81 -x=81 manual21 %%%%%%% twoup -vzh -d=lpt1 -M=1 -y=-80 -x=-81 -x=81 manual21 % italic instead of \ang{...} (or in addition) for metalinguistic variables... % increase leading by 1.2pt to 1pt % explain modeless dialog box %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% PFE => WinEdt %% people who upgrade without WinEdt... %% changes in menus %% changes in ATM 3.02 => 4.0 avoid reference to explicit version number %% NT without ATM flush %% diskette to CD !!! %% Windows 2000 (ATM) %% conversion to TrueType flush %% flush setupttf discussion or move it ? %% European Modern ??? %% adding BMP to TIFF etc. %% environment variables from menu %% check directory => folder %% some items moved from Fonts menu to Special %% some items moved from File menu to Edit %% no mention of `edit menu' ? %% provision for ... prefix in TeX menu %% distinction between ATM rasterizer and ATM font manager % How to set up Windows to show file extensions?