From cczdao@mips.ccc.nottingham.ac.uk Mon Jul 5 07:56:04 1993 Flags: 000000000001 Return-Path: Received: from jess.ccc.nottingham.ac.uk by math.utah.edu (4.1/SMI-4.1-utah-csc-server) id AA25718; Mon, 5 Jul 93 07:55:54 MDT Errors-To: TeXhax-Request@tex.ac.uk Received: from ccsun5.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <02114-0@jess.ccc.nottingham.ac.uk>; Fri, 2 Jul 1993 14:30:00 +0100 From: TeXhax-Request@tex.ac.uk To: TeXhax Distribution:;@jess.ccc.nottingham.ac.uk Subject: TeXhax Digest V93 #011 Reply-To: TeXhax@tex.ac.uk Errors-To: TeXhax-Request@tex.ac.uk Distribution: world Date: Fri, 02 Jul 1993 14:31:05 +0100 Message-Id: <696.741619865@mips.ccc.nottingham.ac.uk> Sender: cczdao@mips.ccc.nottingham.ac.uk TeXhax Digest Friday, 2 Jul 1993 Volume 93 : Issue 011 % The TeXhax Digest is brought to you as a service of the TeX Users Group % % and UK TeX Users Group in cooperation with the UK TeX Archive group % Today's Topics: METAFONT memory usage - position dependency New ftp procedures for VM/CMS TeX Why \markboth{}{} used in standard LaTeX report style? QED command BIBTeX psnfss smallcaps problem Free tex and latex LaTeX3 public documents available Administrivia: Moderators: David Osborne and Peter Abbott Contributions: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: TeXhax-request@tex.ac.uk ---------------------------------------------------------------------- Date: Wed, 16 Jun 1993 13:19:11 -0700 From: "Rex H. Shudde" <0024P@NAVPGS.EARN> Subject: METAFONT memory usage - position dependency Recently I ran into a curious Metafont situation. I had created a series of 36 characters (all 40 pt in height) using the emTeX version of Metafont (Version 2.0 [3a]). I then changed the size to 60 pt to create a larger set, but got the dreaded, "METAFONT capacity exceeded, sorry [main memory size=65531]," error message while the 29th character was being generated. The program is set up so that each symbol is in a separate file which starts with a statement and ends with an statement. A driver program sets up initial housekeeping and then inputs each of the symbol files in turn. What I did next was add a statement between each of the input statements, go back to the 40 pt size, and rerun the program to generate the log file to see which of the characters was chewing up memory and then try to clean those particular files. I did what I thought was a pretty good cleanup job, and then regenerated the characters again. To my dismay, the new log file was identical to the old file---all of my cleanup had done nothing! The next thing I thought of was to generate the offending characters before any of the other characters with the hope that I might find something that they had in common (or lacked in common). After rerunning, I discovered from the log file that I had gained a little memory. That is, after the 36th symbol was generated I had a little bit more memory "untouched" than in the previous run. I repeated this process several times, moving the input of files that seemed to cause increased memory usage up to the top. Curiously enough, some of the files that previously caused increased memory usage no longer did. After about five such iterations it appeared that I had gained enough memory to be able to generate the characters at 60 pt, and it turned out that this was true. All 36 characters were created at 60 pt without a hitch. Sorry that this has been so long winded, but my primary question is, "why is total memory requirement of Metafont dependent upon the order in which the characters are generated?" Also, why isn't the memory between the and reallocated to the memory pool since, presumably, once you've generated a character you're through with that section of code? (Or maybe there is a way to return the memory to the unused memory pool that I'm not aware of.) Finally, is there some better parameter to dump to the log file (incidently, the "string usage" readout that comes with was identical on all runs) than ? Any and all comments will be much appreciated. R. H. Shudde Bitnet: 0024p@navpgs Internet: 0024p@vm1.cc.nps.navy.mil ------------------------------ Date: Wed, 16 Jun 1993 17:13:39 -0700 From: Dean Guenther Subject: New ftp procedures for VM/CMS TeX There are now new procedures to ftp VM/CMS TeX and utilities. You now log into the anonymous account as follows: FTP wsuvm1.csc.wsu.edu logon anonymous cd tex.191 Dean Guenther Internet: guenther@tigger.csc.wsu.edu Washington State University Bitnet: guenther@cougar Pullman, WA. 99164-1220 AT&T: 509 335-0433 fax: 509 335-0540 ------------------------------ Date: Sun, 20 Jun 1993 20:07:27 -0700 From: "Ethan V. Munson" Subject: Why \markboth{}{} used in standard LaTeX report style? I'm the current maintainer of the ucthesis style (for University of California dissertations), which is based closely on the standard LaTeX report style. I asked this question of the comp.text.tex USENET newsgroup but got no reply. So, I'm now trying TeXhax. One user of the ucthesis style wanted to put the text "Draft" on every page and tried to use the \markboth command to do so. It didn't work because the definition for \part invokes \markboth{}{} which overrode the user's \markboth. Is there an important reason why the report style does this? It seems to me that the user is trying to do something very reasonable and I don't see why it shouldn't be possible. So, I'm sorely tempted to remove the \markboth from the definition of \part in the ucthesis style. Thanks for your help, Ethan Munson munson@cs.berkeley.edu ------------------------------ Date: Wed, 23 Jun 1993 09:36:44 -0000 From: Martin Ward Subject: QED command I recently decided I wanted a marker to denote the end of a proof. Digging around in my style file archive I came up with a macro by Paul Vojta (vojta@guinness.ias.edu) (vintage May 1990), based on p. 106 of the TeXbook. I have modified this to work in three different situations in LaTeX: (1) At the end of a text paragraph (2) Inside the LaTeX displayed equation brackets \[...\] (3) After the last equation in a LaTeX eqnarray (just before the \end{eqnarray} command). Below is an example file illustrating the three cases. Comments, criticism, bugs, fixes etc. are welcome. Martin. JANET: Martin.Ward@uk.ac.durham Internet (eg US): Martin.Ward@durham.ac.uk or if that fails: Martin.Ward%uk.ac.durham@nsfnet-relay.ac.uk or even: Martin.Ward%DURHAM.AC.UK@CUNYVM.CUNY.EDU BITNET: Martin.Ward%durham.ac.uk@UKACRL UUCP:...!uknet!durham!Martin.Ward %%%%%%%%%%%%%%%%%%%% CUT HERE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% qed.sty: a LaTeX style for putting a symbol to mark the end of a proof. %% Copyright 1993 Martin Ward %% Email: Martin.Ward@durham.ac.uk %% or: Martin.Ward%DURHAM.AC.UK@CUNYVM.CUNY.EDU %% %% This program is free software; you can redistribute it and/or modify %% it under the terms of the GNU General Public License as published by %% the Free Software Foundation; either version 2 of the License, or %% (at your option) any later version. %% %% This style file defines a command \qed which displays a "QED symbol" %% (by default, a black rectangle) at the right margin. %% It is designed to be placed at the end of a mathematical proof. %% It works in three different situations: %% (1) At the end of a text paragraph %% (2) Inside the LaTeX displayed equation brackets \[...\] %% (3) After the last equation in a LaTeX eqnarray (just before the %% \end{eqnarray} command). %% %% In cases (1) and (3), no extra vertical space should appear. %% In case (2) the vertical space after the equation is removed and %% a new paragraph started (does anyone have a fix for this?) %% Note: it doesn't work inside \begin{equation}...\end{equation}. %% %% If \[ \matrix ... \endmatrix \qed \] doesn't work, then try %% \[ \qed \matrix ... \endmatrix \] The latter approach will always work, %% although it is more wasteful of processing time. %% \def\qedsymbol{\vrule width.6em height.5em depth.1em\relax} \def\qed{\ifx\\\@eqncr\let\next\eqnarrayqed\else \ifmmode\let\next\eqnqed\else \let\next\textqed\fi\fi\next} \def\eqnqed#1\]{\belowdisplayskip\z@\belowdisplayshortskip\z@ \postdisplaypenalty\@M\relax#1 \]\par{\lineskip\z@\baselineskip\z@\vbox to\z@{\vss\noindent\textqed}}} \def\textqed{{\unskip\nobreak\hfil\penalty50\hskip2em\null\nobreak\hfil \qedsymbol\parfillskip\z@\finalhyphendemerits0\par}} \def\eqnarrayqed{\\\noalign{\vspace{-\jot}% {\lineskip\z@\baselineskip\z@% \vbox to\z@{\vss\noindent\textqed}}% \vspace{-\baselineskip}}} \endinput %%%%%%%%%%%%%%%%%%%% CUT HERE TOO %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \documentstyle[qed]{article} \begin{document} Some well-known facts: \begin{eqnarray*} 1+1 &=& 2 \\ 2+2 &=& 4 \qed \end{eqnarray*} This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is an equation: \[ 1+1=2\qed \] This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. \qed This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. This is a paragraph of text. \end{document} ------------------------------ Date: Wed, 23 Jun 1993 12:36:08 +0200 From: sven@ling.gu.se (Sven Stroemqvist) Subject: BIBTeX Hi, is there a BIBTeX macro for the kind of style sheet Lawrence Erlbaum Publ. requires? Would anybody know? regards, Sven Stromqvist Dept of linguistics Univ of Goteborg, Sweden sven@ling.gu.se ------------------------------ Date: Wed, 23 Jun 1993 14:54:35 -0700 From: pss@maxwell.esd.ray.com (Peter Simon x3726) Subject: psnfss smallcaps problem Greetings, TeXnicians! I recently obtained the psnfss macros from ftp.shsu.edu and am experiencing a problem with Small Caps versions of the Postscript fonts: After running psnfss.tex through LaTeX, I submitted the resulting psnfss.dvi file to dvips, which complained that font pplrc was missing. I checked, and both pplrc.tfm and pplrc.vf were included in the distribution and correctly installed. It seems that the problem is that there is no entry for pplrc in the psfonts.map file which is consulted by dvips for mapping short TeX names to actual Postscript names. Looking further, I found that there were {\em no} entries describing any Small Caps versions of fonts. A bit more investigation revealed to me that this is probably because distinct Small Caps versions of fonts do not exist--- they are created from other typefaces by performing Postscript tricks with scaling. I don't know how to perform such a trick. Could someone please tell me how, or better yet, send me the entries from your psfonts.map file which describe the Small Caps fonts, along with any Postscript code which they invoke? (I presume the latter is to be placed in the file texps.pro?) Thanks, Peter S. Simon Raytheon ESD, Dept 9282 6380 Hollister Ave. Goleta, CA 93117, USA pss@coulomb.esd.ray.com ------------------------------ Date: Wed, 30 Jun 1993 20:09:13 +0000 From: mfchen@eagle.fsl.noaa.gov (MFChen) Subject: Free tex and latex Where I can get free and easy-to-installed tex and latex? - -Nick ------------------------------ Date: Wed, 16 Jun 1993 18:21:52 -0600 From: "George D. Greenwade" Subject: LaTeX3 public documents available ***Documents related to the LaTeX3 project*** This collection of documents will contain papers from the core project team and from other volunteers. Some will be progress reports, others will be outlines of work which needs to be done and, as the project develops, there will be definitive papers describing aspects of the new system. All these documents are being made public to encourage you to find out more about the project and to foster constructive comments and further ideas. One of the files, LTX3PUB.BIB, contains a BibTeX-style list of all the public LaTeX3 documents in the collection. Each file also has a header containing bibliographic information. In addition to these documents, the collection will also contain style files: some of these are needed only for particular documents as they enable the author to describe a particular subject; but some will be main styles and style options for whole classes of documents in the collection. At present there is just one of these: L3MS001.STY (MS = main style). This is the main style of all the documents currently in the collection. It is an adaptation of the standard ARTICLE.STY; it produces a cover sheet and running heads/foots using information extracted from the file header. At present, in addition to l3ms001.sty, the following files are available: ==================================================================== filename = "l3d001.tex", archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]", author = "Frank Mittelbach and Chris Rowley", doc-group = "Project core team", title = "The {\LaTeX3} Project", version = "1.02", date = "02 April 1993", time = "22:47:45 GMT", status = "public, official", abstract = "This is a brief sketch of the \LaTeX3 Project: background, history, principles, aims and functionality. The new version of \LaTeX{} is, like the current version, a freely available system for automated processing of structured documents, formatting them to the highest typographic standards by use of the \TeX{} typesetting software. Although its uses include a very large range of published documents, the importance of its unsurpassed ability to format mathematical formulas will not be forgotten in producing the new version. It is being produced by an international group of volunteers under the technical direction of Frank Mittelbach.", note = "submitted to the Euromath bulletin", ==================================================================== filename = "l3d003.tex", archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]", author = "Frank Mittelbach and Chris Rowley", doc-group = "Project core team", title = "{\LaTeX3} Projektwoche in Mainz", version = "1.02", date = "02 April 1993", time = "22:47:23 GMT", status = "public, official", ==================================================================== filename = "l3d004.txt", archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]", author = "Frank Mittelbach and Chris Rowley", doc-group = "Project core team", title = "The {\LaTeX3} Project; Report 1991--92", version = "1.00", date = "01 April 1993", time = "13:37:20 GMT", status = "public, official", abstract = "This report describes the current activities of the \LaTeX3 project. After a short project overview, the major events of 1991 and 1992 are described. Finally the project plan for 1993 is presented. ", project-address = "LaTeX3 Project \\ c/o Dr. Chris Rowley \\ The Open University \\ Parsifal College \\ Finchley Road \\ London NW3 7BG, England, UK", project-tel = "+44 71 794 0575", project-FAX = "+44 71 433 6196", project-email = "LTX3-Mgr@SHSU.edu", copyright = "Copyright (C) 1993 LaTeX3 Project and Frank Mittelbach and Chris Rowley. All rights reserved. Permission is granted to make and distribute verbatim copies of this publication or of coherent parts from this publication provided this copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute translations of this publication or of individual items from this publication into another language provided that the translation is approved by the original copyright holders. No other permissions to copy or distribute this publication in any form are granted and in particular no permission to copy parts of it in such a way as to materially change its meaning.", generalinfo = "To subscribe to the LaTeX3 discussion list: Send mail to listserv@vm.urz.uni-heidelberg.de with the following line as the body of the message (substituting your own name): subscribe LaTeX-L First-name Surname to find out about volunteer work, look at the document in the file VOL-TASK.TEX, which can be obtained electronically." ==================================================================== filename = "vt02d01.tex", archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]", author = "Daniel Flipo", doc-group = "Volunteer Task VT02", title = "Validation of {\LaTeX}~2.09 as part of the {\LaTeX3} project", version = "1.02", date = "25 March 1993", time = "17:21:04 MET", status = "public, contributed", author-email = "flipo@alea.citilille.fr", author-address = "Daniel Flipo, UFR de Math\'ematiques B\^at M2, Universit\'e des Sciences et Technologies F-59655 Villeneuve d'Ascq Cedex", abstract = "This is both a call for volunteers to help us in validating \LaTeX~2.09 (one of the tasks of the \LaTeX3 project), and a brief explanation of the kind of work to be done in this area. ", keywords = "Validation, LaTeX", ==================================================================== filename = "vt05d01.tex", archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]", author = "Ed Sznyter", doc-group = "Volunteer task VT05", title = "Research on Syntax for Tables", version = "1.02", date = "02 April 1993", time = "22:48:49 GMT", status = "public, contributed", author-email = "ews@babel.babel.com", abstract = "This is a preliminary overview of the direction for further research on tables. Much research remains to be done; in particular, the bibliography needs to be expanded, especially to include input from graphic designers and SGML users. Commonly requested features are listed, but more are needed. Because of limitations in \TeX\ and the small systems it must run on, many capabilities necessary for high-quality typesetting are unmanageable or must be relegated to optional substyles. Nonetheless, this list should include even functions we can not implement, if only to document the reasons.", keywords = "Tables.Syntax", ==================================================================== filename = "vt11d01.tex", archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]", author = "Mike Piff", doc-group = "Volunteer task VT11", title = "Backus-Naur form in {\LaTeX3}", version = "1.03", date = "02 April 1993", time = "22:49:47 GMT", status = "public, contributed.", author-email = "M.Piff@sheffield.ac.uk", author-address = "Department of Pure Mathematics \\ University of Sheffield \\ Hicks Building \\ Hounsfield Road \\ SHEFFIELD S3 7RH \\ England", ==================================================================== filename = "vt16d01.tex", archived = "*Niord.SHSU.edu:[FILESERV.LTX3PUB]", author = "Rolf Lindgren", doc-group = "Volunteer task VT16", title = "Preliminary report on {\LaTeX} style options to be converted to {\LaTeX3}", version = "1.02", date = "02 April 1993", time = "22:53:48 GMT", status = "Public, contributed.", author-email = "rolfl@ulrik.uio.no", ==================================================================== filename = "bnf.sty", version = "1.05", date = "09 Feb 1993", time = "15:16:48 BST", author = "Mike Piff", address = "Dr M. J. Piff University of Sheffield Department of Pure Mathematics Hicks Building Hounsfield Road SHEFFIELD S3 7RH England", codetable = "ISO/ASCII", telephone = "+44 742 824431", email = "M.Piff@shef.ac.uk (Janet)", keywords = "Backus,Naur,syntax,grammar", supported = "yes", docstring = "A style option to LaTeX for producing Backus-Naur Form syntax notation.", ==================================================================== filename = "vol-task.tex", version = "6.2a", date = "30 April 1993", time = "13:42:19.55 CDT", list-manager = "George D. Greenwade", address = "Department of Economics and Business Analysis College of Business Administration P. O. Box 2118 Sam Houston State University Huntsville, Texas, USA 77341-2118", email = "bed_gdg@SHSU.edu (Internet) BED_GDG@SHSU (BITNET) SHSU::BED_GDG (THENET)", telephone = "(409) 294-1266", FAX = "(409) 294-3712", supported = "yes", archived = "*Niord.SHSU.edu:[FILESERV.VOL-TASK], pip.SHSU.edu:/vol-task.tex", keywords = "LaTeX3, LaTeX, volunteer task list", codetable = "ISO/ASCII", docstring = "This is general volunteer task list in the development of LaTeX3. There are many tasks needing to be done in support of the LaTeX3 project which can be worked on concurrently with the development of the LaTeX3 kernel. Furthermore, some tasks require special expertise not found among the core programming team. Initial research, analysis, and work on these tasks by volunteers can greatly speed up the process of integrating a number of desirable features into LaTeX3. If you are interested in working on a particular task, the first step is to contact the volunteer list manager, noted above, for details. He will either immediately designate you as the `task coordinator' for that task, and assist you in getting answers to any initial questions you may have, or if someone else is already serving as the task coordinator for that task, you will be put in touch with that person, who will discuss with you the current status of the work and ways in which you might contribute." ==================================================================== As noted, each of these files is available for anonymous ftp retrieval from Niord.SHSU.edu (192.92.115.8) in the directory [FILESERV.LTX3PUB]. Additionally, to retrieve the files via e-mail, include: SENDME LTX3PUB.filename_extension in the body of a mail message to FILESERV@SHSU.BITNET (FILESERV@SHSU.edu). For example, to retrieve the file vt16d01.tex, include: SENDME LTX3PUB.VT16D01_TEX in your mail to FILESERV. The command: SENDME LTX3PUB will send all files with a one line request. Finally, these files are available for retrieval or perusal on the Gopher Server based on Niord.SHSU.edu (port 70) in either: LaTeX3 Working Documents/ or TeX-related Materials/ LaTeX3 Working Documents/ The file VOL-TASK.TEX also resides in these directories and may be retrieved in a parallel manner. As a side and quasi-related note, if you have a Gopher client and are into TeX and its relatives, you really ought to look at the: TeX-related Materials/ on Niord's server. Regards, George George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net ------------------------------ 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. Please send contributions to: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: On Internet: send a one line mail message to TeXhax-request@tex.ac.uk SUBSCRIBE TEX-L UNSUBSCRIBE TEX-L On BITNET: send a similar one-line mail message to LISTSERV@xxx On JANET: send a similar one line mail message to TeXhax-request@uk.ac.tex Back issues of the digest are available for anonymous ftp from the UK TeX Archive, tex.ac.uk (134.151.40.18) in [tex-archive.digests.texhax.YY]texhax.NN and ftp.tex.ac.uk (134.151.44.19) in /pub/archive/digests/texhax/YY/texhax.NN where YY = last two digits of year, NN = issue number ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX Archive Network, and may give better response for subscribers in the USA and Europe, respectively. \bye End of TeXhax Digest [Volume 93 Issue 11] ***************************************** From cczdao@mips.ccc.nottingham.ac.uk Thu Aug 26 09:36:31 1993 Flags: 000000000001 Return-Path: Received: from jess.ccc.nottingham.ac.uk by math.utah.edu (4.1/SMI-4.1-utah-csc-server) id AA23362; Thu, 26 Aug 93 09:36:16 MDT Errors-To: TeXhax-Request@tex.ac.uk Received: from ccsun5.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <04167-0@jess.ccc.nottingham.ac.uk>; Thu, 26 Aug 1993 13:17:09 +0100 From: TeXhax-Request@tex.ac.uk To: TeXhax Distribution:;@jess.ccc.nottingham.ac.uk Subject: TeXhax Digest V93 #012 Reply-To: TeXhax@tex.ac.uk Errors-To: TeXhax-Request@tex.ac.uk Distribution: world Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 26 Aug 1993 13:18:51 +0100 Message-Id: <723.746367531@mips.ccc.nottingham.ac.uk> Sender: cczdao@mips.ccc.nottingham.ac.uk TeXhax Digest Thursday, 26 Aug 1993 Volume 93 : Issue 012 % The TeXhax Digest is brought to you as a service of the TeX Users Group % % and UK TeX Users Group in cooperation with the UK TeX Archive group % Today's Topics: FAQ Requested problem with harvard.sty/latex latex for PC LaTeX documentation: FTP site? re: Why \markboth{}{} used in standard LaTeX report style? ? intro to Tex on DOS defining/specifying other fonts... problem while using dvi2ps xdvi with 600dpi fonts? Funny problem with LaTeX what about fonts? TeX capacity problem dvi driver for hpgl plotter Metafont with bbding10 and callig15 LaTeX2e -- A New Version of LaTeX TeX Users Group Election Administrivia: Moderators: David Osborne and Peter Abbott Contributions: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: TeXhax-request@tex.ac.uk ---------------------------------------------------------------------- Date: Fri, 02 Jul 1993 15:54:01 +0200 From: ivan@clt13bi.der.edf.fr (Ivan Maldonado) Subject: FAQ Requested Hello, I would like a copy of the FAQ for LaTeX installation. I am not a root user but have enough filespace to try and install LaTeX under my account on a SPARCstation IPX. Any suggestions will be greatly appreciated. I have started by looking within ftp.uu.net for information and I have never installed LaTeX, would this be the best place to start? Many have tried to discourage me from building LaTeX from scratch, since I have never done it. Thank you, - -Ivan Maldonado (ivan@clt13bi.der.edf.fr) ------------------------------ Date: Fri, 02 Jul 1993 16:24:34 +0100 From: Richard Kaye Subject: problem with harvard.sty/latex PLEASE HELP! I am getting incomprehensible error messages from LaTeX, using harvard.sty. The problem is when I use a cedilla in someone's name. It happens to be a Polish cedilla-e, but the same problem happens if I try cedilla-c. It tells me I never defined \unbox (which is true, I didn't :-) and gets screwed up with ## and #1. The following are the files produced from LATEX TEST BIBTEX TEST LATEX TEST LATEX TEST The errors occur on the very last pass. Can anyone help please? Sorry there's so much junk to follow, but I thought \tracingmacros=1 might help. Thanks for your help, Richard (Kaye) %=============================test.tex======================================= \documentstyle[harvard]{article} \title{test} \begin{document} \bibliographystyle{dcu} \tracingmacros=1 \cite{WW:Bp} \tracingmacros=0 \bibliography{test} \end{document} %=============================test.bib======================================= @ARTICLE{WW:Bp, AUTHOR = {W{\c e}glorz, B.}, TITLE = {On $\omega_{0}$-categoricity of powers}, YEAR = 1969, JOURNAL = {Bull. Acad. Polon. Sci. S\'er. Sci. Math. Astron. Phys.}, VOLUME = 17, PAGES = {195--199} } %=============================test.aux======================================= \relax \bibstyle{dcu} \citation{WW:Bp} \bibdata{test} \harvardcite{WW:Bp}{W{\pc e}glorz}{W{\pc e}glorz}{1969} %=============================test.bbl======================================= \begin{thebibliography}{xx} \harvarditem[W{\c e}glorz]{W{\c e}glorz}{1969}{WW:Bp} W{\c e}glorz, B. (1969). \newblock On $\omega_{0}$-categoricity of powers, {\em Bull. Acad. Polon. Sci. S\'er. Sci. Math. Astron. Phys.} {\bf 17}:~195--199. \end{thebibliography} %===LOG FILE==================test.lis======================================= This is TeX, Version 3.141 [OUCS VMS 3.4] (preloaded format=lplain 92.12.3) 2 JUL 1993 16:11 **test (FS38:[KAYE.DUGALD.FINAL]TEST.TEX;7 LaTeX Version 2.09 <18 March 1992> (FS12:[OX_STD_TEX.TEX.INPUTS]ARTICLE.STY;5 Standard Document Style `article' <14 Jan 92>. (FS12:[OX_STD_TEX.TEX.INPUTS]ART10.STY;6) \c@part=\count79 \c@section=\count80 \c@subsection=\count81 \c@subsubsection=\count82 \c@paragraph=\count83 \c@subparagraph=\count84 \c@figure=\count85 \c@table=\count86 ) (FS38:[KAYE.DUGALD.FINAL]HARVARD.STY;1 harvard bibliography,) (FS38:[KAYE.DUGALD.FINAL]TEST.AUX;2) [...] ! Illegal parameter number in definition of \b@WW:Bp. \crcr \oalign ...z@skip \lineskip .25ex\ialign {##\crcr #1\crcr }} \pc ...x \z@ \crcr \hidewidth \char 24\hidewidth } }\fi \bha@WW:Bp ->W{\pc e }glorz ...eb }{\csname bha@\@citeb \endcsname } \@ifundefined ...me #1\endcsname \relax #2\else #3 \fi [...] l.6 \cite{WW:Bp} ? ! Undefined control sequence. \unbox \z@ \crcr \hidewidth \char 24\hidewidth \oalign ...skip \lineskip .25ex\ialign {##\crcr #1 \crcr }} \pc ...x \z@ \crcr \hidewidth \char 24\hidewidth } }\fi \bha@WW:Bp ->W{\pc e }glorz ...eb }{\csname bha@\@citeb \endcsname } \@ifundefined ...me #1\endcsname \relax #2\else #3 \fi [...] l.6 \cite{WW:Bp} ? \hidewidth ->\hskip \hideskip \hidewidth ->\hskip \hideskip (FS38:[KAYE.DUGALD.FINAL]TEST.BBL;1) [1 ] (FS38:[KAYE.DUGALD.FINAL]TEST.AUX;3) ) Output written on FS38:[KAYE.DUGALD.FINAL]TEST.DVI;3 (1 page, 680 bytes). ------------------------------ Date: Thu, 08 Jul 1993 11:40:35 -0400 From: Ali Taalebi Subject: latex for PC Where can find a Latex which can be run on a PC? Thanks. Regrads, __ _ M. Ali Taalebinezhaad, Email: taalebi@gel.ulaval.ca ------------------------------ Date: Wed, 14 Jul 1993 10:11:41 -0400 From: isaacsl@pluto.crd.ge.com (Lisa Isaacs) Subject: LaTeX documentation: FTP site? All, I do not use LaTeX, but am a Systems Administrator whose users do use LaTeX. We have recently had requests for copies of documentation. I tried to ftp to librea.stanford.edu (which was listed in the readme file in our LaTeX directory (which I didn't install in the first place)), but I got an "unknown host" error. Can anyone tell me where I can ftp a copy of the/some/any documentation? Please respond in email as I don't read this group and am not subscribed to the mailing list. Any help you can give me would be much appreciated! Thanks, Lisa M. Isaacs Systems Administrator General Electric CR & D Phone: (518)387-7460 Email: isaacsl@pluto.crd.ge.com ------------------------------ Date: Fri, 16 Jul 1993 17:55:59 -0400 From: Jerry Leichter Subject: re: Why \markboth{}{} used in standard LaTeX report style? Ethan V. Munson asks why \part in the standard report style invokes \markboth{}{}, which wipes out a "Draft" header that a user was trying to place on every page of a document produced with "ucthesis", which is based on "report". The answer is obvious if viewed in the right context: In the "headings" page- style, you really want this, since otherwise any chapter/section information left over from the previous part might "leak over" into the new part - if, for example, there is some information about the new part before a \chapter is issued. The \markboth has no effect if the pagestyle is "plain" or "empty". Support for the "myheadings" style, which the user is presumably trying to use, is somewhat shakey. There are a number of places in the standard styles, mainly having to do with sectioning, in which the code just assumes that it can play around with the headings and the page style as it wishes. This is one of them. (Note that \chapter, \section, and \subsection also change the page marks. This is done through a level of indirection using the \XXXmark commands, which are no-ops in "myheadings". There should have been a \partmark command defined and used the same way....) One quick hack solution would be to define "\setdraft" (or whatever you want to call it) as "\markboth{Draft}{Draft}\def\markboth#1#2{}". -- Jerry ------------------------------ Date: Sat, 17 Jul 1993 11:53:35 -0500 From: robinson@atax.eng.uab.edu (John M. Robinson) Subject: ? intro to Tex on DOS I would appreciate any suggestions on how to get started using Tex. Accordingly, I would like to acquire a Tex interpreter for my 486 at home. Thanks - -- JOHN ROBINSON | Internet : robinson@atax.eng.uab.edu University of Alabama at Birmingham | ------------------------------ Date: Thu, 22 Jul 1993 23:30:54 -0500 From: "Michael P. Chandler" Subject: defining/specifying other fonts... someone sent me a latex file....after conversion how can i specify..in either file..another font..?? please respond thru email : mpc1@ra.msstate.edu thanx in advance... below are clips of my frustration... mpc1% latex dc.tex This is TeX, C Version 3.0 Sorry, I can't find that format; will try the default. I can't find the default format file! mpc1% xdvi dc.dvi & [1] 712 mpc1% Can't find font cmbx10. Can't find font cmbx12. Can't find font cmr12. xdvi: Not all pixel files were found [1] Exit 1 xdvi dc.dvi mpc1% more dc.tex \documentstyle[12pt]{article} \setlength{\textwidth}{5.94in} \setlength{\textheight}{8.9in} \setlength{\topmargin}{-0.3in} \setlength{\evensidemargin}{0.25in} \setlength{\oddsidemargin}{0.25in} \setlength{\parindent}{0.4in} \renewcommand{\baselinestretch}{1} \begin{document} \begin{center} {\Large \bf Name header \\ Travel Authorization} \end{center} \thispagestyle{empty} \noindent{\bf Date:}\\ {\bf Requestor:}\\ {\bf Authorized Signature:} (phone) \vspace{.2in} \noindent{\bf Expense Code:} \vspace{.2in} \noindent{\bf Travel Purpose:} \vspace{.2in} \noindent{\bf Arrival Date and Time:}\\ {\bf Departure Date and Time:} \vspace{.5in} \noindent\begin{tabular}{|l|l|l|l|c|c|c|} \hline &\multicolumn{1}{c|}{Name} &\multicolumn{1}{c|}{Origin} [discontinued] ------------------------------ Date: Wed, 28 Jul 1993 17:18:31 -0700 From: gupta@uts.amdahl.com (Ajay Gupta) Subject: problem while using dvi2ps Guys, I do not know if this is the right place, I am having the problem while using the dvi2ps, while running the dvi2ps on an .dvi file , it gives me the following error dvi2ps: FATAL--no font lcmssb8.896 or dvi2ps: FATAL--no font cmbx7.300 I could not find these font files anywhere I searched. Any leads/pointers/help are highly appreciated. PLease email then at the following address : gupta@uts.amdahl.com ------------------------------ Date: Thu, 29 Jul 1993 21:44:06 -0400 From: Calvin Clark Subject: xdvi with 600dpi fonts? Because we got new 600dpi printers at our site, we built 600dpi fonts. However, they don't work very well with xdvi; scaling 600dpi fonts a factor of 6 to 8 seems to be a bit hard on the program. Some characters are mangled, and it is not very readable. Has anyone gotten xdvi to produce good results with 600dpi fonts? I was thinking that it might be best to build some pk files with resolution close to that of an X display, say 75 to 100dpi. Has anyone done that successfully? If so, what mf mode settings did you use? Any advice will be appreciated. Thanks in advance for your help. - -Calvin - -- Calvin Clark ------------------------------ Date: Mon, 02 Aug 1993 11:57:17 -0400 From: Debashis Bhattacharya Subject: Funny problem with LaTeX When I try to use \sc inside \footnotesize, I get a funny error message, viz., \\psc\viiipt=amcsc10 scaled 800 is not a loadable font. I do not see why it tries to find amcsc10, when, by claims made in lfonts.tex, all vestigates of AMR fonts should have been removed. Is this a known problem? If so, what is the solution? If not, anybody care to solve this? Debashis Bhattacharya. Yale University. ------------------------------ Date: Wed, 11 Aug 1993 16:23:06 +0200 From: gunter@pastek.cray.com (Gunter ROTH) Subject: what about fonts? Hello, I am Gunter Roth and it is the first time that I try to install a package like tex or latex. So far, I installed tex and latex version 3.1. Everything seems to work fine. At least all my .tex files can be compiled. I then installed xdvi and here is my problem. Who is creating the fonts for xdvi? Which are the fonts tex is using and in which way I can transform them to get a font for xdvi. Furthermore, I want to print my document out as a postscript file, what are the next font conversions to do? It would be great if you could help me out with the fonts questions. I hope to hear soon from you Bye Gunter Roth e-mail: gunter@pastek.cray.com ------------------------------ Date: Wed, 18 Aug 1993 19:32:39 +0900 From: dhlee@hyowon.pusan.ac.kr (Dohoon Lee ) Subject: TeX capacity problem Hi, I try latex in PC, include main memory 8M. But exceeding of Latex is broken with following error message. ! TeX capacity exceeded, sorry [save size=600]. < to be read again > ... .... What should I do ? Please let me know to solve the problem. Thanks in advance. DoeHoon Lee Dept. of Com. Sci. Pusan National Univ. Pusan 609-735, KOREA e-mail: dhlee@hyowon.pusan.ac.kr ------------------------------ Date: Tue, 24 Aug 1993 17:08:58 -0400 From: karron@mcard27.med.nyu.edu (Dan Karron karron@nyu.edu) Subject: dvi driver for hpgl plotter Does anyone have a driver for a hp E sized (E means BIG BIG BIG) pen plotter ? Dan. | karron@nyu.edu (e-mail alias ) Dan Karron, Ph.D.,Research Associate| | Phone: 212 263 5210 Fax: 212 263 7190 New York University Medical Center | | 560 First Avenue Digital Pager <1> 212 397 9330 | | New York, New York 10016 <2> 10896 <3> | ------------------------------ Date: 26 Aug 1993 11:24:48 -0000 From: Mike Piff Subject: Metafont with bbding10 and callig15 Both bbding10.mf (dingbats font) and callig15 (calligraphic font) give error messages when run through metafont. Some of the dingbats are misformed, though I have not examined the callig font closely enough to see whether the problems there are serious. Does anyone have enough knowledge of MF to know what is wrong here? Mike Piff ------------------------------ Date: Wed, 04 Aug 1993 13:32:26 +0200 From: schoepf@sc.ZIB-Berlin.DE (Rainer Schoepf) Subject: LaTeX2e -- A New Version of LaTeX The following announcement was made last week at the Annual meeting of the TeX User's Group (TUG) at Aston University, Birmingham, UK. There will be a new, standardised version of LaTeX (working name: LaTeX2e) being released before the end of 1993. Not much has been said about the new features; the perhaps most important point was that support for PostScript fonts will be built in. The text below was converted automatically from LaTeX source format into plain text by the dvidoc processor. PLEASE SPREAD THE WORD LaTeX2e -- A New Version of LaTeX Leslie Lamport and the LaTeX3 project team July 27, 1993 1 Reasons For LaTeX2e There are two primary reasons for introducing a new version of LaTeX: * Standardisation: a single format incorporating NFSS2, to replace present multiplicity of incompatible formats (NFSS, lfonts, pslfonts, etc.) * Maintenance: a standardised system is essential to a reliable maintenance policy. Note that LaTeX2e is only a ``working name''---thus this may change. 2 Guiding Principles The following two guiding principles are to be followed: I Unmodified version 2.09 input files will produce the same output with LaTeX2e as with version 2.09. II All new features of LaTeX2e will conform to the conventions of version 2.09, making it as easy as possible for current users to learn to use them. 3 Preamble Commands In order to distinguish old (2.09) documents from those using facilities from the new version, LaTeX2e documents will use a different command on the first line. \documentclass[options]{class} The \documentclass command specifies what kind of document this is---for example, article, book, letter, slide. \includepackage[options]{package} Including a package adds new commands and/or redefines existing commands to provide additional functionality. \documentstyle[options,dvidoc]{style} Invokes the LaTeX2.09 compatibility mode. 4 Documentation The new version will be described in a new edition of LaTeX: A document preparation system by Leslie Lamport and in The LaTeX Companion by Goossens, Mittelbach and Samarin (both to be published by Addison-Wesley). The Companion will also contain a complete description of NFSS2. 5 Distribution Policy Maintenace of the new system will be undertaken by the LaTeX3 project team. A complete distribution of all files, incorporating corrections of errors, will be made available twice a year on fixed dates. This will happen even if there were no changes to the files, and hence only the release dates have to be updated. We are currently looking into the possibility of additionally distributing diff files. 6 Error Reports Error reports can be made using a report generating program latexbug.tex. This will be part of the main distribution. Error reports will be accepted only if the version of LaTeX2e that produces the error is not older than one year. Error reports can be sent to the following mail address: latex-bugs@rus.uni-stuttgart.de or a postal address that is to be announced. Rainer Schoepf Konrad-Zuse-Zentrum fuer Informationstechnik Berlin Heilbronner Strasse 10 D-10711 Berlin Federal Republic of Germany or ------------------------------ Date: Wed, 04 Aug 1993 19:54:56 +0700 From: Joachim Lammarsch Subject: TeX Users Group Election Dear TUG members, the terms of all 15 members of the first elected Board of Directors will expire on December 31, 1993. The election to choose the new Board members will be held this fall, and nominations are invited. Enclosed are two items: ttn2n1.sty nom-form.tex This should be all that's needed to generate the nomination form. It will also be available from TUG Office: TeX Users Group Nominations for 1993 Election P.O. Box 869 Santa Barbara, CA 93102-0869 U.S.A Kind regards Joachim Lammarsch (TUG Elections Committee, Chair) PS.: Thanks to Barbara Beeton, who prepared the files. %% [ the two files are separated by a row of *** ] %% ************************************************************************ %% ttn2n1.sty %% IMPORTANT NOTICE: You *MUST* use this version 2.1 of tugnews.sty %% dated Jan. 1993 in order to run vol.2, no.1 of %% _TeX and TUG NEWS_. (Ch. Thiele, Editor, TTN). %% \input report.sty %% default report style, 10pt font \typeout{Version 2.1 -- Jan. 93} \textwidth=29pc \textheight=43pc \voffset=-2pc \overfullrule=0pt \hfuzz=5pt \font\Sectionfont=cmbxsl10 scaled \magstep2 %% \Large = 14.40pt %% \Subsectionfont and \bsl aren't used in TTN 1,3: %% \font\Subsectionfont=cmbxsl10 scaled \magstep1 %% \large = 12pt \font\subsectionbit=cmbxti10 scaled\magstep1 %% bold italic 12pt %% \font\bsl=cmbxsl10 %% bold slant 10pt \font\unsl=cmu10 %% unslant 10pt for %% upright pound sign %test for nfss as suggested by Johannes Braams (cjc, 1992.10) \ifx\undefined\selectfont % If NFSS is not preloaded, do nothing. \else % If NFSS has been preloaded, we need the following: % \font\tenmi=cmmi10 % or better yet: \def\tenmi{\fontfamily{cmm}\fontseries{m}\fontshape{it}% \fontsize{10}{12pt}\selectfont} \fi \newcommand{\Section}[1]{\section*{\centering% \hrule\hrule \vskip.5pc {\Sectionfont #1} \vskip.5pc \hrule\hrule \vskip1pc } } %% The following macro hasn't been used since the prototype: %% Reggie's \Subsection (6 MAY 91): %% 15 JAN 92: not used in 1,1 %% \newcommand{\Subsection}[1]{\subsection*{\centering% %% \centerline{\vrule width 6cm height .5pt} \vskip 6pt %% {{\Subsectionfont #1}} %% \centerline{\vrule width 6cm height .5pt} \vskip 6pt %% } %% } %% 11 JAN 92: added \bibentry, a hanging indent biblio style (Ch.) \newcommand{\bibentry}{\hangindent=\parindent \hangafter=1 \noindent \sloppy \clubpenalty500 \widowpenalty500 \frenchspacing } %% 3 FEB 92: Jackie Damrau provided this: \newenvironment{Address}{\begin{verse}}% {\end{verse}} %% Abbreviations and Logos (some copped from tugboat.cmn): %% for the METAFONT logo font: \font\manual=manfnt %% logo10 \def\MF{{\manual META}\-{\manual FONT}} \def\PS{{\sc Post\-Script}} \def\TUG{\TeX{} Users Group} \def\tug{{\small TUG}} %% added 30 SEP 92 (Ch.) \def\TUB{{\sl TUGboat\/}} \def\TTN{{\sl\TeX{} and TUG NEWS\/}} \def\ttn{{\small TTN}} %% added 30 SEP 92 (Ch.) \def\isbn{{\small ISBN}} %% added 30 SEP 92 (Ch.) \def\issn{{\small ISSN}} %% added 30 SEP 92 (Ch.) \def\nfss{{\small NFSS}} %% added 30 SEP 92 (Ch.) \def\uk{{\small UK}} %% added 15 OCT 92 (Ch.) \def\fax{{\small FAX}} %% added 15 OCT 92 (Ch.) \def\pounds{{\unsl\$}} %% added 15 OCT 92 (Ch.) \def\GUTenberg{{\small GUT}enberg} %% added 2 FEB 93 (Ch.) %% 4 FEB 92: improved versions of LaTeX, and (La)TeX macros: \newcount\TestCount \def\La{\TestCount=\the\fam \leavevmode L\raise.42ex \hbox{$\fam\TestCount\scriptstyle\kern-.3em A$}} \def\LaTeX{\La\kern-.15em\TeX} \def\AllTeX{{(\La)\TeX}} \def\AmSTeX{{\the\textfont2 A}\kern-.1667em\lower.5ex\hbox {\the\textfont2 M}\kern-.125em{\the\textfont2 S}-\TeX} \def\AmSLaTeX{{\the\textfont2 A}\kern-.1667em\lower.5ex\hbox {\the\textfont2 M}\kern-.125em{\the\textfont2 S}-\LaTeX} \def\BibTeX{{\rm B\kern-.05em{\sc i\kern-.025emb}\kern-.08em\TeX}} \def\careof{\leavevmode\hbox{\raise.75ex\hbox{c}\kern-.15em /\kern-.125em\smash{\lower.3ex\hbox{o}}} \ignorespaces} \def\ILaTeX{I\LaTeX} \def\TeCH{{\rm T\kern-.1667em\lower.7ex\hbox{E}\kern-.125em{\sf CH}}} \def\TeXline{{\TeX\kern-0.1em line}} %% 28 JAN 93: from Phil Taylor: \def \UK-TuG{UK-T\lower 0.5 ex \hbox {U}G} %% Miscellaneous: \hyphenation{Karls-ruhe} \let\ts=\thinspace \let\nl=\newline %% CHANGES FROM ttn1-1.sty TO ttn1-2.sty: %% 25 MAY 92: changed \smc to \sc in \BiBTeX def'n (Ch.) %% added \AmSLaTeX def'n (Ch.) %% 14 JUN 92: added \TeXline def (Ch.) %% CHANGES from ttn1-2.sty TO ttn1-3.sty: %% 10 SEP 92: Jackie added {ttnlist} %% ************************************************************************ \documentstyle[twoside]{ttn2n1} %% Version 2.1, Jan. 1993 \pagestyle{empty} % 1992.2.27: fix for underfull hboxes suggested by Phil Taylor (CJC) \tolerance = 1817 \hbadness = \tolerance \begin{document} %% For TTN 2,3 %% Election procedures (1+ page): \Section{1993 \TeX{} Users Group Election} The terms of all 15 members of the first elected Board of Directors will expire on December 31, 1993. The election to choose the new Board members will be held this fall, and nominations are invited. The Bylaws as amended July 25, 1993, provide that ``Any member may be nominated for election to the Board by submitting a nomination petition in accordance with the TUG Election Procedures. Election of the directors shall be by written mail ballot of the entire membership, carried out in accordance with those same Procedures. Each director will hold office for a term of three (3) years. Directors may be re-elected for successive terms.'' The name of any member may be placed in nomination for election to this office by submission of a petition, signed by two other current (1993) members, to the TUG office by the announced deadline. A petition form is attached; additional forms may be obtained from the TUG office. Along with a petition form, each candidate is asked to supply a passport-size photograph, a short biography, and a statement of intent to be included with the ballot; the biography and statement of intent together may not exceed 400 words. The deadline for receipt at the TUG office of petitions and ballot information is September 1, 1993. For this election only, the lengths of some terms will be altered so that not all members of the Board are replaced at the same time, but only one-third. For Board members elected this year, all terms will begin January 1, 1994. Five members of the new Board will have terms that end with the 1995 annual meeting, five with the 1996 annual meeting, and five with the 1997 annual meeting. Thereafter, all new terms will be for three years, from annual meeting to annual meeting. All positions will be elected this year on the same basis, and the members of each of the three groups chosen by lot by the ballot counter. Ballots will be mailed to all members about 30 days after the close of nominations. Marked ballots must be received no more than 6 weeks following the mailing; the exact date will be noted on the ballots. Ballots will be counted by a disinterested party not part of the TUG organization. The results of the election should be available by the end of November. \begin{flushright} Joachim Lammarsch\\ for the Elections Committee \end{flushright} \newpage %% Nomination form (1 page): \newcommand{\SigRule}{\rule{4.5cm}{.5pt}} \newcommand{\DateRule}{\rule{2.3cm}{.5pt}} \Section{Nomination for\\ 1993 TUG Board of Directors Election} Only current (1993) TUG members are eligible to participate. The signatures of two (2) members are required in addition to that of the nominee. {\bf Type or print} names clearly, exactly as they appear in the most recent TUG membership list or on a TUG mailing label; new members should enter the name which they used on their membership application form. Names that do not exactly match the TUG records will not be accepted as valid. \vspace{2pc} \noindent The undersigned TUG members propose the nomination of: \vspace{1pc} \begin{flushleft} \begin{tabular}{@{}ccc@{}} \SigRule & \SigRule & \DateRule \\ \bf Name of nominee & (signature) & (date) \\ \end{tabular} \end{flushleft} \vspace{1pc} \noindent for the position of {\bf Member of the TUG Board of Directors}, for a term beginning {\bf January 1, 1994}. \vspace{2pc} \begin{flushleft} \begin{tabular}{@{}ccc@{}} \multicolumn{3}{c}{\large \bf Members supporting this nomination} \\ \noalign{\vskip1pc} \bf Nominated by & \bf Signature & \bf Date \\ (please print) & & \\ \noalign{\vskip1pc} \SigRule & \SigRule & \DateRule \\ \noalign{\vskip1pc} \SigRule & \SigRule & \DateRule \\ \end{tabular} \end{flushleft} \vspace{1pc} \noindent Return this petition to the TUG office (FAXed submissions will also be accepted). Petitions must be received in the TUG office no later than {\bf September 1, 1993}. \vspace{2pc} {\parfillskip=\parindent \TeX\ Users Group \hfil {\bf FAX: } 805-963-8358\endgraf} {\bf Nominations for 1993 Election} P.O.%Box 869 Santa Barbara, CA 93102-0869 U.S.A. \newpage \end{document} ------------------------------ 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. Please send contributions to: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: On Internet: send a one line mail message to TeXhax-request@tex.ac.uk SUBSCRIBE TEX-L UNSUBSCRIBE TEX-L On BITNET: send a similar one-line mail message to LISTSERV@xxx On JANET: send a similar one line mail message to TeXhax-request@uk.ac.tex For information on the TeX Users Group, please send a message to TUG@math.ams.com, or write TeX Users Group, P.O. Box 869, Santa Barbara, CA 93102, USA. Back issues of the digest are available for anonymous ftp from the UK TeX Archive, tex.ac.uk (134.151.40.18) in [tex-archive.digests.texhax.YY]texhax.NN and ftp.tex.ac.uk (134.151.44.19) in /pub/archive/digests/texhax/YY/texhax.NN where YY = last two digits of year, NN = issue number ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX Archive Network, and may give better response for subscribers in the USA and Europe, respectively. \bye End of TeXhax Digest [Volume 93 Issue 12] ***************************************** From cczdao@mips.ccc.nottingham.ac.uk Fri Sep 10 06:15:38 1993 Flags: 000000000001 Return-Path: Received: from jess.ccc.nottingham.ac.uk by math.utah.edu (4.1/SMI-4.1-utah-csc-server) id AA08181; Fri, 10 Sep 93 06:15:28 MDT Errors-To: TeXhax-Request@tex.ac.uk Received: from ccsun5.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <12791-0@jess.ccc.nottingham.ac.uk>; Fri, 10 Sep 1993 10:51:30 +0100 From: TeXhax-Request@tex.ac.uk To: TeXhax Distribution:;@jess.ccc.nottingham.ac.uk Subject: TeXhax Digest V93 #013 Reply-To: TeXhax@tex.ac.uk Errors-To: TeXhax-Request@tex.ac.uk Distribution: world Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 10 Sep 1993 10:53:18 +0100 Message-Id: <8713.747654798@mips.ccc.nottingham.ac.uk> Sender: cczdao@mips.ccc.nottingham.ac.uk TeXhax Digest Friday, 10 Sep 1993 Volume 93 : Issue 013 % The TeXhax Digest is brought to you as a service of the TeX Users Group % % and UK TeX Users Group in cooperation with the UK TeX Archive group % Today's Topics: Re: LaTeX documentation: FTP site? Re: TeXhax Digest V93 #012 DVI to (Acrobat) PDF driver Latex on PC re: Why \markboth{}{} used in standard LaTeX report style? latex ISO CD template wanted xdvik 1.1 & PostScript font bitmaps available A raw encoding file for type1 text fonts Administrivia: Moderators: David Osborne and Peter Abbott Contributions: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: TeXhax-request@tex.ac.uk ---------------------------------------------------------------------- Date: Fri, 27 Aug 1993 11:50:40 -0000 From: Manuel Carriba Subject: Re: LaTeX documentation: FTP site? Any TeX/LaTeX related documentation can be found in the CTAN archives, i.e. pip.shsu.edu, ftp.tex.ac.uk, ftp.uni-stuttgart.de. You'll find them in the directory tex-archive/documents Some FAQs and other helpfiles can be found in tex-archive/help Hope this helps :-D Manuel Carriba (M.Carriba@dcs.shef.ac.uk) ------------------------------ Date: Fri, 27 Aug 1993 12:13:21 -0400 From: Lee Wittenberg Subject: Re: TeXhax Digest V93 #012 In reply to the following messages: > Date: Thu, 08 Jul 1993 11:40:35 -0400 > From: Ali Taalebi > Subject: latex for PC > > Where can find a Latex which can be run on a PC? > > ------------------------------ > > Date: Sat, 17 Jul 1993 11:53:35 -0500 > From: robinson@atax.eng.uab.edu (John M. Robinson) > Subject: ? intro to Tex on DOS > > I would appreciate any suggestions on how to get started using Tex. > Accordingly, I would like to acquire a Tex interpreter for my > 486 at home. I would recommend the excellent emTeX implementation by Eberhard Mattes. It is available via anonymous ftp from ftp.uni-stuttgart.de. I believe it is also available from pip.shsu.edu, tex.ac.uk, and other sites. -- Lee Wittenberg ------------------------------ Date: Fri, 27 Aug 1993 11:22:21 -0500 From: "Ed.Garay" Subject: DVI to (Acrobat) PDF driver Is anyone working on a DVI to PDF driver for DOS, Unix or OS/2? PDF is the Portable Document Format, the Adobe Acrobat file format, based on the PostScript imaging model, that is capable of representing any PostScript page. If we could get our TeX documents in PDF format, then we could use one of the Acrobat viewers, like Acrobat Reader or Acrobat Exchange, to preview our documents with all the benefits of the Acrobat technology (e.g. font metric emulation, zooming, panning, searching, post-it-like annotations, etc). With Adobe Exchange, we could print PDF documents on PostScript AND EVEN on non-PostScript printers. This, of course, assumes that Adobe Acrobat is going to take off, which I believe it will, and that the Adobe Acrobat products are going to be commonplace and not expensive. Today, you can get Acrobat Exchange for Windows and the Mac for about $120, in the U.S. Acrobat Reader sells for about $50. Acrobat Distiller, which converts PostScript to PDF, sells for $600, but this wouldn't be needed if we had a DVI2PDF driver ;-) Adobe says these products will run on Windows, Mac, DOS and Unix (and OS/2 I hope), in that order. Also, last week I saw a thin (%180 page) PDF specs book published by Adobe, at a local bookstore. I would really like to hear your thoughts on the merits of a DVI2PDF driver. - --- Ed Garay ------------------------------ Date: Mon, 30 Aug 1993 16:29:23 +0200 From: Khaled Odeh Subject: Latex on PC Is Latex on PC exists in public domain. If yes, where can i find it. Khaled ODEH (University of Compiegne *France*) Tel : (33) 44.23.44.23 Poste. 47.33 E-mail : kodeh@dma.univ-compiegne.fr ------------------------------ Date: Wed, 01 Sep 1993 16:44:12 -0700 From: "Ethan V. Munson" Subject: re: Why \markboth{}{} used in standard LaTeX report style? In addition to Jerry Leichter's reply in the last issue of TeXhax, I received some e-mail responses which suggested alternative work-arounds for my problems with headings in the UCTHESIS style. The most useful came from Mike Piff , who recommended that I use either headerfooter.sty or fancyheadings.sty. I tried headerfooter.sty and had great success. For this, Mike has my eternal gratitude and a standing offer of his choice of libation should our paths ever cross. Jerry replied directly to my technical question. I was sorry to see that a documented feature like the \pagestyle{myheadings} should be so fragile. Since his answer didn't really solve my problem, he gets only temporary gratitude but I'll be happy buy him his choice of libation, too. Ethan Munson munson@cs.berkeley.edu ------------------------------ Date: Wed, 08 Sep 1993 15:03:08 +0200 From: matsu@cso.ricoh.co.jp (Akio Matsubara) Subject: latex ISO CD template wanted Dear everybody, I am looking for a ISO Committe Draft template for LATEX. Please reply if anyone has it. Thanks Akio Matsubara Ricoh Japan ------------------------------ Date: Thu, 26 Aug 1993 18:01:35 -0400 From: karl%edu.umb.cs@uk.ac.nsfnet-relay Subject: xdvik 1.1 & PostScript font bitmaps available I've released new versions of: * kpathsea -- my path searching library, * xdvik -- my modified xdvi that uses it, and * psfonts -- Ghostscript-generated bitmaps for the standard PostScript fonts. ftp.cs.umb.edu:pub/tex/{xdvik,psfonts}.tar.gz Please notice the `.gz' instead of `.z' or `.Z' -- the default gzip extension was changed in response to a poll on the GNU newsgroups. I've stopped making the library available separately, since that was causing maintenance hassles. The library is part of the xdvik distribution. I've established a mailing list, tex-k@cs.umb.edu, for bug reports and discussions for the TeX-related stuff I maintain. I hope this will provide for sharing of interim fixes, quicker help when I cannot respond immediately, and so on. To join, email tex-k-request@cs.umb.edu with a message whose body contains a line subscribe your-preferred-email-address I expect to release a new version of dvipsk shortly, perhaps within a week or two. web2c will follow as soon as possible. Here's the NEWS: kpathsea: * Routines to look up TeX font files, default path specifications, etc. * Sort-of pattern matching: /foo//bar matches subdirectories /foo/a/bar, /foo/b/bar, /foo/a1/a2/bar, etc. * $var and ${var} expansion. * Support for MakeTeX... scripts. * Support for fallback resolutions and font. * Lazy evaluation of path elements. * Some runtime debugging support. xdvik: * Rewrite font finding routines to use the new kpathsea facilities. * Update for xdvi patchlevel 17. psfonts: * In Adobe StandardEncoding, and named with leading `r', for the new xdvik. * TFM widths in the PK files match those in the TFM files. * Umlaut character has been corrected (in the GS fonts). * Encoding of psyr* (the symbol font) matches Adobe's. karl@cs.umb.edu Help fight the new programming monopolies -- write lpf@uunet.uu.net. ------------------------------ Date: Wed, 01 Sep 1993 14:48:17 -0700 From: mackay@edu.washington.cs (Pierre MacKay) Subject: A raw encoding file for type1 text fonts Over the course of a rich discussion of virtual fonts, I have finally come to understand and appreciate the full usefulness of Tom Rokicki's careful distinction between input encoding and output encoding in afm2tfm. In a virtual font environment it answers several questions that have recently been raised about the proper encoding of a {\em raw} tfm file. The raw tfm should contain references to every simple (non-composite) character in the actual list of glyphs, and it need not contain anything else. Dozens of possible output encodings are possible, among which DC will of course be a major player, but all those reencodings will be easier and more portable if there is only one {\em raw} encoding. The raw encoding should provide for {\em every} simple character in the font, including all the unmapped characters. Fortunately, the list of unmapped characters is almost as consistent as Adobe Standard Encoding at least in text fonts. I propose therefore the following ASEX.enc (Adobe Standard Coding Extended) to be used with the -p flag in afm2tfm. What is used for the -t flag is wide open, but it can certainly include DC.enc There remains the question of what to do about the various Superfont layouts: Courier in its most prolific version has 352 simple characters and the Monotype TimesNewRomanSF Superfont has 337 simple characters. In the case of TimesNewRoman, the excess is the result of combining the regular with the expert font, and all that is needed is to code the expert part back out into an expert raw TFM file. Then there are only 12 U&lc pairs of additional simple characters. A similar approach can be taken with Courier; many of the symbol characters, together with the borders and dingbats do not belong in a tex encoding anyway. % ------------------------------------------------------------------------- % % This is ASEX encoding. (file ASEX.enc) % % Adobe Standard Encoding Extended. % % Creator: Pierre A. MacKay mackay@cs.washington.edu % Creation Date: Thu Aug 31 08:56:22 PDT 1993 % % This is an input coding file for use with Radical Eye Software's % afm2tfm. Use with the -p flag. This file should also be % used with ps2pk to create a complete set of bitmapped % characters. % % The sole purpose of this file is to ensure that all non-composite % characters in the font are made available in the raw TFM. Therefore % there are no ligatures or any other refinements. The raw TFM % file contains no ligatures or kernings---nothing but character % metrics. We retain Adobe Standard encoding for all mapped % characters on the AFM file, and extend the list by adding % the unmapped simple characters into the empty code positions % from O 200 to O 240. It is assumed that the output coding used % for the TeX tfm will be different from this ( -t flag in afm2tfm ). % % The extended part of this encoding is consistent with the general % run of text fonts from Adobe, BitStream, DTC, Linotype, Monotype, % URW and probably others as well. For SuperFont characters, see below. % % Jan Michael Rynnings has pointed out that a few very carefully designed % fonts, e. g. Adobe Garamond and Adobe Caslon, treat all the accented % characters as simple glyphs (must make for a huge pfa file), and that % this input encoding would not recognize such refinements. True---but % such fonts will be a tiny minority, and can be dealt with by % special encoding files. % % Usage: % afm2tfm .afm -p ASEX.enc -t .enc -v % /ASEXEncoding [ % now 256 chars follow % % The following will replace the characters from 0 to 32 in the raw encoding % if you have access to a SuperFont. There is reason to hope that this % set will be as stable as the unmapped set in current text fonts % If you don't have a SuperFont, and have to create any of these as a % composite, precede the name with a dot, as is done here for % Scedilla and scedilla. The change in name keeps afm2tfm from thinking % that the character already exists when it comes to evaluate the output % (-t flag) encoding. % % 0x00 /Aogonek /Eogonek /Iogonek /Kafii9170 /Lafii9170 /Lcaron /Nafii9170 /Rafii9170 /Safii9170 /.Scedilla /Tafii9170 /Uogonek /.notdef /.notdef /.notdef /.notdef % 0x10 /aogonek /eogonek /iogonek /kafii9170 /lafii9170 /lcaron /nafii9170 /rafii9170 /safii9170 /.scedilla /tafii9170 /uogonek /.notdef /.notdef /.notdef /.notdef % 0x20 % Keep the space, for use as \boundarychar (Give it zero width in vpl) /space /exclam /quotedb /numbersign /dollar /percent /ampersand /quoteright /parenleft /parenright /asterisk /plus /comma /hyphen /period /slash % 0x30 /zero /one /two /three /four /five /six /seven /eight /nine /colon /semicolon /less /equal /greater /question % 0x40 /at /A /B /C /D /E /F /G /H /I /J /K /L /M /N /O % 0x50 /P /Q /R /S /T /U /V /W /X /Y /Z /bracketleft /backslash /bracketright /asciicircum /underscore % 0x60 /quoteleft /a /b /c /d /e /f /g /h /i /j /k /l /m /n /o % 0x70 /p /q /r /s /t /u /v /w /x /y /z /braceleft /bar /braceright /asciitilde /.notdef % % This is the Extension to Adobe Standard Encoding % % In as many of the next 32 positions as necessary, include % all the unmapped simple (non-composite) characters. The % inclusion of Ccedilla and ccedilla is problematic. These are % composites in some schemes, simple in others. Best to % include them here. Characters are entered in alphabetical order % by name. If you need to create your own composite for Ccedilla % ccedilla or Eth, precede the name with a dot as indicated above. % % 0x80 /Ccedilla /Eth /Thorn /brokenbar /ccedilla /copyright /degree /divide /eth /logicalnot /minus /mu /multiply /onehalf /onequarter /onesuperior % 0x90 /plusminus /registered /thorn /threequarters /threesuperior /trademark /twosuperior /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef % % From here on the order is again Adobe Standard Encoding % % 0xA0 /.notdef /exclamdown /cent /sterling /fraction /yen /florin /section /currency /quotesingle /quotedblleft /guillemotleft /guilsinglleft /guilsinglright /fi /fl % 0xB0 /.notdef /endash /dagger /daggerdbl /periodcentered /.notdef /paragraph /bullet /quotesinglbase /quotedblbase /quotedblright /guillemotright /ellipsis /perthousand /.notdef /questiondown % 0xC0 /.notdef /grave /acute /circumflex /tilde /macron /breve /dotaccent /dieresis /.notdef /ring /cedilla /.notdef /hungarumlaut /ogonek /caron % 0xD0 /emdash /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef % 0xE0 /.notdef /AE /.notdef /ordfeminine /.notdef /.notdef /.notdef /.notdef /Lslash /Oslash /OE /ordmasculine /.notdef /.notdef /.notdef /.notdef % 0xF0 /.notdef /ae /.notdef /.notdef /.notdef /dotlessi /.notdef /.notdef /lslash /oslash /oe /germandbls /.notdef /.notdef /.notdef /.notdef ] def % --------------------END of ASEX.enc------------------------------------- Email concerned with UnixTeX distribution software should be sent primarily to: elisabet@u.washington.edu Elizabeth Tachikawa otherwise to: mackay@cs.washington.edu Pierre A. MacKay Smail: Northwest Computing Support Center Resident Druid for Thomson Hall, Mail Stop DR-10 Unix-flavored TeX University of Washington Seattle, WA 98195 (206) 543-6259 ------------------------------ 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. Please send contributions to: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: On Internet: send a one line mail message to TeXhax-request@tex.ac.uk SUBSCRIBE TEX-L UNSUBSCRIBE TEX-L On BITNET: send a similar one-line mail message to LISTSERV@xxx On JANET: send a similar one line mail message to TeXhax-request@uk.ac.tex For information on the TeX Users Group, please send a message to TUG@math.ams.com, or write TeX Users Group, P.O. Box 869, Santa Barbara, CA 93102, USA. Back issues of the digest are available for anonymous ftp from the UK TeX Archive, tex.ac.uk (134.151.40.18) in [tex-archive.digests.texhax.YY]texhax.NN and ftp.tex.ac.uk (134.151.44.19) in /pub/archive/digests/texhax/YY/texhax.NN where YY = last two digits of year, NN = issue number ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX Archive Network, and may give better response for subscribers in the USA and Europe, respectively. \bye End of TeXhax Digest [Volume 93 Issue 13] ***************************************** From cczdao@mips.ccc.nottingham.ac.uk Tue Oct 5 05:28:48 1993 Flags: 000000000001 Return-Path: Received: from jess.ccc.nottingham.ac.uk by math.utah.edu (4.1/SMI-4.1-utah-csc-server) id AA16864; Tue, 5 Oct 93 05:28:30 MDT Errors-To: TeXhax-Request@tex.ac.uk Received: from ccsun5.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <25584-0@jess.ccc.nottingham.ac.uk>; Mon, 4 Oct 1993 13:49:15 +0100 From: TeXhax-Request@tex.ac.uk To: TeXhax Distribution:;@jess.ccc.nottingham.ac.uk Subject: TeXhax Digest V93 #014 Reply-To: TeXhax@tex.ac.uk Errors-To: TeXhax-Request@tex.ac.uk Distribution: world Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Oct 1993 13:51:12 +0100 Message-Id: <695.749739072@mips.ccc.nottingham.ac.uk> Sender: cczdao@mips.ccc.nottingham.ac.uk TeXhax Digest Monday, 4 Oct 1993 Volume 93 : Issue 014 % The TeXhax Digest is brought to you as a service of the TeX Users Group % % and UK TeX Users Group in cooperation with the UK TeX Archive group % Today's Topics: Re: DVI to (Acrobat) PDF driver Re: A raw encoding file for type1 text fonts ASCII Typesetting from a LaTeX file TeX, LaTeX, etc. on IBM PC On why LaTeX uses save stack while reading .aux Tex Installation on Vax babel release modes.mf 1.0 available xdvik 1.2, dvipsk 5.519a available Administrivia: Moderators: David Osborne and Peter Abbott Contributions: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: TeXhax-request@tex.ac.uk ---------------------------------------------------------------------- Date: Sat, 11 Sep 1993 08:48:21 -0400 From: bkph@ai.mit.edu (Berthold K.P. Horn) Subject: Re: DVI to (Acrobat) PDF driver > Is anyone working on a DVI to PDF driver for DOS, Unix or OS/2? Yes, just use DVIWindo. Aside from being a previewer, it will print to anything that has a Windows Printer driver, including the PDF driver. > PDF is the Portable Document Format, the Adobe Acrobat file format, > based on the PostScript imaging model, that is capable of representing > any PostScript page. > If we could get our TeX documents in PDF format, then we could use > one of the Acrobat viewers, like Acrobat Reader or Acrobat Exchange, > to preview our documents with all the benefits of the Acrobat technology > (e.g. font metric emulation, zooming, panning, searching, post-it-like > annotations, etc). With Adobe Exchange, we could print PDF documents > on PostScript AND EVEN on non-PostScript printers. Which is all very well if you are using plain text fonts. With TeX you may find this approach somewhat problematic unless the recipients also has all of the fonts called for in ATM compatible Adobe Type 1 format. This is because (i) you need specialized math fonts for TeX, and (ii) the encoding of fonts used with TeX is usually non standard. > This, of course, assumes that Adobe Acrobat is going to take off, > which I believe it will, and that the Adobe Acrobat products are ... Well, as long as it only exists on one platform (Mac) it won't do much for inter-platform interchange. It does exist for Windows also now, but without Super ATM for Windows is somewhat limited. It also needs an Adobe Windows Printer Driver for Windows to be really useful. > I would really like to hear your thoughts on the merits of a DVI2PDF driver. Well, you can try one now and see whether you like it! Just keep in mind that part of what Acrobat is supposed to do is solve a problem to which we already have a solution when we use TeX, namely document portability. You can move DVI files (or even TeX source) files between many platforms and be able to preview and print them. Regards, Berthold. P.S. I have connections with Y&Y, the source for DVIWindo, DVIPSONE and fonts. ------------------------------ Date: Sat, 11 Sep 1993 08:53:29 -0400 From: bkph@ai.mit.edu (Berthold K.P. Horn) Subject: Re: A raw encoding file for type1 text fonts > Over the course of a rich discussion of virtual fonts, I have > finally come to understand and appreciate the full usefulness > of Tom Rokicki's careful distinction between input encoding > and output encoding in afm2tfm. In a virtual font environment > it answers several questions that have recently been raised about > the proper encoding of a {\em raw} tfm file. The raw tfm > should contain references to every simple (non-composite) > character in the actual list of glyphs, and it need not contain > anything else. I know this will start a flame war, but... The combination of (i) input encoding, (ii) output encoding, plus (iii) virtual font permutation of numeric codes between 0 - 255 is unneccessarily complex and confusing. A much simpler approach just uses the idea of the encoding vector per se. That is, a mapping from numeric codes (0 - 255) to glyph names. DVI processors need the capability to reencode a font on the fly anyway, and the encoding vector provides the mechanism. Obviously, ONE mapping instead of THREE mappings in series is much easier to understand and implement, and is in fact all that is needed. To be concrete, an encoding can be specified in a file containing lines like the following: 32 space 65 A etc. (or whatever equivalent way you want to use to define the encoding). Such a file can be read by DVI file processors, as well as programs that produce metric files in various formats, including TFM for TeX, PFM for Windows, screen fonts for Mac etc. Nothing could be simpler! While I am at it, it is also not necessary to force users to resort to virtual fonts just because they want a different font layout, or because they are using TrueType or Type 1 fonts! It IS possible to make TFM files complete with proper ligature and kerning information, WITHOUT virtual fonts. And it certainly is a lot less confusing. Virtual fonts have many interesting applications, but they are NOT needed for reencoding, and in fact, in and of themselves are quite inadequate for reencoding. The reason is that virtual fonts per se can only provide a PERMUTATION of the encoding vector, since they ONLY deal with numeric codes --- because VF, like TeX itself treat characters as numbers. Hence unencoded characters CANNOT be made accessible by the VF mechanism itself. Which is why all DVI drivers need in ADDITION a mechanism for actually reencoding a font. And once you have THAT, you do not need to use the numeric permutation of the VF to achieve reencoding! It is easy to be mislead by one particular implementation, which (i) forces one to use VF whenever using anything but bitmapped CM fonts, and which (ii) forces use of a complex sequence of three mappings rather than simply the single overall encoding, and (iii) cannot create TFM files complete with ligatures and kerning WITHOUT resorting to VF. Nothing could be more intuitive than the idea of the `encoding vector' Now for some minor details: > ...all the unmapped characters. Fortunately, the list of > unmapped characters is almost as consistent as Adobe Standard > Encoding at least in text fonts. I propose therefore... The set of available glyphs is only consistent amongst Adobe fonts (which uses the same basic set of 228 glyphs for most text fonts). Other vendors implement other sets of glyphs. Lucida Bright text fonts for example have many additional glyphs not found in Adobe text fonts (for a total of 247). An approach based on a fixed `input encoding' that may not cover these extra characters is obviously inferior to one using a single encoding vector. It also cannot cope with the case where there are more than 256 glyphs in a font (Lucida Sans Linedraw has 400). > There remains the question of what to do about the various > Superfont layouts: Courier in its most prolific version has > 352 simple characters and the Monotype TimesNewRomanSF Superfont > has 337 simple characters. In the case of TimesNewRoman, the > excess is the result of combining the regular with the expert There are many fonts that have more than 256 characters, including some of the Lucida family (Lucida UNICODE has over a thousand). You cannot deal with all of these using a fixed `input encoding'. If, however, you drop the idea of THREE sequential mappings and simple use the idea of an encoding vector there is no issue here. You just specify what glyph you want each number to call up. And your driver should allow you to use the same basic font under two TFM names with different encoding. Of course, without partial font downloading of Type 1 fonts (provided only by DVIPSONE), working with these large fonts (like the IBM version of Courier) can become quite unwieldy. % The sole purpose of this file is to ensure that all non-composite % characters in the font are made available in the raw TFM. Therefore % there are no ligatures or any other refinements. The raw TFM % file contains no ligatures or kernings---nothing but character There is no need for separate `raw' TFM and another TFM for a font. Why use two TFM files when one will do? One CAN construct a single TFM file complete with ligatures and kerning based on any user specified encoding, as already stated above. Also, if you take the `three mapping' approach, you want to make sure that the composite characters ARE in the encoding. You do not want to use TeX's \accent to construct composites. Nor should the virtual font mechanism be used to construct composites that the font designer has already created, presumably with careful attention to positioning, and in some cases by actually designing separate glyphs (for example, shallower accents for upper case characters than for lower case). Almost all text fonts have separate character programs for composite characters, hence these are real characters in their own right. True, in many cases these character programs do use either the `seac' Type 1 operator, or `Subr' calls and hence similar shapes can be achieved by combining the base and accent character with suitable positioning. However, in some cases the rendering will not be as good at low resolution, and most fonts treat at least Ccedilla, ccedilla, and Aring as complete separate glyphs that cannot be achieved by overprinting (The reason is that one does not want overlapping contours when the character is `stroked' instead of `filled'). So if you are going to take this approach you'd want to include at least the `standard' 58 composites in your `input encoding'. Of course, with some fonts you then start to run out of space in the limited 0 - 255 range. Which is another reason why the idea of just a single encoding vector is much to be preferred to the `three map' approach. % /Aogonek /Eogonek /Iogonek /Kafii9170 /Lafii9170 /Lcaron /Nafii9170 /Rafii9170 % /Safii9170 /.Scedilla /Tafii9170 /Uogonek /.notdef /.notdef /.notdef /.notdef % 0x10 % /aogonek /eogonek /iogonek /kafii9170 /lafii9170 /lcaron /nafii9170 /rafii9170 % /safii9170 /.scedilla /tafii9170 /uogonek /.notdef /.notdef /.notdef /.notdef The names for basic characters (like `exclam') are pretty much generally agreed upon (even to the point of accepting the misspelled `guillemot' for `guillemet'!). However, when it comes to some of the above there is absolutely no agreement, and you enter the arena of current corporate warfare. It may make sense to use AFII glyph numbers for these characters, as Adobe seems to suggest, or it may make sense to use UNICODE numbers as MicroSoft seems to believe, or we may use the names used by Apple, etc. Should it be Trightcommaaccent, Tcaron, Thacek, 0164 (hex), AFII100256, or ... ? Again, a fixed `input encoding' is guaranteed to loose out in the end because of such incompatabilities. Anyway, these are minor issues. My main point is that designing a unique `input encoding' is not a useful excercise since it is solving a problem unqiue to one implementation which happens to use a complex system of three mappings where one mapping (the encoding vector) is in fact all that is needed. Berthold. P.S. I put all the emphasized words in upper case just to irritate Don Hosek P.P.S. I have connections with Y&Y, which supplies Lucida fonts in Type 1 form. ------------------------------ Date: Wed, 22 Sep 1993 09:30:20 -0400 From: gajoshi@cam.nist.gov (Ghanashyam_A._Joshi) Subject: ASCII Typesetting from a LaTeX file Dear TeXhackers: I need to use my file typeset in LaTeX and create an ASCII output or text output which preserves the typesetting as far as possible. Can you please URGENTLY send me suggestions on how this can be done using any of the style-files of programs out there. Thanks. Ghanashyam Joshi ------------------------------ Date: Mon, 27 Sep 1993 13:53:43 -0400 From: Debashis Bhattacharya Subject: TeX, LaTeX, etc. on IBM PC I am familiar with TeX on Unix systems. I wish to use it on an IBM PC. Are all sources that I need (including fonts, web2c, various macros, some previewer, postscript drivers, etc.) available in an organized manner from one site? I have looked at various README files from ftp.uu.net and labrea.stanford.edu and have not found my answer. Is it meaningful to use TeX under Windows, or should I stick to DOS? Are there guidelines to take care of other similar (perhaps stupid) questions? Debashis Bhattacharya. ------------------------------ Date: Fri, 01 Oct 1993 00:49:54 -0000 From: Chris Thompson Subject: On why LaTeX uses save stack while reading .aux The following came up in a thread "Managing Large LaTeX Files" on comp.text.tex. I think the explanation may deserve recording in a somewhat more durable medium, so I am posting it here as well. In article <...>, Werenfried Spit writes: > In article <...>, kaye@vax.oxford.ac.uk (Richard Kaye) says: > >Has anyone else had save stack overflow when LaTeX read the .aux files? > > > >[Will a TeX guru please explain it to me? I thought \global\def's could not > >cause save stack overflow until I found this problem. If it's a general > >problem, it seems a bit silly that LaTeX should try to input so much > >information in this way.] > > > >I fixed it so that the data was read {\it outside} the group (as part of one > > Could someone explain it to me too? I'm even more puzzled after I tried > out Richards solution and played a bit with it. When you put in > your input file directly after the \documentstyle command the line > \input \jobname.aux > LaTeX reads the aux file without its memory getting overflowed; then > at \begin{document} it reads the aux file again (as expected), but > the memory doesn't overflow this time either. (If you leave out the > \input \jobname.aux LaTeX only reads the aux file during \begin{document} > and then chokes on an exceedence of the save size.) This was a hard one to track down. I could claim that it was all my fault... The entries on the save stack are not the result of the \global\@namedef, which as suggested above never needs to use such a thing. They come from the earlier \@ifundefined call in \newlabel. Change #337 in tex82.bug numbering, applied in TeX 2.9, changed the implicit setting of an undefined control sequence referenced via \csname...\endcsname to \relax (TeXbook, page 213) from being (sort of) global to being local to the current group. Don made this change as a direct result of my posting to TeXhax (year 1987, digest 103) pointing out that the TeXbook didn't correctly describe what happened. The change was a potent source of new bugs, because TeX was not originally designed to cope with token expansion have side-effects of modifying the save stack (see in particular change #371 in tex82.bug). I have more than once wondered whether I should have kept quiet about the whole business... In an ideal world, the problem wouldn't arise because the implicit setting to \relax wouldn't occur at all (IMNSHO). But everything (especially LaTeX) relies on it now, so it's (far) too late to change it. Something to be got right in the next incarnation. Chris Thompson Cambridge University Computing Service Internet: cet1@phx.cam.ac.uk JANET: cet1@uk.ac.cam.phx ------------------------------ Date: Fri, 01 Oct 1993 14:03:55 -0800 From: SYSTEM@SALK-SC2.SDSC.EDU Subject: Tex Installation on Vax Help! I just received a request from a user to install TeX and Latex on a 6220 Vax. Can you tell me where I might find documentation on installing TeX on the VAX. Some have told me that TeX is old and why would I even bother. I suppose you don't have the same opinions, could you explain why you like it. thanks, diane burns-giles system administrator ------------------------------ Date: Fri, 24 Sep 1993 16:31:25 +0200 From: "Johannes L. Braams" Subject: babel release Hi all, Today I put babel release 3.3.2 in the incoming directory of ftp.tex.ac.uk and it has already found its way to its proper place, pub/archive/languages/babel. It wil presumably also find its way to the other CTAN hosts tonight. This release fixes a number of bugs that crept into the jluy release, which was never announced because of them. Johannes Braams PTT Research, P.O. box 421, 2260 AK Leidschendam, The Netherlands. Phone : +31 70 3325051 E-mail : J.L.Braams@research.ptt.nl Fax : +31 70 3326477 ------------------------------ Date: Wed, 29 Sep 1993 15:38:57 -0400 From: Karl Berry Subject: modes.mf 1.0 available I have released version 1.0 of modes.mf. You can get it by anonymous ftp from ftp.cs.umb.edu:pub/tex/modes.mf You can also get it by email from George Greenwade's (thanks, George!) file server if you cannot ftp: mail fileserv@shsu.edu with a body of `sendme modes'. This file is a collection of Metafont mode_def's. It also makes common definitions for write/white printers, `special' information, and landscape mode. This version has new modes for the HP ruggedwriter, the QMS 1725, and 8-character or less abbreviations for all modes. As always, thanks to the contributors. If you have mode_def's which are not listed below, or corrections to the existing ones, please send them to me. Improvements to the exposition, particularly in how to create a new mode_def, are also welcome. karl@cs.umb.edu mode_def AgfaFourZeroZero = % AGFA 400PS mode_def amiga = % Commodore Amiga mode_def AtariNineFive = % Atari 95dpi previewer mode_def AtariNineSix = % Atari 96x96 previewer mode_def AtariSLMEightZeroFour = % Atari ST SLM 804 printer mode_def AtariSMOneTwoFour = % Atari ST SM 124 screen mode_def aps = % Autologic APS-Micro5 mode_def ApsSixHi = % Autologic APS-Micro6 mode_def bitgraph = % BBN Bitgraph at 118dpi mode_def boise = % HP 2680A mode_def CanonCX = % Canon CX, SX, LBP-LX mode_def CanonEX = % CanonEX in LaserWriter Pro 630 mode_def CanonLBPTen = % e.g., Symbolics LGP-10 mode_def ChelgraphIBX = % Chelgraph IBX mode_def CItohThreeOneZero = % CItoh 310 mode_def CItohEightFiveOneZero = % CItoh 8510A mode_def CompugraphicEightSixZeroZero = % Compugraphic 8600 mode_def CompugraphicNineSixZeroZero = % Compugraphic 9600 mode_def crs = % Alphatype CRS mode_def DataDisc = % DataDisc mode_def DataDiscNew = % DataDisc with special aspect ratio mode_def DECsmall = % DEC 17-inch, 1024 x 768 mode_def DEClarge = % DEC 19-inch, 1280 x 1024 mode_def dover = % Xerox Dover mode_def epsdraft = % Epson at 120x72dpi mode_def epsfast = % Epson at 60x72dpi mode_def epsonlo = % Epson at 120x216dpi mode_def EpsonLQFiveZeroZeroMed = % Epson LQ-500, 360x180dpi mode_def EpsonLQFiveZeroZeroLo = % Epson LQ-500, 180x180dpi mode_def EpsonMXFX = % 9-pin Epson MX/FX family mode_def GThreefax = % 200 x 100dpi G3fax mode_def HPDeskJet = % HP DeskJet 500 mode_def HPLaserJetIIISi = % HP Laser Jet IIISi mode_def HPrugged = % HP RuggedWriter 480 mode_def ibm_a = % IBM 38xx (\#1) mode_def IBMD = % IBM 38xx (\#2) mode_def IBMFourZeroTwoNine = % IBM 4029-30, 4250 mode_def IBMFourTwoOneSix = % IBM 4216 mode_def IBMProPrinter = % IBM ProPrinter mode_def IBMSixOneFiveFour = % IBM 6154 display mode_def IBMSixSixSevenZero = % IBM 6670 (Sherpa) mode_def IBMThreeOneSevenNine = % IBM 3179 screen mode_def IBMThreeOneNineThree = % IBM 3193 screen mode_def IBMThreeEightOneTwo = % IBM 3812 mode_def IBMThreeEightTwoZero = % IBM 3820 mode_def IBMEGA = % IBM EGA monitor mode_def IBMVGA = % IBM VGA monitor mode_def imagewriter = % Apple ImageWriter mode_def laserjetfour = % 600dpi HP LaserJet 4 mode_def laserjetlo = % HP LaserJet at 150dpi mode_def lasermaster = % 1000dpi LaserMaster mode_def LASevenFive = % DEC LA75 mode_def LinotypeOneZeroZeroLo = % Linotype Linotronic [13]00 at 635dpi mode_def LinotypeOneZeroZero = % Linotype Linotronic [13]00 at 1270dpi mode_def LinotypeThreeZeroZeroHi = % Linotype Linotronic 300 at 2540dpi mode_def LNZeroOne = % DEC LN01 mode_def LPSTwoZero = % DEC lps20 mode_def LPSFourZero = % DEC LPS40 mode_def lview = % Sigma L-View monitor mode_def MacMagnified = % Mac screens at magstep 1 mode_def MacTrueSize = % Mac screens at 72dpi mode_def NCD = % NCD 19-inch mode_def NEC = % NEC mode_def NEChi = % NEC-P6 at 360x360dpi mode_def Newgen = % Newgen 400dpi mode_def NeXTprinter = % NeXT 400dpi mode_def NeXTscreen = % 100dpi NeXT monitor mode_def nullmode = % TFM files only mode_def OCESixSevenFiveZeroPS = % OCE 6750-PS mode_def okidata = % Okidata mode_def OneTwoZero = % e.g., high-resolution Suns mode_def phaser = % Tektronix Phaser PXi mode_def PrintwareSevenTwoZeroIQ = % Printware 720IQ mode_def qms = % QMS (Xerox engine) mode_def QMSOneSevenTwoFive = % QMS 1725 mode_def QMSOneSevenZeroZero = % QMS 1700 mode_def RicohFourZeroEightZero = % e.g., TI Omnilaser mode_def RicohLP = % e.g., DEC LN03 mode_def SparcPrinter = % Sun SPARCprinter mode_def StarNLOneZero = % Star NL-10 mode_def sun = % Sun and BBN Bitgraph at 85dpi mode_def supre = % Ultre*setter at 2400dpi mode_def toshiba = % Toshiba 13XX, EpsonLQ mode_def ultre = % Ultre*setter at 1200dpi mode_def VarityperFiveZeroSixZeroW = % Varitype 5060W mode_def VarityperFourThreeZeroZeroLo = % Varityper 4300P at 1200dpi mode_def VarityperFourThreeZeroZeroHi = % Varityper 4300P at 2400dpi mode_def VarityperFourTwoZeroZero = % Varityper 4200 B-P mode_def VarityperSixZeroZero = % Varityper Laser 600 mode_def VAXstation = % VAXstation monitor mode_def XeroxDocutech = % Xerox 8790 or 4045 mode_def XeroxEightSevenNineZero = % Xerox 8790 or 4045 mode_def XeroxFourZeroFiveZero = % Xerox 4050/4075/4090 mode_def XeroxNineSevenZeroZero = % Xerox 9700 mode_def XeroxThreeSevenZeroZero = % Xerox 3700 ------------------------------ Date: Wed, 29 Sep 1993 15:36:55 -0400 From: Karl Berry Subject: xdvik 1.2, dvipsk 5.519a available I've released new versions of: * kpathsea -- my path searching library, * xdvik -- my modified xdvi that uses it, and * dvipsk -- my modified dvips that uses it. ftp.cs.umb.edu:pub/tex/{xdvik,dvipsk}.tar.gz I've established a mailing list, tex-k@cs.umb.edu, for bug reports and discussions for the TeX-related stuff I maintain. I hope this will provide for sharing of interim fixes, quicker help when I cannot respond immediately, and so on. To join, email tex-k-request@cs.umb.edu with a message whose body contains a line subscribe your-preferred-email-address Next thing up is web2c. I don't expect to have something releasable for a month at best (so please don't ask :-). As always, thanks to the many people who contributed. Here's the NEWS: kpathsea 1.2 * Running MakeTeXPK is tried before the fallback resolutions. * The final bitmap name uses a variable spec, so DOS & OS/2 can get dpi300/cmr10.pk. * Document TeX-specific features. * Dpi passed to MakeTeXPK via the envvar KPATHSEA_DPI instead of MAKETEX_DPI. xdvik 1.2 * Remove unnecessary backslash-only lines from dependencies in Makefile. * Make -DGREY and -DTEXXET the default. * Runtime control of whether MakeTeXPK is invoked. * Support for drawing EPS files (using Ghostscript). dvipsk 5.519a * Document DVIPSMAKEPK and DVIPSSIZES. * Remove unnecessary backslash-only lines from dependencies in Makefile. * Use the envvar DVIPSHEADERS, and document it. * Do not include the emtex fontlib support, as it likely does not work. * Update for dvips 5.519. karl@cs.umb.edu Help fight the new programming monopolies -- write lpf@uunet.uu.net. ------------------------------ 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. Please send contributions to: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: On Internet: send a one line mail message to TeXhax-request@tex.ac.uk SUBSCRIBE TEX-L UNSUBSCRIBE TEX-L On BITNET: send a similar one-line mail message to LISTSERV@xxx On JANET: send a similar one line mail message to TeXhax-request@uk.ac.tex For information on the TeX Users Group, please send a message to TUG@math.ams.com, or write TeX Users Group, P.O. Box 869, Santa Barbara, CA 93102, USA. Back issues of the digest are available for anonymous ftp from the UK TeX Archive, tex.ac.uk (134.151.79.28) in [tex-archive.digests.texhax.YY]texhax.NN and ftp.tex.ac.uk (134.151.79.32) in /pub/archive/digests/texhax/YY/texhax.NN where YY = last two digits of year, NN = issue number ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX Archive Network, and may give better response for subscribers in the USA and Europe, respectively. \bye End of TeXhax Digest [Volume 93 Issue 14] ***************************************** From cczdao@unicorn.ccc.nottingham.ac.uk Thu Nov 4 10:05:24 1993 Flags: 000000000001 Return-Path: Received: from jess.ccc.nottingham.ac.uk by math.utah.edu (4.1/SMI-4.1-utah-csc-server) id AA29304; Thu, 4 Nov 93 10:04:44 MST Errors-To: TeXhax-Request@tex.ac.uk Received: from ccsun5.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <24932-0@jess.ccc.nottingham.ac.uk>; Thu, 4 Nov 1993 11:23:25 +0000 From: TeXhax-Request@tex.ac.uk To: TeXhax Distribution:;@jess.ccc.nottingham.ac.uk Subject: TeXhax Digest V93 #015 Reply-To: TeXhax@tex.ac.uk Errors-To: TeXhax-Request@tex.ac.uk Distribution: world Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 04 Nov 1993 11:23:23 +0000 Message-Id: <2909.752412203@unicorn.ccc.nottingham.ac.uk> Sender: cczdao@unicorn.ccc.nottingham.ac.uk TeXhax Digest Thursday, 4 Nov 1993 Volume 93 : Issue 015 % The TeXhax Digest is brought to you as a service of the TeX Users Group % % and UK TeX Users Group in cooperation with the UK TeX Archive group % Today's Topics: Bibliographic software, Toronto, Canada Re: ASCII Typesetting from a LaTeX file Inserting graphics in LaTeX documents Re: Raw encoding for type1 text fonts (TeXhax93.014) Macros for AMS-TeX? Postscript driver for HP9000/700 series workstations. FTP site for TeX for OpenVMS Printing Sanskrit Spacing in Bibliography Metafont settings in DECUS distribution? Flushing Inserts ('\midinsert', '\topinsert', etc.) Info needed on VF files (Q) How do you single-space captions in a double-spaced document? Converting troff to TeX? Virtual fonts, aliases problem in LaTeX and DVIPS. Elsevier Science announces availability of ESP-LaTeX New version of subeqnarray available shortly CTAN-US usage summary -- September 1993 Administrivia: Moderators: David Osborne and Peter Abbott Contributions: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: TeXhax-request@tex.ac.uk M O D E R A T O R ' S N O T E Apologies for the delay in sending out this issue, due to vacations and work on other projects. I'm trying to keep to a two-weekly cycle for TeXhax, but that's not always successful! ---DAO ---------------------------------------------------------------------- Date: Tue, 05 Oct 1993 17:22:32 -0000 From: David_Rhead@vme.ccc.nottingham.ac.uk Subject: Bibliographic software, Toronto, Canada There's a firm in Toronto that produces an MS-DOS bibliographic database system. The firm is Balboa Software, and the software is Library Master. (I.e., Library Master is in some respects a potential proprietary alternative to BibTeX. It has database-y things that BibTeX doesn't. Conversely, BibTeX has some things that Library Master doesn't.) I say "potential alternative" because Library Master is currently aimed at "wordprocessor users". I've had mail from Balboa's Harry Hahne to the effect that they'd be interested in trying to do a (La)TeX option. Is there anyone in the Toronto area who'd be interested in collaborating with them? E.g., get emTeX working on a Balboa PC, tell Balboa what sort of interface would seem natural to TeX users? If so, please contact Harry Hahne and/or me. Harry can be mailed as hahne@epas.utoronto.ca ------------------------------ Date: Wed, 06 Oct 1993 09:06:34 -0000 From: S.J.Bishop.topix01@oasis.icl.co.uk Subject: Re: ASCII Typesetting from a LaTeX file I had good results with the dvi2tty program, which came with my (1990 vintage) UNIX TeX distribution. It didn't need any special style files, although I used a few minor tweaks to please the corporate word processing system. Surprisingly enough, I didn't need to set the document in a typewriter font to get acceptable output. Stephen ------------------------------ Date: Wed, 06 Oct 1993 13:04:25 From: heitor@GPEB.UFSC.BR Subject: Inserting graphics in LaTeX documents Hello all: Does anybody have some hint on how to insert in Latex documents, graphic files in any well-known graphic format (e.g. .PCX, .GIF, etc...), or from spreadsheet charts? I'm using PcTeX, running under DOS, and I noticed that \special{... doesn't work at all. Any help will be appreciated! Thanks, Heitor S. Lopes heitor@gpeb.ufsc.br eel3hsl@ibm.ufsc.br ------------------------------ Date: Wed, 06 Oct 1993 16:02:20 -0700 From: mackay@edu.washington.cs (Pierre MacKay) Subject: Re: Raw encoding for type1 text fonts (TeXhax93.014) Wow!!! No need for an outright war though. I really rather like the fact that my message generated some interest. > The combination of (i) input encoding, (ii) output encoding, plus > (iii) virtual font permutation of numeric codes between 0 - 255 is > unneccessarily complex and confusing. If a stable input coding is possible (which is to some extent brought into question below), the confusion is minimised. That's the idea. > A much simpler approach just uses the idea of the encoding vector per > se. That is, a mapping from numeric codes (0 - 255) to glyph names. > DVI processors need the capability to reencode a font on the fly > anyway, and the encoding vector provides the mechanism. In what {\em available} driver? I have the problem of trying to make a variety of accented glyphs available in a variety of environments, where even the assumption of VF capabilities is questionable, but where it is at least possible to suggest to the user that an upgrade to VF capability is a good idea. Alternatively the dvidvi tool makes it possible to unravel the VF mappings so that a simple-minded driver can handle them. > Obviously, ONE mapping instead of THREE mappings in series is much > easier to understand and implement, and is in fact all that is needed. But tools to do this are not generally available, to the best of my knowledge. > It IS possible to make TFM files complete with proper ligature and > kerning information, WITHOUT virtual fonts. And it certainly is a lot > less confusing. Yes, it is, in any number of ways---VPtoVF produces just such a TFM, and if you have a way to avoid the VF file, I guess that's OK too. > Virtual fonts have many interesting applications, but they are NOT needed > for reencoding, and in fact, in and of themselves are quite inadequate for > reencoding. The reason is that virtual fonts per se can only provide a > PERMUTATION of the encoding vector, since they ONLY deal with numeric > codes --- because VF, like TeX itself treat characters as numbers. > Hence unencoded characters CANNOT be made accessible by the VF mechanism > itself. Which is why all DVI drivers need in ADDITION a mechanism for > actually reencoding a font. And once you have THAT, you do not need > to use the numeric permutation of the VF to achieve reencoding! > It is easy to be mislead by one particular implementation, which > (i) forces one to use VF whenever using anything but bitmapped CM fonts, > and which (ii) forces use of a complex sequence of three mappings rather th an > simply the single overall encoding, and (iii) cannot create TFM files > complete with ligatures and kerning WITHOUT resorting to VF. This assumes that the only problem is remapping. It isn't. Let's just take the simple problem of f-ligatures, which in many existing fonts are split between regular and "expert" layouts (which does lamentable things to TeX's ligature and hyphenation capabilities). What VF allows is the ability to make up a tfm that will ultimately call out characters from more than one file of glyphs, or to supplement defective fonts (e.g. a font with lots of nice directional arrows, but all pointing to the west half of the compass) by incorporating Postscript adjustments. > The set of available glyphs is only consistent amongst Adobe fonts > (which uses the same basic set of 228 glyphs for most text fonts). > Other vendors implement other sets of glyphs. Lucida Bright text fonts for > example have many additional glyphs not found in Adobe text fonts (for a > total of 247). An approach based on a fixed `input encoding' that may > not cover these extra characters is obviously inferior to one using a > single encoding vector. It also cannot cope with the case where there > are more than 256 glyphs in a font (Lucida Sans Linedraw has 400). > There are many fonts that have more than 256 characters, including some > of the Lucida family (Lucida UNICODE has over a thousand). You cannot > deal with all of these using a fixed `input encoding'. If, however, you > drop the idea of THREE sequential mappings and simple use the idea of an > encoding vector there is no issue here. You just specify what glyph > you want each number to call up. And your driver should allow you to > use the same basic font under two TFM names with different encoding. > Of course, without partial font downloading of Type 1 fonts (provided > only by DVIPSONE), working with these large fonts (like the IBM > version of Courier) can become quite unwieldy. Especially in the case of METAFONT output, but not alone there, VF techniques allow me to "use the same basic font under two TFM names with different encoding." That is one of the things I like best about them. It is possible to make a single font up with different sets of ligatures and even with looser or tighter kerning (and I do NOT mean tracking). Unicode may have over a thousand registered glyphs, but it happens to omit the couple of dozen that are used by orientalist scholars all over the world for non latin-letter languages in transcription. One of the chief reasons for working with VF was to supply these for Turkish and for Arabic in Roman transcription. Since the Greek fonts produced by all the major foundries I know of are aggressively monotone (Monotype half-promises a Porson Greek, but the last time I asked the promise was well into the future) VF is needed for Greek as well. > There is no need for separate `raw' TFM and another TFM for a font. > Why use two TFM files when one will do? One CAN construct a single > TFM file complete with ligatures and kerning based on any user specified > encoding, as already stated above. In the case of METAFONT output, the complete tfm as distributed can be used as a raw TFM. That works because TeXText encoding is as predictable as Adobe Standard Encoding. What raw fonts need is predictable encoding. I suppose there may be other ways, but I have found it serves very well to supply the needed accent composites even for Computer Modern (or Concrete, or Pandora) by creating (e.g.) cmr10.afm and running it through the afm2tfm and vptovf processes. There may be a better way, but this uses existing tools and has the virtue that the results can be made available to a wide variety of users who need only to be sure that they have VF capabilities. > Also, if you take the `three mapping' approach, you want to make sure > that the composite characters ARE in the encoding. You do not want to > use TeX's \accent to construct composites. Granted---that is exactly the reason for working with VF and providing preset and carefully adjusted composites. > Nor should the virtual font > mechanism be used to construct composites that the font designer has > already created, presumably with careful attention to positioning, and in > some cases by actually designing separate glyphs (for example, shallower > accents for upper case characters than for lower case). There are a few such fonts, and clearly Lucida should have been added to the mention of Adobe Caslon and Garamond. But the majority, even including some of the best classical designs, use composites. Should the composite recipes in officially issued afm files be considered to be barefaced lies? I agree entirely about the flatter accents for Upper case, and in some conventions the Upper Case letters are squatted down so that the accent does not project quite so alarmingly over the type shoulder. For a given publication in a given font I am prepared to work these refinements out even in a font that does not otherwise have them. But then I have to use VF composites to create the composite glyphs. To achieve this it is commonly necessary to take the substrate letter from one font and the accent from another (for example, a transformed copy of the substrate font). I regret having to second-guess the designer but it is all part of the problem created by the open-ended nature of accented character sets. Remember that even Unicode lacks many accent combinations that are in widespread international use for Arabic, Persian Turkish in Romanized transcription. > Almost all text fonts have separate character programs for composite > characters, hence these are real characters in their own right. True, in > many cases these character programs do use either the `seac' Type 1 > operator, or `Subr' calls and hence similar shapes can be achieved by > combining the base and accent character with suitable positioning. However, > in some cases the rendering will not be as good at low resolution, and most > fonts treat at least Ccedilla, ccedilla, and Aring as complete separate > glyphs that cannot be achieved by overprinting (The reason is that one does > not want overlapping contours when the character is `stroked' instead of > `filled'). I seem to remember that I recommended leaving the Ccedilla and ccedilla as encoded simplex characters, even though about half the fonts I am looking at treat them as composites. Aring is a composite in all the fonts I presently have available to study, though I recognize that the taste of the literate public most likely to use the letter disaproves of the way an unadjusted Aring towers over the rest of a line. The last point about stroked characters is an important one, and what it really emphasizes is that if you genuinely care about the fonts you choose you have to be prepared to treat them as individuals, and not try to set them according to a Procrustean general coding. Hold on now---the intent is not so much to fix input encoding into concrete as to {\em stabilize} it so that output encoding can be fluid. > It may make sense to use AFII glyph numbers for these characters, > as Adobe seems to suggest, or it may make sense to use UNICODE numbers as > MicroSoft seems to believe, or we may use the names used by Apple, etc. > Should it be Trightcommaaccent, Tcaron, Thacek, 0164 (hex), AFII100256, or > ... ? Perhaps I should have left those out. Unicode would probably be the best bet, but when is that likely to be generally recognized? Email concerned with UnixTeX distribution software should be sent primarily to: elisabet@u.washington.edu Elizabeth Tachikawa otherwise to: mackay@cs.washington.edu Pierre A. MacKay Smail: Northwest Computing Support Center Resident Druid for Thomson Hall, Mail Stop DR-10 Unix-flavored TeX University of Washington Seattle, WA 98195 (206) 543-6259 ------------------------------ Date: Wed, 06 Oct 1993 21:55:45 +0630 From: amit@cc.iitb.ernet.in Subject: Macros for AMS-TeX? Can someone pass me some info about site(s) where I can find GOOD macro compatible with AMS-TeX. Information about other macros with a wide ranging facility for mathematical expression composition are also welcome. Please help. The call is for David and Peter as well!! Amit Kumar Sinha ------------------------------ Date: Tue, 12 Oct 1993 14:50:16 +0800 From: Lo Wing Tai Subject: Postscript driver for HP9000/700 series workstations. We have dvios but the resolution from pk files are unacceptable. Does anyone know other public domain or commercial available driver for TeX? Thanks, Dr. W. T. Lo Department of Mathematics The Chinese University of Hong Kong Shatin, N.T. Hong Kong email: wtlo@cuhk.hk ------------------------------ Date: Tue, 12 Oct 1993 11:35:43 -0700 From: brian@aa.washington.edu Subject: FTP site for TeX for OpenVMS I realize that UW is the UNIX site for TeX. Can you tell me the name of an ftp site for TeX for VMS, specifically Alpha OpenVMS? Brian Leverson e-mail: brian@aa.washington.edu phone: (206)543-6736 FAX: (206)543-0217 mail: University of Washington Dept of Aeronautics and Astronautics, FS-10 Guggenheim 318A Seattle, WA 98195 ------------------------------ Date: Thu, 14 Oct 1993 14:35:13 +0100 From: J.POTHARST@ELSEVIER.nl Subject: Printing Sanskrit Can anyone please help with the following: I am looking for ways to print Sanskrit characters ("Devanagari") on a laserprinter from a PC, ideally using Wordperfect. Interest includes also the transliterated script (Latin characters with dots, dashes, etc added). I am very interested to hear on any fonts, programs or other tools that are being used to produce texts with these characters. I've been told that a TeX version or application >From the University of Heidelberg (Germany) exists that can produce Devanagari, but I don't have details. Any further information on tools, organisations and persons is highly appreciated. This question is not related to, and does not serve, any commercial purpose. Jan Potharst j.potharst@elsevier.nl ------------------------------ Date: Thu, 21 Oct 1993 18:27:21 -0400 From: wkelly@utkvx.utk.edu Subject: Spacing in Bibliography I am currently trying to make a bibliography list using BiBTeX to meet local requirements for Senior Graduate Thesis. The Thesis have to be doubled space, with no extra spacing between the bibliography entrees. I've tried modifying \parskip, but to no avail. Everything works okay in the main text, it is just the bibliography that adds the extra spacing. Any suggestions? Bill Kelly Mathematics and Computer Science Dept. Maryville College email: wkelly@utkvx.utk.edu Maryville, TN 37801 (internet) ------------------------------ Date: Fri, 22 Oct 1993 13:15:01 -0000 From: David_Rhead@vme.ccc.nottingham.ac.uk Subject: Metafont settings in DECUS distribution? A colleague got TeX-and-friends for VAX/VMS via DECUS. The DECUS suite includes .pk files. I guess that these were generated with some Metafont settings intended for DEC's LN03. When my colleague uses these .pk files for output on our Hewlett-Packard LaserJet IIISi, he gets output that (some say) seems "better" than the output that other people get using the (CanonCX?) settings that, from modes.mf, one might expect to do well on a IIISi. To consider using such .pk files on non-VMS systems, one would need to know the relevant Metafont settings. Unfortunately, there does not seem to be a consensus about what should be done for an LN03 (assuming that LN03 is the DECUS target printer). At Aston, [tex-archive.metafont.vms] suggests blacker=0.2 (or 0.3, or 0.65) fillin=-0.4 o_correction=0.5 while [tex-archive.metafont.contrib] suggests (for RicohLP=LN03) blacker= 0.65 fillin=-0.2 o_correction=0.5 Does anyone know what Metafont settings were actually used to generate the .pk files in the DECUS distribution? ------------------------------ Date: Mon, 25 Oct 1993 18:26:39 -0500 From: whw@uiuc.edu (Bill Weedon) Subject: Flushing Inserts ('\midinsert', '\topinsert', etc.) Dear TeX Hackers, I am looking for a command to flush inserts created with either '\midinsert' or '\topinsert' (call this new fictional command '\flushinsert'). Here is my problem. I am writing a conference paper in plain TeX and I have several figures (each enclosed in a '\topinsert') near the end of the document. I am also using BibTeX with the macro file 'btxmac.tex' to produce my reference list. The editor of the conference proceedings wants the reference list to start after the last figure, but not necessarily on a new page. I would like to have a command '\flushinsert' to flush the figures and start the reference list afterwards. I have solved the problem temporarily by enclosing the last three figures in a '\pageinsert' and doing a '\break' just before the reference list. However, a more general solution to this problem would be nice. I can make my document and figures available, if necessary. As an aside, can someone please explain the functional difference between '\break' in vertical mode and '\eject'? Thanks, Bill Bill Weedon Graduate Research Assistant Electromagnetics Laboratory ECE Department, M/C 702 Office: 217-333-1047 University of Illinois FAX: 217-244-7345 1406 West Green Street E-mail: whw@uiuc.edu Urbana, IL 61801-2991 (Internet) ------------------------------ Date: Sat, 30 Oct 1993 16:28:00 +0000 From: ajcarr@CCVAX.UCD.IE Subject: Info needed on VF files (Q) If I use the NFSS2 nftimes style, I can get all my text typeset in Times Roman, but the math (including variable names like `x') remain in cmmi. Is it possible to design a TFM and a VF file which I can substitute for cmmi which will use Times Italic for the letters and numbers, but cmmi for the special symbols? I suppose that this is so obvious that someone would have done it long ago. Please respond direct, and I will summarise for the Digest if I get enough responses. Thanks in advance. Alun A. J. Carr, Mech. Eng. Dept., UCD, Belfield, Dublin 4, Ireland Internet: ajcarr@ccvax.ucd.ie ------------------------------ Date: Mon, 01 Nov 1993 13:16:33 -0800 From: "Ethan V. Munson" Subject: How do you single-space captions in a double-spaced document? Hi - I'm the person maintaining the UCTHESIS style for LaTeX. This style approximates double-spacing by setting the \baselinestretch to 1.37. However, certain elements of the document must be single-spaced. To do this, the style uses the \ssp macro: \def\ssp{\def\baselinestretch{1.0}\large\normalsize} Here is an example of the \ssp macro being used to make tabular environments be single-spaced: \def\tabular{\par\ssp\let\@halignto\@empty\@tabular} One document element I'd also like to be single-spaced is captions for figures and tables, so the style includes the following code: \long\def\@makecaption#1#2{% \vskip 10\p@ \setbox\@tempboxa\hbox{#1: #2}% \ifdim \wd\@tempboxa >\hsize % IF longer than one line: {\ssp#1: #2}\par % THEN set as ordinary paragraph. \else % ELSE center. \hbox to\hsize{\hfil\box\@tempboxa\hfil}% \fi} But this does not work even though the 5th line clearly invokes the \ssp macro. I've been able to use the \message macro to check the value of \baselinestretch at every point in that line. The value starts at 1.37, changes to 1.00 immediately after the \ssp macro, and returns to 1.37 after the closing brace. I suspect that there is something tricky about the way captions are handled because they are in floats, but I am not able to figure it out. Can anyone help with this problem? Ethan Munson munson@cs.berkeley.edu ------------------------------ Date: Wed, 03 Nov 1993 18:52:16 -0800 From: John O'Rourke Subject: Converting troff to TeX? Anyone recall seeing something that reads troff and writes TeX? Regards, John O'Rourke loyola@crl.com ------------------------------ Date: Thu, 04 Nov 1993 16:35:00 +1000 From: H.LING@qut.edu.au Subject: Virtual fonts, aliases problem in LaTeX and DVIPS. Hello TeX experts, Re: LaTeX, DVIPS fonts, aliases problem I would be most grateful if you could help me with the 2 problems below. My VAX VMS site has experienced peculiar problems with LaTeX and DVIPS with regards to the new virtual fonts. Problem 1 - --------- Around 9/1992, I got all the TeX and DVIPS savesets from the ftp site ymir.claremont.edu. I then installed them. The DVIPS is by Tomas Rokicki, version 5490 and has the virtual fonts (e.g. ptmr.vf, ptmr.tfm and rptmr.tfm) with it which I installed. Lately, some users been using postscript fonts such as times-roman and helvetica. When they tried to do LaTeX, it complained bad fonts. WHY???? Are my TeX and LaTeX too old? I have $set watch file/class=all on and it was accessing the ptmri.tfm alright. See the trace below: bauple> latex vhhl This is TeX, Version 3.14 [PD VMS 3.3a] (preloaded format=lplain 92.2.15) (DSKC:[TEX.TESTING]VHHL.TEX;6 LaTeX Version 2.09 <14 January 1992> (TEX_ROOT:[INPUTS.LOCAL]QITDOC.STY;1 Document Style 'qitdoc'. Version 0.05 --- 1988 May 27 (TEX_ROOT:[INPUTS.LOCAL]QITDOC11.STY;1)) (DSKC:[TEX.TESTING]VHHL.AUX;2) ! Font \txxx=ptmri at 36.0pt not loadable: Bad metric (TFM) file. So I used AFM2TFM and then VPTOVF to regenerate the fonts which resolved the problem. Problem 2 - --------- My users did not like to use aliases for fonts names. So, what I did was to use the same conventional names as the alias name in the psfonts.map file and using these long names in the AFM2TFM and VPTOVF commands. What this means is that times-roman.tfm is not the old font but the virtual font. Is there any implications for other programs? I found out my XDVI (pre 1989) did not like the new fonts and I read somewhere that only XDVI 1.4 or later can handle virtual fonts. Is this correct? Thanks in advance, How-Hie Ling. h.ling@qut.edu.au Queensland Uni of Technology, Brisbane, Australia ------------------------------ Date: Thu, 21 Oct 1993 13:20:21 +0100 From: "Nico A.F.M. Poppelier" (Tel 31-20-5803482) Subject: Elsevier Science announces availability of ESP-LaTeX Elsevier Science has the pleasure to announce the availability of their ESP-LaTeX package from the Comprehensive TeX Archive Network (CTAN). In order to assist authors in preparing their papers for articles published by Elsevier Science Publishers in such a way that their files can be used to print the article, we have developed a LaTeX package ESP-LaTeX, consisting of a document style `espart' and a booklet with instructions to authors. Authors are kindly requested to use the `espart' document style. This document style, which produces a preprint-like output, enables the Publisher to adapt the article to the layout and style of the journal in which the article will appear (the Publisher will replaced `espart' by a journal-specific production document style). The ESP-LaTeX package contains the following files. Please make sure that you retrieve all these files. readme.esp Brief instructions. espart.sty The main document style. Copy this to the directory where all other .sty files are. espart12.sty The pointsize-related definitions. Copy this to the directory where all other .sty files are. The ESP-LaTeX package can be obtained using anonymous FTP from the Comprehensive TeX Archive Network (CTAN): host names: CTAN directory: - -------------------- ------------------------------------------ ftp.uni-stuttgart.de /pub/tex/macros/latex/contrib/elsevier ftp.tex.ac.uk /pub/archive/macros/latex/contrib/elsevier ftp.shsu.edu /tex-archive/macros/latex/contrib/elsevier Questions concerning the LaTeX author-prepared article project and requests for the booklet with instructions to authors should be directed to the address on the inside cover of one of the journals participating in the project. Nico Poppelier Manager for the LaTeX author-prepared article project ------------------------------ Date: Tue, 02 Nov 1993 15:40:51 +0100 From: "Johannes L. Braams" Subject: New version of subeqnarray available shortly Hi, Today I have put a new version of the subeqnarray option in the incoming directory of ftp.tex.ac.uk. I am sure it will find its way to the proper place in CTAN shortly. The difference between this version, 2.0 and the previous one, 1.1, is that it now checks if the user specified either one (or both) of the options leqno and fleqn. Regards, Johannes Braams PTT Research, P.O. box 421, 2260 AK Leidschendam, The Netherlands. Phone : +31 70 3325051 E-mail : J.L.Braams@research.ptt.nl Fax : +31 70 3326477 ------------------------------ Date: Wed, 06 Oct 1993 09:05:39 -0600 From: "George D. Greenwade" Subject: CTAN-US usage summary -- September 1993 TOTALS FOR SUMMARY PERIOD Wed Sep 1 1993 TO Thu Sep 30 1993 Files Transmitted During Summary Period 132516 Bytes Transmitted During Summary Period 11156239589 Systems Using Archives 0 Average Files Transmitted Daily 4417 Average Bytes Transmitted Daily 371874653 Daily Transmission Statistics Number Of Number of Average Percent Of Percent Of Date Files Sent Bytes Sent Xmit Rate Files Sent Bytes Sent - --------------- ---------- ----------- ---------- ---------- ---------- Wed Sep 1 1993 4740 639403757 10.2 KB/s 3.58 5.73 Thu Sep 2 1993 30036 784316348 8.4 KB/s 22.67 7.03 Fri Sep 3 1993 12780 474383193 7.6 KB/s 9.64 4.25 Sat Sep 4 1993 1568 215966902 12.8 KB/s 1.18 1.94 Sun Sep 5 1993 2259 100418333 8.3 KB/s 1.70 0.90 Mon Sep 6 1993 1966 133531811 10.9 KB/s 1.48 1.20 Tue Sep 7 1993 3506 357412081 6.5 KB/s 2.65 3.20 Wed Sep 8 1993 3091 818686870 10.2 KB/s 2.33 7.34 Thu Sep 9 1993 1467 422399485 10.5 KB/s 1.11 3.79 Fri Sep 10 1993 1582 200169264 4.4 KB/s 1.19 1.79 Sat Sep 11 1993 1777 142370666 5.9 KB/s 1.34 1.28 Sun Sep 12 1993 1168 58516174 11.0 KB/s 0.88 0.52 Mon Sep 13 1993 3443 346080667 7.7 KB/s 2.60 3.10 Tue Sep 14 1993 3467 495492262 9.9 KB/s 2.62 4.44 Wed Sep 15 1993 8265 519389193 4.5 KB/s 6.24 4.66 Thu Sep 16 1993 3379 339310317 3.6 KB/s 2.55 3.04 Fri Sep 17 1993 3655 242231830 8.4 KB/s 2.76 2.17 Sat Sep 18 1993 1656 201385046 11.6 KB/s 1.25 1.81 Sun Sep 19 1993 5471 154574819 4.6 KB/s 4.13 1.39 Mon Sep 20 1993 8020 489297353 6.7 KB/s 6.05 4.39 Tue Sep 21 1993 2626 360994684 4.8 KB/s 1.98 3.24 Wed Sep 22 1993 1671 297766050 7.7 KB/s 1.26 2.67 Thu Sep 23 1993 3422 432748660 4.5 KB/s 2.58 3.88 Fri Sep 24 1993 3074 410387999 4.9 KB/s 2.32 3.68 Sat Sep 25 1993 1529 148110909 6.9 KB/s 1.15 1.33 Sun Sep 26 1993 1444 196491225 9.3 KB/s 1.09 1.76 Mon Sep 27 1993 5835 241581838 5.0 KB/s 4.40 2.17 Tue Sep 28 1993 4632 1392929803 19.6 KB/s 3.50 12.49 Wed Sep 29 1993 1600 214632122 2.7 KB/s 1.21 1.92 Thu Sep 30 1993 3387 325259928 3.6 KB/s 2.56 2.92 Total Transfers from each Archive Section ---- Percent Of ---- Archive Section Files Sent Bytes Sent Files Sent Bytes Sent - ------------------------- ---------- ----------- ---------- ---------- Index/Informational Files 742 236791308 0.56 2.12 bin 20 345125 0.02 0.00 bin/ftp-exec 5 513 0.00 0.00 doc 3 122205 0.00 0.00 economics 4 7196938 0.00 0.06 economics/EconData 20 10402404 0.02 0.09 etc 2 660 0.00 0.00 etc/msgs 1 1225 0.00 0.00 incoming 2 91812 0.00 0.00 incoming/comp-fonts-FAQ 24 1725688 0.02 0.02 incoming/jpeg 2 152143 0.00 0.00 incoming/npr 6 303300 0.00 0.00 incoming/psutils 2 191072 0.00 0.00 incoming/sgi 1 199 0.00 0.00 incoming/texit 2 79124 0.00 0.00 incoming/treetex 8 37111 0.01 0.00 pub 37 1308599 0.03 0.01 pub/MaasInfo 5 83266 0.00 0.00 pub/cdrom 11 580373 0.01 0.01 pub/ftp-list 83 3933253 0.06 0.04 pub/ltx3pub 158 3632405 0.12 0.03 tex-archive 1361 2400487679 1.03 21.52 tex-archive/archive-tools 4609 210237265 3.48 1.88 tex-archive/bibliography 4856 103724470 3.66 0.93 tex-archive/digests 2752 69314531 2.08 0.62 tex-archive/documentation 2225 50441020 1.68 0.45 tex-archive/dviware 6415 239999579 4.84 2.15 tex-archive/fonts 29679 903519346 22.40 8.10 tex-archive/graphics 4604 87342043 3.47 0.78 tex-archive/help 953 79604037 0.72 0.71 tex-archive/indexing 946 10994508 0.71 0.10 tex-archive/languages 7918 197251258 5.98 1.77 tex-archive/macros 38128 1191865483 28.77 10.68 tex-archive/misc 53 2588365 0.04 0.02 tex-archive/support 4610 124424517 3.48 1.12 tex-archive/systems 17708 5134379468 13.36 46.02 tex-archive/web 4553 83079105 3.44 0.74 Total Transfer Amount By Domain Number Of Number of Average Percent Of Percent Of Domain Name Files Sent Bytes Sent Xmit Rate Files Sent Bytes Sent - ----------- ---------- ------------ ---------- ---------- ---------- at 73 656076 3.7 KB/s 0.06 0.01 au 14045 788129076 5.9 KB/s 10.60 7.06 be 317 28053356 1.9 KB/s 0.24 0.25 br 62 5377882 0.8 KB/s 0.05 0.05 ca 5119 754330106 4.5 KB/s 3.86 6.76 ch 308 21388123 16.3 KB/s 0.23 0.19 cl 8 2053709 3.3 KB/s 0.01 0.02 cr 36 8189266 3.3 KB/s 0.03 0.07 cz 14 233140 0.6 KB/s 0.01 0.00 de 1505 54989094 1.2 KB/s 1.14 0.49 dk 221 29854139 4.5 KB/s 0.17 0.27 es 146 20113848 1.1 KB/s 0.11 0.18 fi 283 11614190 8.0 KB/s 0.21 0.10 fr 1736 142116187 9.8 KB/s 1.31 1.27 gr 25 299306 3.4 KB/s 0.02 0.00 hk 144 4325092 1.2 KB/s 0.11 0.04 hu 45 2543453 1.6 KB/s 0.03 0.02 ie 10 524597 0.6 KB/s 0.01 0.00 il 69 1025807 2.4 KB/s 0.05 0.01 in 1 1169695 0.6 KB/s 0.00 0.01 it 221 27881663 3.5 KB/s 0.17 0.25 jp 88 2333739 3.6 KB/s 0.07 0.02 kr 62 10760612 2.5 KB/s 0.05 0.10 mx 1243 13645464 2.0 KB/s 0.94 0.12 nl 1541 44739639 2.9 KB/s 1.16 0.40 no 22 3740876 1.6 KB/s 0.02 0.03 nz 310 28993326 2.6 KB/s 0.23 0.26 pl 2 7862 1.1 KB/s 0.00 0.00 pt 6 108275 1.5 KB/s 0.00 0.00 se 76 2763510 2.3 KB/s 0.06 0.02 sg 95 20543387 1.1 KB/s 0.07 0.18 si 10 64730 3.6 KB/s 0.01 0.00 tw 762 100398023 2.0 KB/s 0.58 0.90 uk 1086 43908740 5.6 KB/s 0.82 0.39 us 90 693789 2.1 KB/s 0.07 0.01 za 90 6037495 0.3 KB/s 0.07 0.05 com 8029 956927996 3.9 KB/s 6.06 8.58 edu 83585 4790386033 14.6 KB/s 63.08 42.94 gov 1166 769859331 19.6 KB/s 0.88 6.90 int 21 7620596 3.8 KB/s 0.02 0.07 mil 694 131115187 18.8 KB/s 0.52 1.18 net 149 38721029 30.4 KB/s 0.11 0.35 org 1087 169293265 2.3 KB/s 0.82 1.52 shsu.edu 8 1917908 47.9 KB/s 0.01 0.02 unresolved 7906 2106790972 6.5 KB/s 5.97 18.88 These figures only reflect ANONYMOUS FTP transfers. There are many sites which mount the archives via NFS, and those transfers are not logged and reported by this program. Top 15 Most Popular Archive Sections By Bytes Transferred ---- Percent of ---- Archive Section Files Sent Bytes Sent Files Sent Bytes Sent - ------------------------- ---------- ----------- ---------- ---------- tex-archive/systems 17708 5134379468 13.36 46.02 tex-archive 1361 2400487679 1.03 21.52 tex-archive/macros 38128 1191865483 28.77 10.68 tex-archive/fonts 29679 903519346 22.40 8.10 tex-archive/dviware 6415 239999579 4.84 2.15 Index/Informational Files 742 236791308 0.56 2.12 tex-archive/archive-tools 4609 210237265 3.48 1.88 tex-archive/languages 7918 197251258 5.98 1.77 tex-archive/support 4610 124424517 3.48 1.12 tex-archive/bibliography 4856 103724470 3.66 0.93 tex-archive/graphics 4604 87342043 3.47 0.78 tex-archive/web 4553 83079105 3.44 0.74 tex-archive/help 953 79604037 0.72 0.71 tex-archive/digests 2752 69314531 2.08 0.62 tex-archive/documentation 2225 50441020 1.68 0.45 ------------------------------ 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. Please send contributions to: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: On Internet: send a one line mail message to TeXhax-request@tex.ac.uk SUBSCRIBE TEX-L UNSUBSCRIBE TEX-L On BITNET: send a similar one-line mail message to LISTSERV@xxx On JANET: send a similar one line mail message to TeXhax-request@uk.ac.tex For information on the TeX Users Group, please send a message to TUG@math.ams.com, or write TeX Users Group, P.O. Box 869, Santa Barbara, CA 93102, USA. Back issues of the digest are available for anonymous ftp from the UK TeX Archive, tex.ac.uk (134.151.79.28) in [tex-archive.digests.texhax.YY]texhax.NN and ftp.tex.ac.uk (134.151.79.32) in /pub/archive/digests/texhax/YY/texhax.NN where YY = last two digits of year, NN = issue number ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX Archive Network, and may give better response for subscribers in the USA and Europe, respectively. \bye End of TeXhax Digest [Volume 93 Issue 15] ***************************************** From TeXhax-request@jess.ccc.nottingham.ac.uk Fri Dec 10 16:20:22 1993 Flags: 000000000001 Return-Path: Received: from jess.ccc.nottingham.ac.uk by math.utah.edu (4.1/SMI-4.1-utah-csc-server) id AA26760; Fri, 10 Dec 93 16:20:06 MST Errors-To: TeXhax-Request@tex.ac.uk Received: from ccsun5.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <24975-0@jess.ccc.nottingham.ac.uk>; Fri, 10 Dec 1993 17:34:29 +0000 From: TeXhax-Request@tex.ac.uk To: TeXhax Distribution:;@jess.ccc.nottingham.ac.uk Subject: TeXhax Digest V93 #016 Reply-To: TeXhax@tex.ac.uk Errors-To: TeXhax-Request@tex.ac.uk Distribution: world Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 10 Dec 1993 17:34:41 +0000 Message-Id: <5177.755544881@unicorn.ccc.nottingham.ac.uk> Sender: cczdao@unicorn.ccc.nottingham.ac.uk TeXhax Digest Friday, 10 Dec 1993 Volume 93 : Issue 016 % The TeXhax Digest is brought to you as a service of the TeX Users Group % % and UK TeX Users Group in cooperation with the UK TeX Archive group % Today's Topics: Re: How do you single-space captions in a double-spaced document? Re: Metafont settings in DECUS distribution? Abbreviation marks for feet and inches Making large circles in LaTeX or PicTeX Re: Inserting graphics in LaTeX documents DVIJEP -j option for VAX/VMS systems Searching for items in UK CTAN Re: Searching for items in UK CTAN TeX Solaris 2.X TeX etc. TeX converters to Braille? Invisible printing! Report on the inaugural meeting of the NTS group, September 1993 modes.mf 1.1 available [comp.text.tex] announcing the French Style Files distribution V3,25 [comp.text.tex] German dictionary available for ftp announcement Donald E. Knuth Scholarship Administrivia: Moderators: David Osborne and Peter Abbott Contributions: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: TeXhax-request@tex.ac.uk ---------------------------------------------------------------------- Date: Thu, 04 Nov 1993 13:05:35 -0800 From: "Ethan V. Munson" Subject: Re: How do you single-space captions in a double-spaced document? Mike Piff came to my rescue for the second time with the following observation: > I suspect that the answer is a simple one. > > Try {\ssp#1: #2\par} instead. (Set paragraph before forgetting single > spacing.) The original line of code was: {\ssp#1: #2}\par Mike's suggestion solved the problem. Ethan Munson munson@cs.berkeley.edu ------------------------------ Date: Thu, 04 Nov 1993 17:39:41 -0500 From: Bill Denning Subject: Re: Metafont settings in DECUS distribution? David Rhead writes: >>A colleague got TeX-and-friends for VAX/VMS via DECUS. >>The DECUS suite includes .pk files. I guess that these were generated with >>some Metafont settings intended for DEC's LN03. >>Does anyone know what Metafont settings were actually used to generate the >>.pk files in the DECUS distribution? Try contacting the DECUS TeX Collection editor, Ted Nieland. If Ted can't help himself, he can probably refer you to the folks who did the port. ted@nieland.dayton.oh.us nieland@decus.org ------------------------------ Date: Thu, 04 Nov 1993 18:01:01 -0500 From: Bill Denning Subject: Abbreviation marks for feet and inches >From time to time I need to write LaTeX documents that include measurements in feet and inches. What I'm looking for is a method of using the ' and " marks to abbreviate feet and inches. I've tried several simple macros, but with limited success. \newcommand{\inch}{{\tt "}} This does exactly what I want for inches, but I can't seem to get a similar vertical mark for feet -- what I really would like is half of the " mark in the \tt font. {\tt '} and {\tt `} give "curled" marks, and \verb doesn't seem to help either. As an alternative, I've also tried: \newcommand{\feet}{$^{^{\small\prime}}$} \newcommand{\inch}{\feet\feet} At least the marks are consistent with each other, but I'm not really satisfied with the results. (Most of the time I use \large for the type size of my text. ) Can anyone make any other suggestions? Thanks for your help, Bill ------------------------------ Date: Thu, 04 Nov 1993 18:50:58 -0500 From: Bill Denning Subject: Making large circles in LaTeX or PicTeX Does anyone have any experience in creating large circles in either PicTeX or the LaTeX picture environment? As documented in Leslie Lamport's book, the largest circle that can normally be made is approxmately 1/2 inch in diameter. On my system I can generate a circle of about 14 mm in diameter, but that's the upper limit. Any suggestions would be appreciated. Thanks, Bill ------------------------------ Date: Thu, 04 Nov 1993 23:38:49 +0000 From: Manuel Carriba Subject: Re: Inserting graphics in LaTeX documents Heitor S. Lopes (heitor@gpeb.ufsc.br) writes: > Does anybody have some hint on how to insert in Latex documents, > graphic files in any well-known graphic format (e.g. .PCX, .GIF, etc...), > or from spreadsheet charts? I'm using PcTeX, running under DOS, and I noticed > that \special{... doesn't work at all. Switch to emTeX :-) It supports your desired graphic formats. Your nearest site is pip.shsu.edu:tex-archive/systems/msdos/emtex Manuel Carriba (M.Carriba@dcs.shef.ac.uk) ------------------------------ Date: Thu, 04 Nov 1993 18:21:49 -0500 From: Bill Denning Subject: DVIJEP -j option for VAX/VMS systems I'm doing some work in LaTeX using the picture environment, and I want to do it in landscape mode. PORTLAND.STY does the trick, and XDVI handles the output nicely for screen display. However, when I convert it to print on my HP LaserJet IIP using DVIJEP, all text wider than 7.50in gets truncated. I'm using the February, 1991 distribution of the DECUS TeX Collection for VAX/VMS systems. I looked around in [TEX_SOURCE.DVI], and found that Nelson Beebe mentions an update for DVIJEP in his message dated 26-May-1988, which is contained in the file 00MAIL.16. There is also a file called DVIJEP.LANDSCAPEMODS, which is a mail message from Julian Perry containing the source code modifications needed to implement the - -j option for DVIJEP. The -j option is used to convert .DVI files that are generated in landscape mode. Does anyone have an updated version of DVIJEP on a VAX/VMS system that allows the use of the -j option? I need either object or executable code, as I don't have a C compiler. An .EXE would need to be linked under VMS 5.4-2 or earlier. I do not have access to ftp. I believe that the VMSmail command SEND/FOREIGN would work if the sender is using a MIME compliant mailer. Several sources in DECUS have been unable to help with this request. Thanks in advance, Bill ------------------------------ Date: Thu, 04 Nov 1993 23:54:59 +0000 From: Manuel Carriba Subject: Searching for items in UK CTAN Dear all, I guess the UK node of the CTAN provides the facility to search for the location of some specific files, directories or both if you don't know exactly wehre they're placed in directory tree. Can someone tell me the commands or give a short explanation how I can do this? It should work similar to archie's query. Cheers, Manuel Carriba (M.Carriba@dcs.shef.ac.uk) ------------------------------ Date: Fri, 05 Nov 1993 10:53:13 +0000 From: Sebastian Rahtz Subject: Re: Searching for items in UK CTAN > I guess the UK node of the CTAN provides the facility to search for > the location of some specific files, directories or both if you don't > know exactly wehre they're placed in directory tree. > > Can someone tell me the commands or give a short explanation how if you use ftp, the command quote site index foo searches the file list for the word "foo". is that what you mean > I can do this? It should work similar to archie's query. "should" is a strong word. sebastian ------------------------------ Date: Wed, 10 Nov 1993 13:36:00 -0500 From: wwetmore@amweld.org (William Wetmore, amweld sysop) Subject: TeX I need to find out where to get TeX, which platforms it is available for, etc... Now that we are on the Internet it seems that our technical writers would like to use this system. Thanks in advance for any info you can share with me. - ---- William Wetmore American Welding Society, Miami, Florida amweld.org ------------------------------ Date: Wed, 10 Nov 1993 17:25:01 -0500 From: Steven "M." Christensen Subject: Solaris 2.X TeX etc. Do you know if TeX and its related programs have been ported to Sun Solaris 2.2 or better? Steve Christensen ------------------------------ Date: Fri, 03 Dec 1993 10:34:42 +0000 From: James Renshaw Subject: TeX converters to Braille? We have a blind student in our department who currently converts all his notes into Braille (including a lot of the mathematics). A number of my collegues use TeX/LaTeX and we would like to save him some time and effort by converting out lecture notes/tutorial sheets from TeX to Braille. I have come a cross a LaTeX file called braille.sty together with the relevant fonts which can output Braille as a sequence of dots but (1) it can't cope with mathematics and (2) we need some hardware to convert the dots to actual Braille. Does anybody have any suggestions as to how we might achieve this? Dr JH Renshaw | Tel : (0703) 593673 Faculty of Mathematical Studies | Fax : (0703) 593939 University of Southampton | E-mail : jhr@soton.ac.uk Southampton SO9 5NH, ENGLAND | or : jhr@maths.soton.ac.uk ------------------------------ Date: Thu, 09 Dec 1993 14:14:00 +0000 From: AMG0199@vax2.queens-belfast.ac.uk Subject: Invisible printing! I would like to set up an environment in LaTeX say \begin{invisible} ..... \end{invisible} such that all material contained within it is processed in the normal way in terms of spacing and paging but at the print out stage blank characters (invisible ink) are used. Presumably this will involve providing dummy pixel files. Any advice will be welcome. (This may seem like a strange specification -- it has to do with lecture notes being prepared with parts blanked out, later to be filled in by students!) Tom Patterson Department of Applied Mathematics & Theoretical Physics Queen's University of Belfast uk.ac.qub.v2 ------------------------------ Date: Fri, 12 Nov 1993 12:34:06 +0000 From: P.Taylor@rhbnc.ac.uk Subject: Report on the inaugural meeting of the NTS group, September 1993 Report on the Inaugural Meeting of the NTS Core Group: September, 1993. ========================================================================= This is a report on the inaugural meeting of the NTS (`New Typesetting System') project group, held during the autumn DANTE meeting at Kaiserslautern (Germany) on 23rd and 25th September, 1993. Present: Joachim Lammarsch (DANTE President, and instigator of the NTS project) ; Philip Taylor (Technical co-ordinator, NTS project); Marion Neubauer (minutes secretary); Prof. Dr. Peter Breitenlohner, Mariusz Olko, Bernd Raichle, Joachim Schrod, Friedhelm Sowa. Background: Although the NTS project has been in existence for approximately eighteen months, there has not previously been a face-to-face meeting of members of the core group; at the Spring meeting of DANTE Rainer Sch\"opf announced his resignation as technical co-ordinator, and Philip Taylor was invited by Rainer and Joachim to take over as co-ordinator, which he agreed to do. Joachim Lammarsch opened the Autumn meeting by reviewing the history of the project and the rationale which lay behind its creation; each member of the group then briefly reviewed his or her particular area of interest in the project, after which the group received an extended presentation from Joachim Schrod on one possible approach to the realisation of NTS. The members of the group were broadly in support of the approach outlined by Joachim Schrod, and it was \stress {agreed} that this should form the basis for discussions at the meeting. The approach proposed by Joachim may be summarised as follows: {\TeX} in its present form is not amenable to modification; the code, although highly structured in some ways, is also painfully monolithic in others, and any attempt to modify the present code in anything other than trivial ways is almost certainly doomed to failure. Accordingly, before attempting to modify {\TeX} in any way it is first necessary to re-implement it, the idea behind such re-implementation being to eliminate the interdependencies of the present version and to replace these with a truly modular structure, allowing various elements of the typesetting process to be easily modified or replaced. This re-implementation should be undertaken in a language suitable for rapid prototyping, such as the Common Lisp Object System (`CLOS'). The primary reason for the re-implementation is to provide modularisation with specified internal interfaces and therby provide a test bed, firstly to ensure that {\TeX} has been properly re-implemented and subsequently to allow the investigation of new typesetting paradigms. Once a working test bed has been created, and compatibility with existing {\TeX} demonstrated, a second re-implementation will be undertaken; this re-implementation will have the same modular structure as the test bed but will be implemented with efficiency rather than extensibility in mind, and will be undertaken using a combination of literate programming and a widespread language with a more traditional approach, such as `C++'. When this second version has also been demonstrated to be compatible with {\TeX}, it will be made available to implementors around the world, the idea being to encourage people to migrate to NTS by demonstrating its complete compatibility with {\TeX} (the test bed will also be made available if there is interest shewn in its use). Thereafter new ideas and proposals will be investigated using the test bed, and if found to be successful these will be re-implemented in the distribution version. The main problem which the group identified with the approach outlined by Joachim was simply one of resources: in order to accomplish two re-implementations within a reasonable time-scale, it would be essential to use paid labour, it being estimated that each re-implementation requires a minimum of four man-months work to produce a prototype, and eight man-months to reach the production stage. As this is far beyond the ability of members of the group to contribute in the short term, it is clearly necessary to employ a small team (of between two and four members) to carry out the re-implementations under the guidance and supervision of one or more members of the core group. Initial costings suggested that this could not be accomplished within the present financial resources of the group, and accordingly it was \stress {agreed} that Joachim Lammarsch should seek further financial support. Subsequent investigations shewed that a quite significant reduction in costs could be achieved if the programming team were sited in a central or eastern European country, particularly if the members of the team were also residents of the country; this approach is being investigated. As it was obvious that no immediate progress could be made with Joachim Schrod's proposal, even though the group agreed that it represented an excellent philosophical approach, it was also \stress {agreed} that the group needed to identify some fallback approaches, which could (a)~be commenced immediately, and (b)~would be of significant benefit to the {\TeX} community at large. The group identified two such projects, these being (1)~the specification of a canonical {\TeX} kit, and (2)~the implementation of an extended {\TeX} (to be known as e-{\TeX}) based on the present WEB implementation. It was also \stress {agreed} that Marek Ry\'cko \& Bogus{\l}aw Jackowski would be asked if they were willing to co-ordinate the first of these activities, and that Peter Breitenlohner would co-ordinate the second. The ideas behind the two proposals are as follows. (1)~The canonical {\TeX} kit: at the moment, the most that can be assumed of any site offering {\TeX} is (a)~ini{\TeX}; (b)~plain {\TeX}; (c)~{\LaTeX}; and (d)~at least sixteen Computer Modern fonts. Whilst these are adequate for a restricted range of purposes, it is highly desirable when transferring documents from another site to be able to assume the existence of a far wider range of utilities. For example, it may be necessary to rely on BibTeX, or on MakeIndex; it may be useful to be able to assume the existence of BM2FONT; and so on. Rather than simply say ``all of these can be found on the nearest CTAN archive'', it would be better if all implementations contained a standard subset of the available tools. It is therefore the aim of this project to identify what the elements of this subset should be, and then to liaise with developers and implementors to ensure that this subset is available for, and distributed with, each {\TeX} implementation. (2)~Extended {\TeX} (e-{\TeX}): whilst the test bed and production system approach is philosophically very sound, the reality at the moment is that the group lacks the resources to bring it to fruition. None the less, there are many areas in which a large group of existing {\TeX} users believe that improvements could be made within the philosophical constraints of the existing {\TeX} implementation. E-{\TeX} is an attempt to satisfy their needs which could be accomplished without a major investment of resources, and which can pursued without the need for additional paid labour. Finally the group agreed to individually undertake particular responsibilities; these are to be: Peter Breitenlohner: Remove any existing incompatibilities between {\TeX}--{\XeT} and {\TeX}, with the idea of basing further e-{\TeX} developments on {\TeX}--{\XeT}; liaise with Chris Thompson concerning portability of the code; produce a catalogue of proposed extensions to e-{\TeX}. Joachim Lammarsch: liaise with vendors and publishers in an attempt to raise money for the implementation of NTS proper; arrange a further meeting of interested parties; liaise with Eberhard Mattes concerning the present constraints on the unbundling of em{\TeX}; negotiate with leading academics concerning possible academic involvement in the project. Mariusz Olko: take responsibility for the multi-lingual aspects of e-{\TeX} and NTS; discuss the possibility of siting the NTS programming team in Poland; discuss the possibility of academic involvement with leading Polish academics. Bernd Raichle: endeavour to get {\TeX}--{\XeT} integrated into the standard UNIX distribution; prepare a list of proposed extensions to e-{\TeX}; lead discussions on NTS-L. Friedhelm Sowa: primary responsibility for finance; prepare proposals for a unified user interface and for unification of the integration of graphics; liaise with the Czech/Slovak groups concerning possible siting of the NTS programming team in the Czech Republic or Slovakia; discuss possible academic involvement with leading academics. Philip Taylor: Overall technical responsibility for all aspects of the project; liaise with other potential NTS core group members; prepare and circulate a summary of the decisions of this and future meetings. Philip Taylor, 09-NOV-1993 14:02:03 ------------------------------ Date: Wed, 24 Nov 1993 11:08:52 -0500 From: kb@cs.umb.edu Subject: modes.mf 1.1 available I have released version 1.1 of modes.mf. You can get it by anonymous ftp from ftp.cs.umb.edu:pub/tex/modes.mf You can also get it by email from George Greenwade's (thanks, George!) file server if you cannot ftp: email fileserv@shsu.edu with a body of `sendme modes'. This file is a collection of Metafont mode_def's. It also makes common definitions for write/white printers, `special' information, and landscape mode. The mode for the HP LaserJet 4 has completely new values, from mbr@research.nj.nec.com; his seemed better tested than previous. The IBM 4019 is now a separate mode from the IBM 4216. This version again runs through TeX. As always, thanks to the contributors. If you have mode_def's which are not listed below, or corrections to the existing ones, please send them to me. Improvements to the exposition, particularly in how to create a new mode_def, are also welcome. karl@cs.umb.edu mode_def AgfaFourZeroZero = % AGFA 400PS mode_def amiga = % Commodore Amiga mode_def AtariNineFive = % Atari 95dpi previewer mode_def AtariNineSix = % Atari 96x96 previewer mode_def AtariSLMEightZeroFour = % Atari ST SLM 804 printer mode_def AtariSMOneTwoFour = % Atari ST SM 124 screen mode_def aps = % Autologic APS-Micro5 mode_def ApsSixHi = % Autologic APS-Micro6 mode_def bitgraph = % BBN Bitgraph at 118dpi mode_def boise = % HP 2680A mode_def CanonCX = % Canon CX, SX, LBP-LX mode_def CanonEX = % CanonEX in LaserWriter Pro 630 mode_def CanonLBPTen = % e.g., Symbolics LGP-10 mode_def ChelgraphIBX = % Chelgraph IBX mode_def CItohThreeOneZero = % CItoh 310 mode_def CItohEightFiveOneZero = % CItoh 8510A mode_def CompugraphicEightSixZeroZero = % Compugraphic 8600 mode_def CompugraphicNineSixZeroZero = % Compugraphic 9600 mode_def crs = % Alphatype CRS mode_def DataDisc = % DataDisc mode_def DataDiscNew = % DataDisc with special aspect ratio mode_def DECsmall = % DEC 17-inch, 1024 x 768 mode_def DEClarge = % DEC 19-inch, 1280 x 1024 mode_def dover = % Xerox Dover mode_def epsdraft = % Epson at 120x72dpi mode_def epsfast = % Epson at 60x72dpi mode_def epsonlo = % Epson at 120x216dpi mode_def EpsonLQFiveZeroZeroMed = % Epson LQ-500, 360x180dpi mode_def EpsonLQFiveZeroZeroLo = % Epson LQ-500, 180x180dpi mode_def EpsonMXFX = % 9-pin Epson MX/FX family mode_def GThreefax = % 200 x 100dpi G3fax mode_def HPDeskJet = % HP DeskJet 500 mode_def HPLaserJetIIISi = % HP Laser Jet IIISi mode_def HPrugged = % HP RuggedWriter 480 mode_def ibm_a = % IBM 38xx (\#1) mode_def IBMD = % IBM 38xx (\#2) mode_def IBMFourZeroTwoNine = % IBM 4029-30, 4250 mode_def IBMFourTwoOneSix = % IBM 4216 mode_def IBMFourZeroOneNine = % IBM 4019 mode_def IBMProPrinter = % IBM ProPrinter mode_def IBMSixOneFiveFour = % IBM 6154 display mode_def IBMSixSixSevenZero = % IBM 6670 (Sherpa) mode_def IBMThreeOneSevenNine = % IBM 3179 screen mode_def IBMThreeOneNineThree = % IBM 3193 screen mode_def IBMThreeEightOneTwo = % IBM 3812 mode_def IBMThreeEightTwoZero = % IBM 3820 mode_def IBMEGA = % IBM EGA monitor mode_def IBMVGA = % IBM VGA monitor mode_def imagewriter = % Apple ImageWriter mode_def laserjetfour = % 600dpi HP LaserJet 4 mode_def laserjetlo = % HP LaserJet at 150dpi mode_def lasermaster = % 1000dpi LaserMaster mode_def LASevenFive = % DEC LA75 mode_def LinotypeOneZeroZeroLo = % Linotype Linotronic [13]00 at 635dpi mode_def LinotypeOneZeroZero = % Linotype Linotronic [13]00 at 1270dpi mode_def LinotypeThreeZeroZeroHi = % Linotype Linotronic 300 at 2540dpi mode_def LNZeroOne = % DEC LN01 mode_def LPSTwoZero = % DEC lps20 mode_def LPSFourZero = % DEC LPS40 mode_def lview = % Sigma L-View monitor mode_def MacMagnified = % Mac screens at magstep 1 mode_def MacTrueSize = % Mac screens at 72dpi mode_def NCD = % NCD 19-inch mode_def NEC = % NEC mode_def NEChi = % NEC-P6 at 360x360dpi mode_def Newgen = % Newgen 400dpi mode_def NeXTprinter = % NeXT 400dpi mode_def NeXTscreen = % 100dpi NeXT monitor mode_def nullmode = % TFM files only mode_def OCESixSevenFiveZeroPS = % OCE 6750-PS mode_def okidata = % Okidata mode_def OneTwoZero = % e.g., high-resolution Suns mode_def phaser = % Tektronix Phaser PXi mode_def PrintwareSevenTwoZeroIQ = % Printware 720IQ mode_def qms = % QMS (Xerox engine) mode_def QMSOneSevenTwoFive = % QMS 1725 mode_def QMSOneSevenZeroZero = % QMS 1700 mode_def RicohFourZeroEightZero = % e.g., TI Omnilaser mode_def RicohLP = % e.g., DEC LN03 mode_def SparcPrinter = % Sun SPARCprinter mode_def StarNLOneZero = % Star NL-10 mode_def sun = % Sun and BBN Bitgraph at 85dpi mode_def supre = % Ultre*setter at 2400dpi mode_def toshiba = % Toshiba 13XX, EpsonLQ mode_def ultre = % Ultre*setter at 1200dpi mode_def VarityperFiveZeroSixZeroW = % Varitype 5060W mode_def VarityperFourThreeZeroZeroLo = % Varityper 4300P at 1200dpi mode_def VarityperFourThreeZeroZeroHi = % Varityper 4300P at 2400dpi mode_def VarityperFourTwoZeroZero = % Varityper 4200 B-P mode_def VarityperSixZeroZero = % Varityper Laser 600 mode_def VAXstation = % VAXstation monitor mode_def XeroxDocutech = % Xerox 8790 or 4045 mode_def XeroxEightSevenNineZero = % Xerox 8790 or 4045 mode_def XeroxFourZeroFiveZero = % Xerox 4050/4075/4090 mode_def XeroxNineSevenZeroZero = % Xerox 9700 mode_def XeroxThreeSevenZeroZero = % Xerox 3700 ------------------------------ Date: 26 Nov 1993 16:31:59 +0100 From: gaulle@frors65.circe.fr (Bernard Gaulle) Subject: [comp.text.tex] announcing the French Style Files distribution V3,25 I'm pleased to announce the availability of the so called "French Style Files" distribution V3,25 on the French archives server of GUTenberg at ftp.univ-rennes1.fr in directory pub/GUTenberg/french I recall that this package is intended for people willing to deal with French documents or multi-lingual documents with TeX, LaTeX, etc... Below is the file giving the major changes since the last distributed version V3,20 in may, 1993. Enjoy, --bg % fichier Changements de la distribution << style french >> =============================================================================== Voici les principaux changements intervenus dans la distribution du style french V3,25 du 25 novembre 1993 par rapport a la V3.20 du 11 mai 1993 : A NOTER que presque tous les fichiers ont ete modifies. Il s'agit d'une version consolidee permettant l'utilisation du dispositif NFSS2 (New Font Selection Scheme version 2) qui sera introduit a peu pres sous sa forme actuelle dans LaTeX2e. La prochaine distribution des fichiers de francisation devrait etre relative a cette nouvelle version de LaTeX. Ameliorations apportees : - au niveau de la francisation : - un mot suivi d'une \footnote peut desormais etre divise en fin de ligne ; - lettrines produites de facon plus rigoureuse ; possibilite d'imposer le nombre de lignes ; - mise en page du style letter ; - ajout de \prefacename comme dans la distribution de Babel ; - traitement des guillemets modifie (pour laisser la possibilite a l'utilisateur de redefinir des macros ayant des noms composes des caracteres < ou >) ; - \begin{french} et \end{french} sont autorises avec LaTeX ; - prise en compte de NFSS2 et de son << Encoding Scheme >> ; - utilisation possible avec le moteur TeX--XeT ; - la << contribution >> allemande a ete remise a jour par son auteur, Marc Torzynski. Nouveaux outils proposes : - possibilite de preciser son clavier personnel (keyboard.dat) en le chargeant par \documentstyle[keyboard,...]{...} (ce dispositif est en beta-test) ; particulierement utile dans le cas d'installation multi-utilisateurs ou lorsque le << codepage >> est amene a etre change souvent. - mise en oeuvre de convertisseurs 7-bits <==> 8-bits a partir du fichier keyboard.dat personnel (un compilateur C est necessaire pour la generation de ces convertisseurs realises avec TeX et lex). Est particulierement utile pour l'envoi de documents ASCII 7-bits sur les reseaux. Corrections de bogues : - utilisation depuis plain TeX ; - < et > dans le mode mathematique d'AmSLaTeX ; - definition de \vert et de \bibcite etaient incorrectes ; - \c est corrige comme dans la distribution de MlTeX ; - elimination de blancs intempestifs a la suite de \endnonfrench et \endguillemets ; - \cite[X] n'imprimait pas X a la francaise ; - \wrongtypedspaces pouvait etre utilise par erreur en francais. Contournements : - de quelques problemes introduits par NFSS2 (\input non standard, messages contenant des caracteres non proteges) ; - de la methode utilisee dans seminar.sty (ou xcomment.sty) pour produire uniquement des transparents (option slidesonly) ; La conformite des fichiers de la distribution est maintenant assuree par la mise en place d'un << checksum >> qui a ete calcule par le programme (du domaine public) de Robert M. Soloway. Ce code est inscrit dans tous les fichiers ou cela s'est avere possible et utile. Vous pouvez donc verifier la validite de vos fichiers en leur appliquant ce programme (avec l'option -v). Vous devez obtenir le message : << The checksum verification of the input file was successful. >> Si vous obtenez le message : << The checksum verification of the input file did not succeed. >> alors cela signifie que vos fichiers ne sont pas d'origine. Des formulaires << d'installation correcte >> et << d'incidents >> sont fournis pour etre completes et renvoyes a l'adresse indiquee. Mes remerciements vont a tous ceux qui ont signale des problemes ou suggere des ameliorations. --bg ------------------------------ Date: 02 Dec 1993 17:37:06 +0100 From: geoff@ficus.cs.ucla.edu (Geoff Kuenning) Subject: [comp.text.tex] German dictionary available for ftp I have made a German dictionary for ispell available for ftp on ftp.cs.ucla.edu, in the directory pub/ispell/languages/deutsch. The dictionary was developed some time ago by Martin Schulz, who was unable to distribute it. He passed it on to me with a request that I make it available, and somehow I managed to lose track of his request. I am embarrassed about how long it took me to rediscover it, but "better late than never", so it's there for the taking. The files are gzipped except for README/LIESMICH, which I have left uncompressed so that you can easily view them. I suggest that you read one of these files before retrieving any others. - -- Geoff Kuenning geoff@maui.cs.ucla.edu geoff@ITcorp.com ------------------------------ Date: Tue, 07 Dec 1993 08:42:14 +0100 From: Nico Poppelier Subject: announcement Donald E. Knuth Scholarship At the 1993 TUG Annual Meeting the Board of Directors of the TeX Users Group (TUG) has decided that, starting with the 1994 Scholarship, the Donald E. Knuth Scholarship will be open to non-TUG members as well as to TUG members. The same rules for the Scholarship competition will apply, and the current committee will serve again for the 1994 Scholarship. Announcement of the next competition - ------------------------------------ One Knuth Scholarship will be available for award next year. The competition will be open to all TeX users holding support positions that are secretarial, clerical or editorial in nature. It is therefore not intended for those with a substantial training in technical, scientific or mathematical subjects and, in particular, it is not open to anyone holding, or studying for, a degree with a major or concentration in these areas. The award will consist of an expense-paid trip to the 1994 TUG Annual Meeting at Santa Barbara, USA, and to the Scholar's choice from the short courses offered in conjunction with that meeting, and TUG membership for 1993, if the Scholar is not a TUG member, or for 1994, if the Scholar is a TUG member. A cap of $2000 has been set for the award; however, this does not include the meeting or course registration fee, which will be waived. To enter the competition, applicants should submit to the Scholarship Committee, by the deadline specified below, the input file and final TeX output of a project that displays originality, knowledge of TeX, and good TeXnique. The project as submitted should be compact in size. If it involves a large document or a large number of documents then only a representative part should be submitted, together with a description of the whole project. For example, from a book just one or two chapters would be appropriate. The project may make use of a macro package, either a public one such as LaTeX or one that has been developed locally; such a macro package should be identified clearly. Such features as sophisticated use of math mode, of macros that require more than ``filling in the blanks'', or creation and use of new macros will be taken as illustrations of the applicant's knowledge. All macros created by the candidate should be well documented with clear descriptions of how they should be used and an indication of how they work internally. All associated style files, macro-package files, etc., should be supplied, or a clear indication given of any widely available ones used (including version numbers, dates, etc.); clear information should be provided concerning the version of TeX used and about any other software (e.g. particular printer drivers) required. Any nonstandard fonts should be identified and provided in the form of .tfm and .pk files suitable for use on a 300dpi laser printer. While the quality of the typographic design will not be an important criterion of the judges, candidates are advised to ensure that their printed output adheres to sound typographic standards; the reasons for any unusual typographic features should be clearly explained. All files and documents comprising the project must be submitted on paper; the input files should be provided in electronic form as well. Suitable electronic media are IBM PC-compatible or Macintosh diskettes, or a file sent by electronic mail. A brochure with additional information is available from the TUG office. To obtain a copy, or to request instructions on e-mail submission, write to the address at the end of this announcement, or send a message by e-mail to TUG@tug.org with the subject ``Knuth Scholarship request''. Along with the project, each applicant should submit a letter stating the following: 1. affirmation that he/she will be available to attend the 1994 TUG Annual Meeting; 2. affirmation of willingness to participate on the committee to select the next Scholar. Each applicant should also submit a `curriculum vitae' summarizing relevant personal information, including: 1. statement of job title, with a brief description of duties and responsibilities; 2. description of general post-secondary school education, TeX education, identifying courses attended, manuals studied, personal instruction from experienced TeX users, etc.; 3. description of TeX resources and support used by the candidate in the preparation of the project. Neither the project nor the `curriculum vitae' should contain the applicant's name or identify the applicant. These materials will be reviewed by the committee without knowledge of applicants' identities. If, despite these precautions, a candidate is identifiable to any judge, then that judge will be required to make this fact known to the others and to the TUG board members responsible for the conduct of the judging. The covering letter, `curriculum vitae', and all macro documentation that is part of the project input should be in English. (English is not required for the output of the project.) However, if English is not the applicant's native language, that will not influence the decision of the committee. Selection of the Scholarship recipient will be based on the project submitted. Schedule - -------- The following schedule will apply (all dates are in 1994): March 7 Deadline for receipt of submissions March 21--May 16 Judging period May 23 Notification of winner 31 July--4 August 1994 Annual Meeting, Santa Barbara, USA The 1994 Scholarship Committee consists of - - Chris Rowley, Open University, UK (Chair); - - David Salomon, California State University, Northridge, USA; - - Jenny Smith, Jon Wiley and Sons, Ltd. Chichester, UK. Where to write - -------------- All applications should be submitted to the Committee in care of the TUG office: TeX Users Group Attn: Knuth Scholarship Competition PO Box 869 Santa Barbara, CA 93102 USA email: TUG@tug.org Nico Poppelier Liaison to the 1993 Committee ------------------------------ 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. Please send contributions to: TeXhax@tex.ac.uk Administration, subscription and unsubscription requests: On Internet: send a one line mail message to TeXhax-request@tex.ac.uk SUBSCRIBE TEX-L UNSUBSCRIBE TEX-L On BITNET: send a similar one-line mail message to LISTSERV@xxx On JANET: send a similar one line mail message to TeXhax-request@uk.ac.tex For information on the TeX Users Group, please send a message to TUG@TUG.org, or write TeX Users Group, P.O. Box 869, Santa Barbara, CA 93102, USA. Back issues of the digest are available for anonymous ftp from the UK TeX Archive, tex.ac.uk (134.151.79.28) in [tex-archive.digests.texhax.YY]texhax.NN and ftp.tex.ac.uk (134.151.79.32) in /pub/archive/digests/texhax/YY/texhax.NN where YY = last two digits of year, NN = issue number ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX Archive Network, and may give better response for subscribers in the USA and Europe, respectively. \bye End of TeXhax Digest [Volume 93 Issue 16] ***************************************** From TeXhax-request@jess.ccc.nottingham.ac.uk Fri Dec 24 06:47:13 1993 Flags: 000000000001 Return-Path: Received: from jess.ccc.nottingham.ac.uk by math.utah.edu (4.1/SMI-4.1-utah-csc-server) id AA08187; Fri, 24 Dec 93 06:47:04 MST Errors-To: TeXhax-Request@ftp.tex.ac.uk Received: from ccsun5.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <27497-0@jess.ccc.nottingham.ac.uk>; Fri, 24 Dec 1993 10:33:44 +0000 From: TeXhax-Request@ftp.tex.ac.uk To: TeXhax Distribution:;@jess.ccc.nottingham.ac.uk Subject: TeXhax Digest V93 #017 Reply-To: TeXhax@ftp.tex.ac.uk Errors-To: TeXhax-Request@ftp.tex.ac.uk Distribution: world Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 24 Dec 1993 10:34:03 +0000 Message-Id: <862.756729243@unicorn.ccc.nottingham.ac.uk> Sender: cczdao@unicorn.ccc.nottingham.ac.uk TeXhax Digest Friday, 24 Dec 1993 Volume 93 : Issue 017 % The TeXhax Digest is brought to you as a service of the TeX Users Group % % and UK TeX Users Group in cooperation with the UK TeX Archive group % Today's Topics: TeXhax in 94 Re: Abbreviation marks for feet and inches RE: Abbreviation marks for feet and inches Word for Windows How to make Glossary during thesis writing LaTeX2e -- Preliminary Release Available Bachotek '94 Administrivia: Moderators: David Osborne and Peter Abbott Contributions: TeXhax@ftp.tex.ac.uk Administration, subscription and unsubscription requests: TeXhax-request@ftp.tex.ac.uk M O D E R A T O R ' S N O T E Please note the change of host in our mail addresses to ftp.tex.ac.uk instead of tex.ac.uk as the VAX system tex.ac.uk will soon be withdrawn. A Happy Christmas and Prosperous New Year to all our readers! ---------------------------------------------------------------------- Date: Fri, 24 Dec 1993 09:54:26 +0000 From: David Osborne Subject: TeXhax in 94 Dear reader, We're planning some changes to TeXhax in '94 to make it a more useful electronic publication for the TeX community. We have some ideas but we'd like your suggestions for what you'd like to see in it, and what you'd find interesting. Please spare a few minutes of your time to answer the following questions and help us make TeXhax the publication you want it to be. Send your replies to TeXhax-request@ftp.tex.ac.uk ****************** A. About TeXhax... 1. TeXhax has traditionally been a "question and answer" digest of mail messages. Do you like this format? YES / NO / NOT SURE 2. If you answered "NO" or "NOT SURE" above, are questions best answered in other places? YES / NO 3. Do you like to see announcements of new TeX software and services in TeXhax? YES / NO 4. Would you like to see regular topic "columns", as in a magazine? YES / NO 5. If you answered "YES", which of the following topics would you like to see covered: News from the Archives YES / NO Beginner's corner YES / NO Expert's corner YES / NO TUG News YES / NO Announcements of meetings YES / NO New publications YES / NO TeX book reviews YES / NO Other (please describe)... 6. TeXhax currently appears at 2-weekly to monthly intervals, depending on size of contents. Is this the right sort of frequency? YES / NO 7. If you answered "NO", how often would you like to see it appear? WEEKLY / EVERY TWO WEEKS / MONTHLY ****************** B. About you... 1. Are you a member of the TeX Users Group, or affiliated national or language user group? YES / NO 2. How do you currently receive TeXhax? a) Personally, via mail b) Read it in USENET newsgroup comp.text.tex c) Other MAIL / NEWS / OTHER 3. Do you also read other electronic TeX-oriented media? a) UKTeX YES / NO b) Other (please describe)... YES / NO 4. Do you think TeXhax overlaps with othe electronic TeX-oriented media? YES / NO 5. Do you have an Internet connection? YES / NO ****************** Thanks for your co-operation. David Osborne (TeXhax Digest moderator) on behalf of TUG Publications Committee ------------------------------ Date: Sat, 11 Dec 1993 19:49:17 +0000 From: KNAPPEN@VKPMZD.kph.uni-mainz.de Subject: Re: Abbreviation marks for feet and inches Here are feet and inches (or minutes and seconds) \def\feet{\'{}} \def\inches{\H{}} - --J"org Knappen. ------------------------------ Date: Tue, 14 Dec 1993 15:46:33 +0000 From: P.Taylor@rhbnc.ac.uk Subject: RE: Abbreviation marks for feet and inches >From time to time I need to write LaTeX documents that include measurements in >feet and inches. What I'm looking for is a method of using the ' and " marks >to abbreviate feet and inches. Maths mode is perfect: for example 1 foot four inches can be set as $1' 4''$ Philip Taylor, RHBNC. ------------------------------ Date: Tue, 14 Dec 1993 13:27:13 +0000 From: idb@cimio-limited.co.uk (Ian Bailey) Subject: Word for Windows I wonder if anyone might be able to help me. I have several word-for-windows documents which I must now submit for examination in LATEX format. Is there any software available to carry out the conversion from WfW v.2.0 to a generic LATEX structure ? If anyone has such a product for distribution (or for sale, if it is within the budget of a student), then could they please let me know. Ian Bailey idb@cimio.co.uk ------------------------------ Date: Tue, 21 Dec 1993 19:11:21 -0500 From: Ferose Lambay Subject: How to make Glossary during thesis writing Hello TeX-Hackers, I have quite got in a fix, I want to know how to make a glossary with the description of the items in it and placed at the end in an appendix. The LaTex book by Lamport only mentions the command \glossary to be used similar to \index, and says nothing how to use \description to describe the \item to be glossarized. So what I understood was only how to put \glossary next to the word to be put into the glossary, but nothing about how to use \description or which commands \makeglossary to be used whether in the TeX file or the document file Kindly help and quote an example for the usage of the commands to make a glossary with some text. Thanking you and wishing you all a Merry X'mas and a Happy New TeX year. Bye........ ferose A. University of Florida USA ------------------------------ Date: Tue, 21 Dec 1993 14:57:57 +0100 From: Schoepf@sc.zib-berlin.de Subject: LaTeX2e -- Preliminary Release Available It's not a bird, it's not plain, it's......... LaTeX2e -- Preliminary Release Available Leslie Lamport and the LaTeX3 project team 21 December 1993 The new release of LaTeX is now available for testing. LaTeX2e is the new standard version of LaTeX -- prepared and supported by the LaTeX3 project team. It is upwardly compatible with LaTeX 2.09 documents, but contains new features. Over the years many extensions of LaTeX have been developed. This is, of course, a welcome development, since it shows that the LaTeX system is in a healthy state. It has, however, had one unfortunate consequence: there are now several incompatible systems, in the sense of format (.fmt) files, all claiming to be LaTeX. Therefore, in order to process documents coming from various places, a site maintainer needs to provide several format files: LaTeX (with and without NFSS), SLiTeX, AmSLaTeX, and so on. In addition, when looking at a source file it is not always clear for which format the document was written. LaTeX2e puts an end to this unsatisfactory situation---it will give access to all such extensions based on a single format and thus end the proliferation of mutually incompatible dialects of LaTeX 2.09. It uses an enhanced version (NFSS2) of the New Font Selection Scheme. Files such as amstex.sty (formerly the AmSLaTeX format) or slides.sty (formerly the SLiTeX format) will become extension packages, all working with this single format. The introduction of this new version will also make it possible to add a small number of often-requested features (such as extended versions of \newcommand). To summarize: * Standardisation: a single format incorporating NFSS2, to replace the present multiplicity of incompatible formats (NFSS, lfonts, pslfonts, etc.) * Maintenance: a standardised system supported by a reliable maintenance policy. LaTeX2e adheres, as far as possible, to the following principles: * Unmodified version 2.09 document files can be processed with LaTeX2e. * All new features of LaTeX2e conform to the conventions of version 2.09, making it as easy as possible for current users to learn to use them. LaTeX2e is described in a new edition of `LaTeX: A Document Preparation System' by Leslie Lamport (to appear during 1994) and `The LaTeX Companion' by Goossens, Mittelbach and Samarin, both published by Addison-Wesley. LaTeX2e will be distributed twice a year. This distribution is a preliminary test release, and doesn't contain all of the files that will be part of the full release. In particular, it does not contain the planned extensions in the area of graphics inclusion. The first full release will be available in Spring 1994. This is a test release, so please get it and test it on as many different systems as possible! LaTeX2e can be retrieved by anonymous ftp from the CTAN archives: ftp.tex.ac.uk /tex-archive/macros/latex/distribs/latex2e-test ftp.shsu.edu /tex-archive/macros/latex/distribs/latex2e-test ftp.uni-stuttgart.de /tex-archive/macros/latex/distribs/latex2e-test Please report any problems with LaTeX2e by using the report-generating program latexbug.tex, included in the LaTeX2e distribution. Error reports can be sent to the following mail address: latex-bugs@rus.uni-stuttgart.de Note that no one on the programming team will be reachable until January 1994 (to give them a chance to see their families again). All mail sent to the above address will be answered then. Seasons greetings to you all! For the LaTeX3 Project Johannes Braams David Carlisle Alan Jeffrey Frank Mittelbach Chris Rowley Rainer Sch\"opf ------------------------------ Date: Tue, 21 Dec 1993 11:12:41 -0500 From: Wlodek Bzyl Subject: Bachotek '94 Dear David and Peter, We send you an official announcement of the 2nd GUST meeting, which will be held in the coming year. Merry Christmas and Happy New Year! - --W{\l}odek Bzyl - --Tomek Przechlewski (editors of the GUST bulletin) ***************************************************************** 2nd General Meeting of the Polish TeX Users Group (GUST) Bacho\TeX '94 2nd general meeting of GUST will be held in Bachotek (Brodnica Lake District) from 30.04 to 2.05 94. The deadline for submission of papers is March 1st 1994. A correspondence and papers should be directed to Hanna Ko{\l}odziejska, International Computers Ltd Poland, ul. Leszno 21, 01-199 Warszawa POLAND e-mail: hkolo@plearn.edu.pl ****************************************************************** ------------------------------ 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. Please send contributions to: TeXhax@ftp.tex.ac.uk Administration, subscription and unsubscription requests: On Internet: send a one line mail message to TeXhax-request@ftp.tex.ac.uk SUBSCRIBE TEX-L UNSUBSCRIBE TEX-L On BITNET: send a similar one-line mail message to LISTSERV@xxx On JANET: send a similar one line mail message to TeXhax-request@uk.ac.tex.ftp For information on the TeX Users Group, please send a message to TUG@TUG.org, or write TeX Users Group, P.O. Box 869, Santa Barbara, CA 93102, USA. Back issues of the digest are available for anonymous ftp from the UK TeX Archive, tex.ac.uk (134.151.79.28) in [tex-archive.digests.texhax.YY]texhax.NN and ftp.tex.ac.uk (134.151.79.32) in /pub/archive/digests/texhax/YY/texhax.NN where YY = last two digits of year, NN = issue number ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX Archive Network, and may give better response for subscribers in the USA and Europe, respectively. \bye End of TeXhax Digest [Volume 93 Issue 17] *****************************************