TeXhax Digest Sunday, February 3, 1991 Volume 91 : Issue 005 Moderators: Tiina Modisett and Pierre MacKay %%% The TeXhax digest is brought to you as a service of the TeX Users Group %%% %%% in cooperation with the UnixTeX distribution service at the %%% %%% University of Washington %%% Today's Topics: Fig 2.1.1 patchlevel 1 AmsTeX 2.0 Fonts with LaTeX Imake-less ImakeTeX 2.00 and SchemeWEB TeX on a DECStation 5000 Anyone? ftping TeX for MS-DOS TeXhax Digest V91 #002 latex question Address of G. W. Stewart Increasing memory for METAFONT (SBMF under DOS) Naming of Non-CM Fonts -------------------------------------------------------------------------- Date: Mon, 28 Jan 91 12:15:31 -0500 From: beck@cs.cornell.edu (Micah Beck) Subject: Fig 2.1.1 patchlevel 1 Keywords: Fig 2.1.1, SunView Enclosed is patchlevel 1 of the Fig 2.1.1 SunView graphics editor. It fixes a bug in the mapping between PostScript text fonts and the numbers used to represent them in the Fig output file. The bug exhibited itself by a mismatch between the font specified to Fig and the font used by TransFig in PS output. This happened only for text objects with the PS-Font flag set. Any text objects created using Fig 2.1.1 patchlevel 0 with PS-Font set will need their font changed using patchlevel 1 in order to fix the problem. Micah Beck Cornell CS Dept. ---------------- *** patchlevel.h.sav Mon Jan 28 11:56:35 1991 --- patchlevel.h Mon Jan 28 11:56:46 1991 *************** *** 1 **** ! #define PATCHLEVEL 0 --- 1 ---- ! #define PATCHLEVEL 1 *** change.c.sav Sun Dec 23 14:38:41 1990 --- change.c Thu Jan 10 14:54:55 1991 *************** *** 345,351 **** PANEL_LABEL_STRING, "Font:", ATTR_LIST, psfont_text(new_text) ? psfont_names: font_names, ! PANEL_VALUE, new_text->font, 0); rigid_panel = panel_create_item(change_panel, PANEL_CYCLE, PANEL_LABEL_X, ATTR_COL(2), --- 345,351 ---- PANEL_LABEL_STRING, "Font:", ATTR_LIST, psfont_text(new_text) ? psfont_names: font_names, ! PANEL_VALUE, new_text->font+1, 0); rigid_panel = panel_create_item(change_panel, PANEL_CYCLE, PANEL_LABEL_X, ATTR_COL(2), *************** *** 430,436 **** struct pr_size size; new_text->type = (int)panel_get_value(subtype_panel); ! new_text->font = (int)panel_get_value(font_panel); new_text->size = atoi(panel_get_value(font_size_panel)); new_text->flags = (panel_get_value(rigid_panel) ? RIGID_TEXT : 0) --- 430,436 ---- struct pr_size size; new_text->type = (int)panel_get_value(subtype_panel); ! new_text->font = (int)panel_get_value(font_panel)-1; new_text->size = atoi(panel_get_value(font_size_panel)); new_text->flags = (panel_get_value(rigid_panel) ? RIGID_TEXT : 0) *************** *** 1016,1021 **** --- 1016,1022 ---- { font_names = attr_create_list( PANEL_CHOICE_STRINGS, "Default", + "Default", "Roman", "Bold", "Italic", *************** *** 1545,1551 **** get_new_default_values() { cur_texttype = (int)panel_get_value(subtype_panel); ! cur_textfont = (int)panel_get_value(font_panel); cur_textsize = atoi(panel_get_value(font_size_panel)); cur_textangle = M_PI/180*atoi(panel_get_value(angle_panel)); cur_dotgap = (int)panel_get_value(dotgap_panel)/10.0; --- 1546,1552 ---- get_new_default_values() { cur_texttype = (int)panel_get_value(subtype_panel); ! cur_textfont = (int)panel_get_value(font_panel)+1; cur_textsize = atoi(panel_get_value(font_size_panel)); cur_textangle = M_PI/180*atoi(panel_get_value(angle_panel)); cur_dotgap = (int)panel_get_value(dotgap_panel)/10.0; *************** *** 1689,1695 **** if (compound_item_selected(C_SUBTYPE)) t->type = (int)panel_get_value(subtype_panel); if (compound_item_selected(C_FONT)) t->font = ! (int)panel_get_value(font_panel); if (compound_item_selected(C_FONT_SIZE)) t->size = atoi(panel_get_value(font_size_panel)); if (compound_item_selected(C_ANGLE)) t->angle = --- 1690,1696 ---- if (compound_item_selected(C_SUBTYPE)) t->type = (int)panel_get_value(subtype_panel); if (compound_item_selected(C_FONT)) t->font = ! (int)panel_get_value(font_panel)-1; if (compound_item_selected(C_FONT_SIZE)) t->size = atoi(panel_get_value(font_size_panel)); if (compound_item_selected(C_ANGLE)) t->angle = ----------------------------------------------------------------------------- Date: Mon, 28 Jan 91 09:42:51 EST From: Tom Prusa Subject: AmsTeX 2.0 Fonts with LaTeX Keywords: AmSTeX, LaTeX Hello, This has probably been posted but I do not remember seeing it... but does anyone have (or can anyone point me to) a amssymbol.sty that allows the use of AmSTeX 2.0 fonts with LaTeX. I appreciate the time. thanks, tom prusa ----------------------------------------------------------------------------- Date: Mon, 28 Jan 91 08:55:39 EST From: ramsdell@linus.mitre.org Subject: Imake-less ImakeTeX 2.00 and SchemeWEB Keywords: ImakeTeX, SchemeWEB ImakeTeX automates much of the installation of UnixTeX. An alpha version of ImakeTeX (2.00) has been released. The aim of the new version is to eliminate the use of features that are not available in the important Unix implementations. The approach used has been to eliminate any feature that does not appear in Draft 10 of POSIX 1.002. Changes to ImakeTeX include: [1] updating the web2c version so that compiles TeX 3.1 and MF 2.7, [2] replacing MIT's imake program by a simple AWK program, and [3] support for installing AMSTeX 2.0 software. ImakeTeX is available via anonymous FTP from june.cs.washington.edu in the file tex/imaketex200.tar.Z. Know bugs: the makefiles use the double colon target feature which is not supported on some systems. The next release will eliminate its use. I have no access to a System V machine, so please check it. Send bug reports to ramsdell@mitre.org. ******************************* SchemeWEB SchemeWEB provides simple support for literate programming in any dialect of Lisp. Originally created for use with Scheme, it defines a new source file format which may be used to produce LaTeX input or Lisp code. The version of July 1990 is available from the Clarkson archives in the tex-programs directory. John ---------------------------------------------------------------------------- Date: Mon, 28 Jan 91 09:52:59 +0100 From: Harald Hanche-Olsen Subject: TeX on a DECStation 5000 Anyone? Keywords: TeX, DECStation 5000 I have no experience with the DECStation 5000, but the first question that comes to the mind is, have you tried compiling with optimizing turned off? Many optimizers create wrong code from the TeX source, including the one on Apollos. - Harald Hanche-Olsen Division of Mathematical Sciences The Norwegian Institute of Technology N-7034 Trondheim, NORWAY ------------------------------------------------------------------------- Date: Mon, 28 Jan 91 02:12:38 EST From: Jon Radel Subject: ftping TeX for MS-DOS Keywords: TeX, ftp, MS-DOS A cautionary note on using terminator.cc.umich.edu as a source for TeX for MS-DOS. As of 27Jan91, the copy of emTeX there is not current. The fonts for emTeX are in the old library format, which, I believe, will cause you problems if you try use them with T.R.'s dvips. As of now, the current version of emTeX is from 25Sep90. Actually, sb30tex isn't the latest either. Get sb34tex from venus.ycc.yale.edu or other source instead. --Jon Radel jonradel@phoenix.princeton.edu ------------------------------------------------------------------------- Date: Mon, 21 Jan 91 14:58:24 EST From: petsche@learning.siemens.com (Thomas Petsche) Subject: TeXhax Digest V91 #002 Keywords: TeX, hyphenation Is there a difference in the hyphenation rules for TeX 3.0? For our TeX, C Version 2.98 (no format preloaded) *\showhyphens{state} Underfull \hbox (badness 10000) detected at line 0 [] \tenrm state For our TeX, C Version 3.0 *\showhyphens{state} Underfull \hbox (badness 10000) detected at line 0 [] \tenrm s-tate (Or try stand, stood, or stuck) (BTW, hyphen.tex for version 2.98 is exactly the same as hyphen.tex for 3.0) What going on? Thomas Petsche petsche@leaning.siemens.com ------------------------------------------------------------------------ Date: Sun, 20 Jan 91 22:59:07 EST From: steiner@bakerst.rutgers.edu Subject: latex question Keywords: LaTeX, \count1 I want to get the section no. into \count1 so dviselect can use it. I've used the following code: % We need to get the section number for dviselect. So we copy the % section number from \c@section (count79) to count1. We need to do % this after the section command but we need to do it this way since the % old \section is written funny. \makeatletter \let\oldsection=\section \count1=\c@section %initialize \def\section{\expandafter\count1\expandafter\c@section\oldsection} \makeatother This pretty much works except for the page where the section starts. Any ideas why? ds Dave Steiner arpa: Steiner@BakerSt.Rutgers.Edu or Steiner@Rutgers.Edu uucp: ...{backbone site}!rutgers!bakerst.rutgers.edu!steiner ----------------------------------------------------------------------------- Date: Sun, 20 Jan 91 20:04:47 MEZ From: Erich Neuwirth Subject: Address of G. W. Stewart Keywords: G.W.Stewart Can anybody help me to contact G. W. Stewart. He is the author of jeep.sty and his address was, stewart@thales.und.edu but this machines seems no longer to be known on internet. ERICH NEUWIRTH BITNET (EARN): A4422DAB@AWIUNI11 INTERNET: a4422dab@Helios.EDVZ.UniVie.AC.AT Institute for Statistics and Computer Science UNIVERSITY OF VIENNA, UNIVERSITAETSSTR. 5/9, A-1010 VIENNA, AUSTRIA ------------------------------------------------------------------------------ Date: 18 Jan 91 17:42:51 GMT From: katehaki@andromeda.rutgers.edu (Michael N Katehakis) Subject: Increasing memory for METAFONT (SBMF under DOS) Keywords: METAFONT, memory I need to icrease the METAFONT (SBMF) memory for MSDOS enviroment. I am not not a METAFONT expert (just a novice), and don't have a clear idea of what parameters should I change. I would appreciate hearing from people who have had similar experiences. Please send me mail to: katehaki@andromeda.rutgers.edu Thank you ! -------------------------------------------------------------------------- Date: Wed, 16 Jan 91 05:39:54 EST From: "Teresa A. Ehling" Subject: Naming of Non-CM Fonts Keywords: fonts, non-CM fonts A RECOMMENDATION FOR THE NAMING of NON-CM FONTS USED IN TeX Now that increasing use is being made of non-CM fonts in TeX, it is important that standards be developed for the names used to refer to such fonts in TeX input. Without such a standard, TeX cannot locate the appropriate font metric information, and DVI processing programs connot locate the required font outlines or bitmaps, or use the correct font name to invoke the correct printer-resident fonts. This lack of codification has proved to be a major source of frustration when DVI files are ported from one computer system to another, as is common when publishing journal articles and books from author-supplied material. As it stands now, each project to be run out requires customization, compelling the typesetter to set up yet another new font name translation table that maps names used in TeX to file names. And this usually requires consulting with the author to determine just what the font names in the manuscript mean. Perhaps more seriously, without a uniform naming convention, it may happen that the DVI processing program and TeX have conflicting notions about what fonts are being referred to-- with disasterous consequences. Without a naming convention then, DVI files are not truly "device independent" since they are tied to the naming convention used on a particular computer system. As a basis for our proposal, we quote from the "The TeXbook" (p.278): "The syntax for in \font is not standard in TeX because different operating systems have different conventions. You should ask your local system wizards for details on just how they have decided to implement filenames. However, the following principles should hold universally: A should consist of followed by explicit character tokens (after expansion). A sequence of six or fewer ordinary letters and/or digits followed by a space should be a file name that works in essentially the same way on all installations of TeX...." Consequently: * We recommend that where a standard naming convention for a font library already exists that fits into the scheme advocated in "The TeXbook", then that convention should be adopted for use with TeX and DVI converters. Presently, many of the non-CM fonts called for by users of TeX are PostScript outline fonts, either printer resident or in downloadable form. Adobe Systems was already inspired to invent a naming convention for the fonts in their library for use on computers that cannot handle long file names. In their library, file names are assigned to fonts by (manually) contracting the font family name and appending standard modifiers for bold (b), italic (i), bold-italic (bi), light (l), oblique (o), narrow (n), condensed (c), and so on. Thus information about the font with PostScript FontName 'Times-BoldItalic', for example, is stored in files with the name 'tibi'. An extension of the file name indicates what type of information is in the file. Commonly used extensions are .afm (for Adobe font metric information), .tfm (for TeX font metric information), .pfm (for MicroSoft Windows printer font metric information), .pfb (for printer font binary), and .pfa (for printer font ASCII). Adobe's Fontdownloader limits the file name to six characters, which conforms exactly to the recommendation in "The TeXbook". It seems logical then that: * When using Adobe PostScript outline fonts in TeX, one should simply follow this naming convention. (There is presently no conflict with CM font names since none of the fonts in the Adobe font library have names starting with the letters 'cm'.) One possible complication arises from the practice of remapping character codes in non-CM fonts to lie in positions that are used by TeX in some CM font. One should be able to distinguish between a font that is used verbatim and one that has been remapped: * We recommend that the suffix 'm' be appended to a fontname when a remapped version is intended. This is not completely unambiguous since the font can be remapped in different ways, but it will usually be obvious what is intended. Thus a regular font would normally be remapped to the ordinary text (roman) encoding of TeX (as for cmr10), an italic font would be remapped to TeX's italic encoding (as for cmti10), while a symbol font would be remapped to TeX's symbol encoding (as in cmsy10). * We recommend that the 'm' be used as a suffix, NOT as a prefix so that related fonts continue to appear together in a sorted list. (Adding the suffix to a name with six characters brings it to seven, but even the most limiting file systems these days allow up to eight characters.) It should be noted that the issue of remapping is now becoming less important as users are switching to TeX 3.0, which supports fonts with 256 character codes. But it seems likely that continued used will be made of remapping for specialized purposes. * We also recommend that no prefix (e.g. 'ps') be attached to fontnames since this wastes two precious characters out of the six (or perhaps eight) that are available on some systems. We welcome your comments on this proposal and look foward to the utilization of a viable font naming standard in the near future. We welcome your comments on this proposal and look foward to the utilization of a viable font naming standard in the near future. Berthold K.P. Horn Artificial Intelligence Lab MIT bkph@ai.mit.edu Teresa A. Ehling The MIT Press Cambridge, Mass. ehling@mitvma.mit.edu ADDENDUM: Names of Some Commonly used Adobe Outline Fonts --------------------------------------------------------- ag AvantGarde-Book ago AvantGarde-BookOblique agd AvantGarde-Demi agdo AvantGarde-DemiOblique bkl Bookman-Light bkli Bookman-LightItalic bkd Bookman-Demi bkdi Bookman-DemiItalic cll Clarendon-Light cl Clarendon clb Clarendon-Bold com Courier coo Courier-Oblique cobo Courier-BoldOblique cob Courier-Bold hv Helvetica hvo Helvetica-Oblique hvb Helvetica-Bold hvbo Helvetica-BoldOblique hvc Helvetica-Condensed hvco Helvetica-Condensed-Oblique hvcb Helvetica-Condensed-Bold hvcbo Helvetica-Condensed-BoldObl lmi LucidaMath-Italic lms LucidaMath-Symbol lme LucidaMath-Extension nbr NewBaskerville-Roman nbi NewBaskerville-Italic nbb NewBaskerville-Bold nbbi NewBaskerville-BoldItalic ncr NewCenturySchlbk-Roman nci NewCenturySchlbk-Italic ncb NewCenturySchlbk-Bold ncbi NewCenturySchlbk-BoldItalic new NeuzeitS-Book newh NeuzeitS-BookHeavy por Palatino-Roman poi Palatino-Italic pob Palatino-Bold pobi Palatino-BoldItalic sy Symbol tir Times-Roman tii Times-Italic tib Times-Bold tibi Times-BoldItalic zcmi ZapfChancery-MediumItalic zd ZapfDingbats ----------------------------------------------------------------------- %%% Further information about the TeXhax Digest, the TeX %%% Users Group, and the latest software versions is available %%% in every tenth issue of the TeXhax Digest. %%% %%% Concerning subscriptions, address changes, unsubscribing: %%% %%% BITNET: send a one-line mail message to LISTSERV@xxx %%% SUBSCRIBE TEX-L % to subscribe %%% or UNSUBSCRIBE TEX-L %%% %%% Internet: send a similar one line mail message to %%% TeXhax-request@cs.washington.edu %%% JANET users may choose to use %%% texhax-request@uk.ac.nsf %%% All submissions to: TeXhax@cs.washington.edu %%% %%% Back issues available for FTPing as: %%% machine: directory: filename: %%% JUNE.CS.WASHINGTON.EDU TeXhax/TeXhaxyy.nnn %%% yy = last two digits of current year %%% nnn = issue number %%% %%%\bye %%% End of TeXhax Digest ************************** -------