24-Feb-88 08:03:21-PST,29091;000000000000 From: The Mailer Daemon Message failed for the following: rjjt@Score.Stanford.EDU.#Internet: Can't forward - unknown host "oberon.sv.DG.COM" Subject: TeXhax Digest V88 #20 ------- 24-Feb-88 16:04:11-PST,29770;000000000000 Return-Path: Received: from decwrl.dec.com by SCORE.STANFORD.EDU with TCP; Wed 24 Feb 88 16:03:52-PST Received: from SCORE.STANFORD.EDU by decwrl.dec.com (5.54.4/4.7.34) id AA17774; Wed, 24 Feb 88 14:38:56 PST Date: Wed, 24 Feb 88 14:38:56 PST From: MAILER-DAEMON@decwrl.dec.com (Mail Delivery Subsystem) Subject: Returned mail: Host unknown Message-Id: <8802242238.AA17774@decwrl.dec.com> To: To: TeXhax-request@Score.Stanford.EDU ----- Transcript of session follows ----- mail11: partner exited, No such file or directory mail11: %MAIL-E-LOGLINK, error creating network link to node A1 mail11: -SYSTEM-F-NOSUCHNODE, remote node is unknown 550 ... Host unknown ----- Unsent message follows ----- Received: from SCORE.STANFORD.EDU by decwrl.dec.com (5.54.4/4.7.34) id AA17756; Wed, 24 Feb 88 14:38:56 PST Message-Id: <8802242238.AA17756@decwrl.dec.com> Date: Wed 24 Feb 88 07:42:50 PST Subject: TeXhax Digest V88 #20 From: TeXhax Digest Errors-To: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List:;@UNKNOWN Reply-To: TeXhax@Score.Stanford.edu TeXhax Digest Wednesday, February 24, 1988 Volume 88 : Issue 20 [SCORE.STANFORD.EDU]TEXHAX20.88 Editor: Malcolm Brown Today's Topics: End of TeXhax Digest ************************** ------- 25-Feb-88 01:41:49-PST,30837;000000000000 Return-Path: Received: from ames-io.ARPA (io.arc.nasa.gov.#Internet) by SCORE.STANFORD.EDU with TCP; Thu 25 Feb 88 01:41:36-PST Date: Thu, 25 Feb 88 01:21:21 PST From: Delivr@ames-io.ARPA Subject: Undeliverable Mail To: TeXhax-Request@Score.Stanford.EDU Comment: reason for return -- Addresses refused by VMS mail receiver Comment: the affected addresses follow ... Comment: <@ear:MCINNIS@EAR> Start of returned message Received: from Score.Stanford.EDU by ames-io.ARPA with INTERNET ; Wed, 24 Feb 88 13:31:20 PST Date: Wed 24 Feb 88 07:42:50 PST Subject: TeXhax Digest V88 #20 From: TeXhax Digest Errors-to: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List: ; Reply-to: TeXhax@Score.Stanford.edu TeXhax Digest Wednesday, February 24, 1988 Volume 88 : Issue 20 [SCORE.STANFORD.EDU]TEXHAX20.88 Editor: Malcolm Brown Today's Topics: End of TeXhax Digest ************************** ------- End of returned message 25-Feb-88 08:32:27-PST,23916;000000000000 Return-Path: <@RELAY.CS.NET:MAILER-DAEMON@sorak.kaist.ac.kr> Received: from RELAY.CS.NET by SCORE.STANFORD.EDU with TCP; Thu 25 Feb 88 08:31:56-PST Received: from relay2.cs.net by RELAY.CS.NET id ab24818; 25 Feb 88 11:10 EST Received: from sorak.kaist.ac.kr by RELAY.CS.NET id aa21592; 25 Feb 88 10:51 EST Received: by sorak.kaist.ac.kr (5.51/4.12) id AB04264; Thu, 25 Feb 88 19:23:38+0900 Date: Thu, 25 Feb 88 19:23:38+0900 From: Mail Delivery Subsystem Subject: Returned mail: Cannot send message for 1 week To: root%sorak.kaist.ac.kr@RELAY.CS.NET To: TeXhax-request@SCORE.STANFORD.EDU To: TeXhax-request@SCORE.STANFORD.EDU ----- Transcript of session follows ----- 421 ketri.etri.re.kr.ether... Deferred: Connection timed out during user open with ketri.etri.re.kr ----- Unsent message follows ----- Received: by sorak.kaist.ac.kr (5.51/4.12) id AA29931; Thu, 18 Feb 88 19:14:51+0900 Message-Id: <8802181014.AA29931@sorak.kaist.ac.kr> Received: from relay.cs.net by RELAY.CS.NET id aa11684; 17 Feb 88 19:32 EST Received: from score.stanford.edu by RELAY.CS.NET id aa29884; 17 Feb 88 19:08 EST Date: Wed 17 Feb 88 11:17:07 PST Subject: TeXhax Digest V88 #17 From: TeXhax Digest Errors-To: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List:; Reply-To: TeXhax@score.stanford.edu Received: from CSNet-Relay by kaist; 18 Feb 88 18:47:39-GMT+9:00 (Thu) TeXhax Digest Wednesday, February 17, 1988 Volume 88 : Issue 17 A [SCORE.STANFORD.EDU]TEXHAX17.88 Editor: Malcolm Brown Today's Topics: End of TeXhax Digest ************************** ------- 25-Feb-88 08:40:44-PST,30472;000000000000 Return-Path: Received: from uunet.UU.NET by SCORE.STANFORD.EDU with TCP; Thu 25 Feb 88 08:39:59-PST Received: from mcvax.UUCP by uunet.UU.NET (5.54/1.14) with UUCP id AA02722; Thu, 25 Feb 88 11:43:41 EST Received: by mcvax.cwi.nl; Thu, 25 Feb 88 17:05:23 +0100 (MET) Message-Id: <8802251605.AA14737@mcvax.cwi.nl> Received: from quantime.co.uk by kestrel.Ukc.AC.UK with UUCP id aa06031; 24 Feb 88 18:30 GMT From: Mail Delivery Subsystem Date: Wed, 24 Feb 88 18:05:05 GMT Subject: Returned mail: Unable to deliver mail To: texhax-request ----- Transcript of session follows ----- 554 mcvax!Score.Stanford.EDU!TeXhax-request... Unknown site . Check your mail address ----- Unsent message follows ----- Received: from mcvax by kestrel.Ukc.AC.UK with authorised UUCP id aa04786; 24 Feb 88 17:28 GMT Received: by mcvax.cwi.nl; Wed, 24 Feb 88 16:22:30 +0100 (MET) Received: from SCORE.STANFORD.EDU by uunet.UU.NET (5.54/1.14) id AA28530; Tue, 23 Feb 88 18:37:34 EST Message-Id: <8802232337.AA28530@uunet.UU.NET> Date: Tue 23 Feb 88 07:49:09 PST Subject: TeXhax Digest V88 #19 From: TeXhax Digest Errors-To: TeXhax-request%Score.Stanford.EDU@mcvax Maint-Path: TeXhax-request@Score.Stanford.EDU To: "Score.Stanford.EDU!TeXhax.Distribution.List":; Reply-To: TeXhax@score.stanford.edu TeXhax Digest Tuesday, February 23, 1988 Volume 88 : Issue 19 [SCORE.STANFORD.EDU]TEXHAX19.88 Editor: Malcolm Brown Today's Topics: End of TeXhax Digest ************************** ------- 26-Feb-88 08:13:12-PST,30008;000000000000 Date: Fri 26 Feb 88 08:10:24-PST From: The Mailer Daemon To: TeXhax-Request@Score.Stanford.EDU Subject: Message of 23-Feb-88 07:50:12 Message undeliverable and dequeued after 3 days: djones@rocky.Stanford.EDU.#Internet: Cannot connect to host pjs%grouch.span@vlsi.jpl.nasa.gov.#Internet: Cannot connect to host TRENFROW@vlsi.jpl.nasa.gov.#Internet: Cannot connect to host Bell%kuphsx.span@vlsi.jpl.nasa.gov.#Internet: Cannot connect to host percus@ACF4.NYU.EDU.#Internet: Cannot connect to host texhax@mahendo.jpl.nasa.gov.#Internet: Cannot connect to host texhax%use.uio.uninett@tor.NTA.NO.#Internet: Cannot connect to host unix-tex%vax.runit.unit.uninett@tor.NTA.NO.#Internet: Cannot connect to host ------------ Date: Tue 23 Feb 88 07:49:09 PST Subject: TeXhax Digest V88 #19 From: TeXhax Digest Errors-to: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List: ; Reply-to: TeXhax@Score.Stanford.edu TeXhax Digest Tuesday, February 23, 1988 Volume 88 : Issue 19 [SCORE.STANFORD.EDU]TEXHAX19.88 Editor: Malcolm Brown Today's Topics: End of TeXhax Digest ************************** ------- ------- 26-Feb-88 09:51:24-PST,30013;000000000000 Return-Path: Received: from uunet.UU.NET by SCORE.STANFORD.EDU with TCP; Fri 26 Feb 88 09:50:40-PST Received: from mcvax.UUCP by uunet.UU.NET (5.54/1.14) with UUCP id AA07467; Fri, 26 Feb 88 12:54:39 EST Received: by mcvax.cwi.nl; Fri, 26 Feb 88 18:15:46 +0100 (MET) Message-Id: <8802261715.AA26206@mcvax.cwi.nl> Received: from quantime.co.uk by kestrel.Ukc.AC.UK with UUCP id aa07190; 26 Feb 88 12:03 GMT From: Mail Delivery Subsystem Date: Fri, 26 Feb 88 06:08:27 GMT Subject: Returned mail: Unable to deliver mail To: texhax-request ----- Transcript of session follows ----- 554 mcvax!Score.Stanford.EDU!TeXhax-request... Unknown site . Check your mail address ----- Unsent message follows ----- Received: from mcvax by kestrel.Ukc.AC.UK with authorised UUCP id aa11820; 25 Feb 88 20:45 GMT Received: by mcvax.cwi.nl; Thu, 25 Feb 88 21:18:40 +0100 (MET) Received: from SCORE.STANFORD.EDU by uunet.UU.NET (5.54/1.14) id AA22652; Wed, 24 Feb 88 20:43:08 EST Message-Id: <8802250143.AA22652@uunet.UU.NET> Date: Wed 24 Feb 88 07:42:50 PST Subject: TeXhax Digest V88 #20 From: TeXhax Digest Errors-To: TeXhax-request%Score.Stanford.EDU@mcvax Maint-Path: TeXhax-request@Score.Stanford.EDU To: "Score.Stanford.EDU!TeXhax.Distribution.List":; Reply-To: TeXhax@score.stanford.edu TeXhax Digest Wednesday, February 24, 1988 Volume 88 : Issue 20 [SCORE.STANFORD.EDU]TEXHAX20.88 Editor: Malcolm Brown Today's Topics: End of TeXhax Digest ************************** ------- 25-Feb-88 21:47:36-PST,29942;000000000000 Return-Path: Received: from uunet.UU.NET by SCORE.STANFORD.EDU with TCP; Thu 25 Feb 88 21:47:16-PST Received: from mcvax.UUCP by uunet.UU.NET (5.54/1.14) with UUCP id AA19844; Fri, 26 Feb 88 00:51:13 EST From: mcvax!minster.york.ac.uk!postmaster@uunet.UU.NET Received: by mcvax.cwi.nl; Thu, 25 Feb 88 23:02:42 +0100 (MET) Received: from minster.york.ac.uk by kestrel.Ukc.AC.UK via Janet (UKC CAMEL FTP) id aa18613; 25 Feb 88 3:30 GMT Subject: mailer error report Date: 25 Feb 1988 02:44:37 GMT To: TeXhax Message-Id: Reason: local mail handler complained as follows jmail: hohn -- unknown user or mailbox -------- rejected letter --------- Via: 00000511168018/UCL-CS.FTP.MAIL ; 25 Feb 1988 02:44:07 GMT Received: from NSS.CS.UCL.AC.UK by NSS.Cs.Ucl.AC.UK via List-Channel id aa10639; 24 Feb 88 22:27 GMT Received: from score.stanford.edu by NSS.Cs.Ucl.AC.UK via Satnet with SMTP id aa10619; 24 Feb 88 22:23 GMT Date: Wed 24 Feb 88 07:42:50 PST Subject: TeXhax Digest V88 #20 From: TeXhax Digest Errors-to: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List: ; Reply-to: TeXhax@edu.stanford.score Sender: texhax-request@uk.ac.ucl.cs.nss TeXhax Digest Wednesday, February 24, 1988 Volume 88 : Issue 20 [SCORE.STANFORD.EDU]TEXHAX20.88 Editor: Malcolm Brown Today's Topics: End of TeXhax Digest ************************** ------- 24-Feb-88 12:33:20-PST,30404;000000000000 Return-Path: Received: from uunet.UU.NET by SCORE.STANFORD.EDU with TCP; Wed 24 Feb 88 12:32:34-PST Received: from mcvax.UUCP by uunet.UU.NET (5.54/1.14) with UUCP id AA04604; Wed, 24 Feb 88 15:36:21 EST From: mcvax!minster.york.ac.uk!postmaster@uunet.UU.NET Received: by mcvax.cwi.nl; Wed, 24 Feb 88 20:48:48 +0100 (MET) Received: from minster.york.ac.uk by kestrel.Ukc.AC.UK via Janet (UKC CAMEL FTP) id aa03710; 23 Feb 88 18:40 GMT Subject: mailer error report Date: 23 Feb 1988 18:38:18 GMT To: TeXhax Message-Id: Reason: local mail handler complained as follows jmail: hohn -- unknown user or mailbox -------- rejected letter --------- Via: 00000511168018/UCL-CS.FTP.MAIL ; 23 Feb 1988 18:37:48 GMT Received: from NSS.CS.UCL.AC.UK by NSS.Cs.Ucl.AC.UK via List-Channel id aa08800; 23 Feb 88 18:04 GMT Received: from score.stanford.edu by NSS.Cs.Ucl.AC.UK via Satnet with SMTP id aa08746; 23 Feb 88 17:59 GMT Date: Tue 23 Feb 88 07:49:09 PST Subject: TeXhax Digest V88 #19 From: TeXhax Digest Errors-to: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List: ; Reply-to: TeXhax@edu.stanford.score Sender: texhax-request@uk.ac.ucl.cs.nss TeXhax Digest Tuesday, February 23, 1988 Volume 88 : Issue 19 [SCORE.STANFORD.EDU]TEXHAX19.88 Editor: Malcolm Brown End of TeXhax Digest ************************** ------- 27-Feb-88 08:00:54-PST,29561;000000000000 Date: Sat 27 Feb 88 08:00:05-PST From: The Mailer Daemon To: TeXhax-Request@Score.Stanford.EDU Subject: Message of 24-Feb-88 07:44:41 Message undeliverable and dequeued after 3 days: djones@rocky.Stanford.EDU.#Internet: Cannot connect to host pjs%grouch.span@vlsi.jpl.nasa.gov.#Internet: Cannot connect to host TRENFROW@vlsi.jpl.nasa.gov.#Internet: Cannot connect to host Bell%kuphsx.span@vlsi.jpl.nasa.gov.#Internet: Cannot connect to host texhax@mahendo.jpl.nasa.gov.#Internet: Cannot connect to host texhax%use.uio.uninett@tor.NTA.NO.#Internet: Cannot connect to host unix-tex%vax.runit.unit.uninett@tor.NTA.NO.#Internet: Cannot connect to host tex-hackers@FCS280S.NCIFCRF.GOV.#Internet: Cannot connect to host ------------ Date: Wed 24 Feb 88 07:42:50 PST Subject: TeXhax Digest V88 #20 From: TeXhax Digest Errors-to: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List: ; Reply-to: TeXhax@Score.Stanford.edu TeXhax Digest Wednesday, February 24, 1988 Volume 88 : Issue 20 [SCORE.STANFORD.EDU]TEXHAX20.88 Editor: Malcolm Brown End of TeXhax Digest ************************** ------- 29-Feb-88 10:52:17-PST,27010;000000000000 Return-Path: <@RELAY.CS.NET:MAILER-DAEMON@sorak.kaist.ac.kr> Received: from RELAY.CS.NET by SCORE.STANFORD.EDU with TCP; Mon 29 Feb 88 10:51:24-PST Received: from relay2.cs.net by RELAY.CS.NET id aa19164; 29 Feb 88 11:15 EST Received: from sorak.kaist.ac.kr by RELAY.CS.NET id ab01189; 29 Feb 88 10:52 EST Received: by sorak.kaist.ac.kr (5.51/4.12) id AA00102; Mon, 29 Feb 88 18:21:44+0900 Date: Mon, 29 Feb 88 18:21:44+0900 From: Mail Delivery Subsystem Subject: Returned mail: Cannot send message for 1 week To: root%sorak.kaist.ac.kr@RELAY.CS.NET To: TeXhax-request@SCORE.STANFORD.EDU ----- Transcript of session follows ----- 421 ketri.etri.re.kr.ether... Deferred: Connection timed out during user open with ketri.etri.re.kr ----- Unsent message follows ----- Received: by sorak.kaist.ac.kr (5.51/4.12) id AA12292; Mon, 22 Feb 88 17:51:52+0900 Message-Id: <8802220851.AA12292@sorak.kaist.ac.kr> Received: from relay.cs.net by RELAY.CS.NET id aa06352; 21 Feb 88 19:33 EST Received: from score.stanford.edu by RELAY.CS.NET id aa03258; 21 Feb 88 19:07 EST Date: Sun 21 Feb 88 13:03:57 PST Subject: TeXhax Digest V88 #18 From: TeXhax Digest Errors-To: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List:; Reply-To: TeXhax@score.stanford.edu Received: from CSNet-Relay by kaist; 22 Feb 88 17:15:38-GMT+9:00 (Mon) TeXhax Digest Sunday, February 21, 1988 Volume 88 : Issue 18 [SCORE.STANFORD.EDU]TEXHAX18.88 Editor: Malcolm Brown Today's Topics: Immoderate notes: brief pause in texhax; issue 17 sliced up LaTeX Notes (Re: TeXhax Digest V88 #15) clatex vs. latex a plea for sanity Something similar to the dangerous bend Problems with VMS version of MetaFont 2 C compilations of TeX various UNIX TeX distribution two line footers? transferring dvi files across systems \unhbox and discretionary breaks Does anyone have a good LN03 mode definition? new .bst files in LaTeX style collection TeXhax Digest V88 #16 Re: \dotfill in \halign \dotfill again Bibtex change files for UNIX (VAX,SUN) Setting undertildes more on extensions Public Domain Previewer wanted/and a puzzle LaTeX Notes (Re: TeXhax Digest V88 #17) ---------------------------------------------------------------------- Date: 21 Feb 88 From: Malcolm Subject: Immoderate notes: brief pause in texhax; issue 17 sliced up %%% Please note I'll be away from Feb 25 to Mar 4 inclusive. I recommend %%% that you hold your submissions until I get back; they'll just get %%% stale and moldy on Score. Needless to say, there won't be any TeXhax %%% during that time. %%% %%% Issue 17 was sliced in half by some unkind IBM systems using SMTP. Glenn %%% Vanderburg informs me that the reason was a line that was longer than %%% 80 columns got wrapped, which resulted in the next line beginning with %%% a period. SMTP though that this meant it was about to get a command. So %%% it went through the remainder of the digest, looking for a command, which %%% of course it didn't find -- only more TeXhax. %%% %%% Please do NOT write to texhax-request for a reissue; sorry, I just won't %%% have time. TEX-L has a complete copy and will be happy to provide you %%% with a new copy. Malcolm ------------------------------ Date: Mon, 15 Feb 88 15:51:56 pst From: lamport@src.dec.com (Leslie Lamport) Subject: LaTeX Notes (Re: TeXhax Digest V88 #15) Dimitri Vulis writes: I tried to use a crazy Hungarian name in tabbing environment in LaTeX: \> \> blah blah blah M\'at\'e blah For some reason LaTeX moved the 'at' and 'e blah' to the beginning of the line! The subject line of his message was: Accents in tabbing environment in LaTeX On page 211 of the LaTeX manual is an index entry that reads accents, 40 ... in tabbing environment, 181 This would seem to suggest that page 181 just might contain the solution to his problem. Leslie Lamport ------------------------------ Subject: clatex vs. latex Date: Mon, 15 Feb 88 17:09:36 PST From: Richard Roy I preliminary comparison of clatex, a C-version of latex generated using TeX-to-C on tex.web.2.9 and all the latest macros as of 22 Jan 88, and the corresponding pascal compiled web-code, on a SUN3-110 with 16Mbytes shows clatex to be approx. 30%-50% faster (depending on you you score it). clatex - 53.7u 1.6s 1:15 73% 80+240k 5+13io 62pf+0w latex - 60.9u 2.6s 1:25 74% 96+376k 15+18io 105pf+0w RR ------------------------------ Subject: a plea for sanity Date: Tue, 16 Feb 88 01:36:38 -0500 From: Ken Yap Whatever happened to the effort to standardize on one dvi2ps filter last year? I see a half a dozen drivers out there all derived from the original dvi2ps, all with some subset of desirable features. Is there any hope of standardization? Would it be possible for each author to compare his/her driver against the others and send the improvements to one person who would put it all in one super driver? And then defer in favour of that super driver when it appears? Here's hoping. Here is a list of what I consider desirable features in roughly descending order (mine). Please throw in more comment on this mailing list. Tpic support Landscape support Horizontal and vertical offsets PostScript file inclusion Access to PostScript fonts Inline PostScript* Compact PostScript output Fast PostScript output Support for any resolution Customizable font paths Font substitution Forward/reverse printing Logging Debug output *There are many bells and whistles that could be added here but I think a driver that generates markers at various points in the output will make it possible for post-filters to inject almost any PostScript code. This can take care of many disparate features, like a draft header, two-up, manualfeed, etc. (Such post-filters are useful for other PostScript output, like that generated by enscript, a ASCII to PostScript filter). Ken ken@cs.rochester.edu ------------------------------ Date: Mon, 15 Feb 88 10:49:57 -0100 From: mcvax!ruuinf!piet@uunet.UU.NET (Piet van Oostrum) Subject: Something similar to the dangerous bend I believe the 'dangerous bend' sign was designed to stick below the baseline. You have to check the Metafont Book (somebody borrowed mine). So you have to lower the box. See also some previous tex-haxes (and TUGBOAT). ------------------------------ Date: Tue, 16 Feb 88 08:11:54 PST From: KARNEY%PPC.MFENET@NMFECC.ARPA Subject: Problems with VMS version of MetaFont You can get rid of the warning message about the non-initialization of ready_already by including @x @!ready_already:integer; {a sacrifice of purity for economy} @y @!ready_already:[static]integer:=0; {a sacrifice of purity for economy} @z in your change file. A previous version of the Pascal compiler had a bug which also necessitates making a couple of variables static. The required change is @x @!smooth_bot,@!smooth_top:0..move_size; {boundaries of smoothing} @y @!smooth_bot,@!smooth_top:[static] 0..move_size; {boundaries of smoothing} @z The current version of the compiler (version 3.6) doesn't need this change. Charles Karney Plasma Physics Laboratory Phone: +1 609 243 2607 Princeton University MFEnet: Karney@PPC.MFEnet PO Box 451 ARPAnet: Karney%PPC.MFEnet@NMFECC.ARPA Princeton, NJ 08543-0451 Bitnet: Karney%PPC.MFEnet@ANLVMS.Bitnet CC: PADWA@HUSC3.BITNET TeXhax@Score.Stanford.EDU KARNEY ------------------------------ Date: Tue, 16 Feb 88 08:40:54 PST From: mackay@june.cs.washington.edu (Pierre MacKay) Subject: 2 C compilations of TeX In a recent communication to TeXhax, Common TeX was declared a clear winner against TeX-to-C on the grounds of a marginally faster processing of a test file (we may disregard the third-place pascal compilation.) It seemed that there could be a question of whether the playing field was absolutely level but, assuming that it was, there are still reasons to view the verdict rather carefully. Common TeX is a carefully hand-coded rewrite of the pascal part of Donald Knuth's WEB code, and in the course of that rewrite has drifted a fair distance from the WEB. TeX-to-C is directly interpreted by way of the pascal brick (does anyone know who first used that description of tangle output?) and retains a recognizeable kinship with the original source. In addition, TeX-to-C retains the string pool, and TeX-to-C is showing that it can pass trip on an ever wider variety of systems. None of these details is trivial. 1. Association with the WEB. During the past week, I spent a maximum of 6 hours, most of it on the text-editor, in the creation of a Cxet.ch change file for the compilation of TeX-XeT through TeX-to-C. Throughout this effort I had *Computers and Typesetting* Volume B, open as a reference. and could work through the modules sequentially. (I was, in essence, merging the system-independent part of Don Knuth's WAITS change file with the Ctex.ch file). I do not wish to think about how long it would take to recode without the benefit of Tim Morgan's interpreter. TeX-XeT is not alone among extended versions of TeX. JTeX (Japanese) is put together through the mechanism of the change file, Michael Ferguson's multi-lingual TeX is probably done the same way, as is the Finnish accent-stripping TeX and at least one commercial multilingual TeX. Users of the change-file mechanism can contemplate the rush of small improvements from Version 2.1 through 2.9 with no particular uneasiness, the more so since recompilation under TeX-to-C is substantially faster than monolithic pascal compilations. 2. The string pool. The is the most underrated part of the whole WEB system. Don Knuth introduces the string pool mechanism [4.38] as merely a way to avoid the deficiencies in string handling in pascal, but it could be argued any large software system ought to adopt it. The advantages of having all possible messages located in a file separate from the the rest of the code can easily be seen. In a monolingual environment, it allows for detailed editing of the messages without recompilation, and in a multi-lingual environment, it is an absolute virtue. Editing a string pool isn't the easiest thing in the world (you have to watch out for terminal spaces in the character count), but it is a lot easier than editing an entire source file. 3. The trip test. I do not know what the present status of Common TeX is with regard to the trip test. In the last version I saw, the rewording of a considerable number of messages made it very difficult to sift out significant from insignificant differences, and gave evidence that some operations were done in a different order in Common TeX from the order given in the WEB source. The copy of version 2.1 I got never completed the test. TeX-to-C completes the test with ease. In every compilation in which I have got a working initex at all, the associated triptex passes the trip test. 4. Speed. I suspect that Common TeX will always have a fine edge here, and one of the reasons is the use of the string pool. TeX-to-C is still being adjusted and refined, and will probably close up the small gap somewhat, but it is likely that hand-coded efficiencies will always be a bit better than machine coded efficiencies. To get that edge, you have to give up the close filiation from the WEB sources, and from the WEB listing, and the string pool mechanism. In most environments, I would argue that those features are more valuable than raw speed. Pierre A. MacKay TUG Site Coordinator for Unix-flavored TeX ------------------------------ Date: Tue, 16 Feb 88 17:43:57 GMT From: Dr R M Damerell (RHBNC) Subject: various 1. Pretty-printing TANGLE's output. (A.Woo, Texhax 88/11). I think the official line is that you are not allowed to want to do this, you should Weave it instead. I am currently working on a sort of PP; it will run on VMS (I hope) in about 3 months. One simple thing you could do right now is alter TANGLE to break lines after every semicolon. I know that isnt anywhere near "pretty", but might do what you need. 2. Dotfill. (P. Flynn, TEXHAX 88/12). Please may I suggest the WEBMAC.TEX macros? I think the one you seem to need is \Z , nearly at the end of the file. 3. Bug sanctuary. A mistake I find myself making with distressing frequency is that of inadvertently using a global variable locally in a procedure. Please does anybody know of a cross-referencer that can be made to flag all uses of global variables inside a PASCAL procedure? The VMS cross-ref flags all uses of all variables; thats not really useful as the signal- to-noise ratio is so poor. 4. Another sanctuary. This is prompted by J.Leichter (Texhax 88/05) who found un-initialised variables in PXtoPK. Every VMS Change file I have seen for TEX-related software initialises the XORD array incorrectly. This has 256 elements and only the first 128 get values. 5. Converting DVI files (CCZDAO, Texhax 88.14) Converting binary files to another machine's system is a dreadfully difficult job, not worth trying unless you are compelled. It will almost certainly be far easier to re-run the TeX source. If you cant, there are 3 utilities that might help you find what is wrong 1. DVITYPE 2. $DIRECTORY/FULL 3. $DUMP Reading DUMP files is somewhat of a black art. By default each line of output contains 4 or 8 blocks of hex digits. These must be read right to left, but within each block the digits must be read left to right. I think this is because VMS packs bytes into a word in Small-End order(least significant first) and DVI files use Big-End order. Also: variable-length records are preceded by a byte count & depending on the qualifiers, DUMP ***sometimes*** shows them. I suggest that you examine the last block of the file to see if it is correctly padded. (? cant remember, but I think it should be filled with HEX DF ) Good luck, you'll need it, Mark ------------------------------ Date: Tue, 16 Feb 88 09:57:31 PST From: Phil Farrell Subject: UNIX TeX distribution Here is a simple question from a new reader ... Whom do I contact to order a tape with the complete UNIX TeX distribution (for a Vax running 4.3BSD UNIX)? ------------------------------ From: Tim Finin Date: Tue, 16 Feb 88 16:07:57 EST Subject: two line footers? I have a problem that someone suggested I send to this mailing list. I'm writing a document using LaTeX and need to have non-standard headers and footers. In particular, every page needs a constant, centered string as the header and a two line footer. The footer should be composed of a centered page number on the first line and a centered constant string on the second. I've had no luck in mixing in TeX commands to do this in the context of LaTex. Any suggestions? Tim ------------------------------ Date: Tue 16 Feb 88 14:49:41-PST From: Barbara Beeton Subject: transferring dvi files across systems at the american math society, we've had some experience transferring dvi files (and other binaries -- .tfm, etc.) from "other" systems (tops-20, ibm pc) to the vax/vms. we have found it necessary to pad the files to a multiple of 512 bytes; the padding character is octal 337. -- barbara beeton ------------------------------ Date: Tue, 16 Feb 1988 17:57 EST From: Jim Walker Subject: \unhbox and discretionary breaks As far as I can tell by experimentation, in text produced by \unhbox, explicit hyphens are never recognized as locations of discretionary breakpoints. Why is this? Is it considered a bug? -- Jim Walker, University of South Carolina ------------------------------ Date: Tue, 16 Feb 88 21:33:15 PST From: robinson%SOE.Berkeley.EDU@jade.berkeley.edu (Michael Robinson) Subject: Does anyone have a good LN03 mode definition? I need to make a set of fonts for our LN03, and I would like to use a tried and true mode definition. Can anyone help me out? -Michael Michael Robinson USENET: ucbvax!dewey.soe.berkeley.edu!robinson ARPA: robinson@dewey.soe.berkeley.edu ------------------------------ Subject: new .bst files in LaTeX style collection Date: Wed, 17 Feb 88 10:41:32 -0500 From: Ken Yap WARNING WARNING WARNING To: latex-style subscribers The files acm.bst, ieeetr.bst, siam.bst and apalike.bst are updated versions that require BibTeX 0.99b to work. Ken PS: I'm expecting more new style files soon so I'll post a full update shortly. Remember you can always fetch 00index and 00directory to see the current state of things. ------------------------------ Date: Wed, 17 Feb 88 07:53:31 PST From: mackay@june.cs.washington.edu (Pierre MacKay) Subject: TeXhax Digest V88 #16 bibtex.BSD4_n.ch is available on june.cs.washington.edu, in ~ftp/pub You may have to adjust the alpha character in the version number, depending on which new bibtex you got. (The newest is 99c) Pierre A. MacKay TUG Site Coordinator for Unix-flavored TeX ------------------------------ From: Julian Bradfield Date: Wed, 17 Feb 88 16:01:01 GMT Subject: Re: \dotfill in \halign [ Reprise: the problem was to produce a table of the form Title 1 ......................................................... Author 1 second title .................................................... second Author third ........................................................... and last ] The idea for the following solution is due to Duncan Baillie (dmb@lfcs.ed.ac.uk) : \halign to \hsize {#\dotfill\tabskip=0pt plus1fill&#\tabskip=0pt&#\hfil\cr \cr\noalign{\vskip-\baselineskip} Title 1\span& Author 1\cr second title\span& second Author\cr third\span& and last\cr} \bye ------------------------------ Mail-From: BEETON created at 17-Feb-88 09:02:57 Date: Wed 17 Feb 88 09:02:57-PST From: Barbara Beeton Subject: \dotfill again i recommend a look at the texbook, appendix d, pp. 392-394. this technique handles multi-line entries automatically. much more powerful than \halign, and it gives you better control over baselines. -- barbara beeton ------------------------------ Subject: Bibtex change files for UNIX (VAX,SUN) Date: Wed, 17 Feb 88 09:22:37 PST From: Richard Roy I got one just a few days ago from june.cs.washington.edu (P. Mackay) and it worked on bibtex.web 0.99c which I got from score the same day. It compiled and ran on my SUN-3 110 OS3.4 no problem. Note that the style files on rochester are inconsistent. Some are for the NEW bibtex, others for the OLD bibtex 0.98i and earlier. THEY ARE NOT COMPATIBLE!!! I have mentioned this to O. Patashnik and K. Yap and the current thought is to put a note to this effect in the 00index and 00readme files in public/latex-style on cayuga.cs.rochester.edu. RR ------------------------------ Date: Wed, 17 Feb 88 14:18:28 EST From: "Doug Arnold" Subject: Setting undertildes Mike Meyer (mikem@andrew.cmu.edu) asks about setting undertildes. I make frequent use of undertildes (or undertwiddles, or, as one journal editor termed them "inferior waves") as well double undertildes. Many of my papers start with a bunch of macros setting them up. I've done them in plain TeX (using macros like "\def\ut#1{\rlap{${}_{_{\sim}}$}{#1}}"), but I much prefer the results using AMSTeX's \underset. Here is an example: \input amstex \def\ut#1{\underset\sim\to{\botsmash{#1}}} \def\utt{\underset\sim\to} % \operatorname doesn't like \botsmash \def\dut#1{\underset\approx\to{\botsmash{#1}}} \def\grad{\operatorname{g\utt{ra}d}} \def\curl{\operatorname{\utt{curl}}} \def\div{\operatorname{div}} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \document $$ \div \ut\psi = \psi_{1,1} + \psi_{2,2}, \qquad \curl r = \dut\chi \grad r, \qquad \dut\chi = \pmatrix 0 & -1 \\ 1 & \phantom{-} 0 \endpmatrix $$ \bye -- Doug Arnold dna@emmy.umd.edu dna%emmy.umd.edu@eneevax.umd.edu na.arnold@score.stanford.edu ------------------------------ Date: Wed, 17 Feb 88 14:01:10 EST From: "Karl Berry." Subject: more on extensions Changing TeX will allow, say, `latex paper', without any paper. As things stand now, nothing should prevent you from being Consistently throughout TeX (and Metafont) the extension is `.tex' is never insisted on; if you supply an extension, that one will be used. So, if you want to a different extension on your LaTeX files, fine. Just type in the extension you want. Four extra characters. Taking the default extension from a parameter, as William LeFebvre suggests, is probably the best idea of all. Maybe in TeX92. Karl. karl@umb.edu able to type `latex paper.ltx', or whatever you like. ------------------------------ Date: Wed, 17 Feb 88 18:21:47 EST From: Ajit Ranade Subject: Public Domain Previewer wanted/and a puzzle Where can I find a public domain previewer for PC-TeX on my IBM PS/2? I am using ver 1.5 with pixel files 1200 thru 2488 (ie dpi 240 to 570(?)). I am at a Bitnet site, so no easy FTP possible. %%%%%%%%%% And now the puzzle (whose answer I don't know)- Without using Metafont, how does one generate the symbol which looks like \succsim (of AMSTeX) except that the \sim part of the symbol should be inclined diagonally upwards i.e. \succ shouldn't sit \atop on \sim. Same applies to \ge where the horizontal part under > (greater than) shouldn't be \atop 'ed but sloping upwards i.e. parallel to the lower segment of >. ------------------------------ Date: Wed, 17 Feb 88 17:44:08 pst From: lamport@src.dec.com (Leslie Lamport) Subject: LaTeX Notes (Re: TeXhax Digest V88 #17) This is in response to Julian Bradfield's "(Flame)", which I won't quote in full. On the matter of nonindented first paragraphs, he writes I should be obliged if he would explain it, instead of preaching from on high I'm sorry if I've given the impression of "preaching from on high"; the only knowledge I will claim to have is of my own ignorance on the subject--which seems to be a greater claim than can; be made by many TeXHaXers. I have refrained from trying to explain document-style decisions because I don't feel qualified to do so. However, this question has arisen so often, that I will give what I think are the reasons for the convention. I do this reluctantly, knowing that a competent designer might find my comments naive and all wrong. Anyway, one first must understand the purpose of paragraph indentation, which is to inform the reader of the beginning of a new paragraph. Since the reader is already informed of this by the section heading, indenting the opening paragraph is redundant. Why is it bad? My belief is that the function of the heading is to introduce the following text. To emphasize this function, the design should visualy tie the heading to the following text and separate it from the preceding text. That's why one usually finds more space above the heading than after it. (A typical mistake made by computer hackers is to make the two spaces the same.) If the section heading is flush left, as in the LaTeX styles, it is more strongly tied visually to the following paragraph if there is no paragraph indentation. Dr Lamport is that he seems always to assume that those who disagree with him are wrong, ignorant and stupid I can't recall anyone disagreeing with me in TeXHaX. Many people don't like the way LaTeX does some things, which I don't regard as disagreeing with me. There are lots of things LaTeX does that I don't like. Anyone seeking perfection had better not try writing TeX macros. I find questions of right and wrong to be irrelevant in this context, I try to ignore stupidity (I've found little of it in TeXHaX), and I try to correct ignorance when I can. I would ask Dr Lamport to be less abrasive in his public utterances There are many things I would rather be doing than answering queries about LaTeX. I wrote LaTeX in my spare time because I wanted a set of TeX macros for my own use and decided to put in a little (hah!) extra effort so others could use them. I haven't yet taken Knuth's step of refusing to discuss LaTeX at all, though that is very tempting. Instead, I try to respond to all queries, and even to answer some flames. However, I do try to respond as quickly as I can. I appologize if my responses are abrasive, but I hope that an abrasive response is preferable to none. extreme ugliness is a sufficient condition for unreadability I have yet to see any evidence that a document is harder to read because it is ugly rather than because it violates principles of good design. I have, however, seen a number of cases in which documents were made harder to read by being made more beautiful. (See my AMS article reprinted in TUGboat for one example.) Leslie Lamport ------------------------------ %%% %%% subscriptions, address changes to: texhax-request@score.stanford.edu %%% please send a valid arpanet address!! %%% %%% BITNET distribution: subscribe by sending the following %%% line to LISTSERV@TAMVM1.BITNET: %%% SUBSCRIBE TEX-L %%% %%% submissions to: texhax@score.stanford.edu %%% %%%\bye %%% ------------------------------ End of TeXhax Digest ************************** ------- 1-Mar-88 04:41:29-PST,1499;000000000001 Return-Path: Received: from RELAY.CS.NET by SCORE.STANFORD.EDU with TCP; Tue 1 Mar 88 04:41:25-PST Received: from relay2.cs.net by RELAY.CS.NET id ac04090; 1 Mar 88 7:08 EST Date: Tue, 1 Mar 88 6:58:06 EST From: RELAY Mail System (MMDF) Sender: mmdf@RELAY.CS.NET Subject: Failed mail (msg.ar10319) To: @RELAY.CS.NET:TeXhax-Request@SCORE.STANFORD.EDU After 7 days (155 hours), your message could not be fully delivered. It failed to be received by the following address(es): @math.waterloo.edu:shirley@watdcsu.waterloo.edu (host: math.waterloo.edu) (queue: waterloo) ML_texhax@math.waterloo.edu (host: math.waterloo.edu) (queue: waterloo) Problems usually are due to service interruptions at the receiving machine. Less often, they are caused by the communication system. Your message begins as follows: Received: from relay.cs.net by RELAY.CS.NET id ar10319; 23 Feb 88 19:04 EST Received: from score.stanford.edu by RELAY.CS.NET id aa18193; 23 Feb 88 18:20 EST Date: Tue 23 Feb 88 07:49:09 PST Subject: TeXhax Digest V88 #19 From: TeXhax Digest Errors-to: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List: ; Reply-to: TeXhax@SCORE.STANFORD.EDU TeXhax Digest Tuesday, February 23, 1988 Volume 88 : Issue 19 [SCORE.STANFORD.EDU]TEXHAX19.88 ... 2-Mar-88 02:37:49-PST,30413;000000000000 Return-Path: <@RELAY.CS.NET:MAILER-DAEMON@sorak.kaist.ac.kr> Received: from RELAY.CS.NET by SCORE.STANFORD.EDU with TCP; Wed 2 Mar 88 02:36:52-PST Received: from relay2.cs.net by RELAY.CS.NET id aa10153; 2 Mar 88 5:38 EST Received: from sorak.kaist.ac.kr by RELAY.CS.NET id ac05247; 2 Mar 88 5:20 EST Received: by sorak.kaist.ac.kr (5.51/4.12) id AA29917; Wed, 2 Mar 88 17:31:29+0900 Date: Wed, 2 Mar 88 17:31:29+0900 From: Mail Delivery Subsystem Subject: Returned mail: Cannot send message for 1 week To: root%sorak.kaist.ac.kr@RELAY.CS.NET To: TeXhax-request@SCORE.STANFORD.EDU ----- Transcript of session follows ----- 421 ketri.etri.re.kr.ether... Deferred: No buffer space available ----- Unsent message follows ----- Received: by sorak.kaist.ac.kr (5.51/4.12) id AA16074; Wed, 24 Feb 88 17:24:49+0900 Message-Id: <8802240824.AA16074@sorak.kaist.ac.kr> Received: from relay.cs.net by RELAY.CS.NET id ar10319; 23 Feb 88 19:04 EST Received: from score.stanford.edu by RELAY.CS.NET id aa18193; 23 Feb 88 18:20 EST Date: Tue 23 Feb 88 07:49:09 PST Subject: TeXhax Digest V88 #19 From: TeXhax Digest Errors-To: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List:; Reply-To: TeXhax@score.stanford.edu Received: from CSNet-Relay by kaist; 24 Feb 88 16:54:55-GMT+9:00 (Wed) TeXhax Digest Tuesday, February 23, 1988 Volume 88 : Issue 19 [SCORE.STANFORD.EDU]TEXHAX19.88 Editor: Malcolm Brown Today's Topics: under-tilde Re: Search paths (font files) for drivers Re: file extensions Request for fonts for the Addison-Wesley Epson printer driver. Icelandic TeX DVIDIS on BITNET Footnote rule macro Re: Flame of the week: Unix-style command interfaces PCWRITEX conversion driver PC-WRITE==>TeX Drop initials for LaTeX Bradfield comment LaTeX version numbers: statis thereof. multiplying cmssdc10 by 4 Re: Dynamic \parskip computation ---------------------------------------------------------------------- Date: 18-FEB-1988 08:37:36 GMT From: FPS%VAXA.CC.IMPERIAL.AC.UK@forsythe.stanford.edu Subject: under-tilde under-tilde: this is all rather embarassing. the following code will do an undertilde, and remains robust under a variety of conditions (like superscripting etc). however, i suspect \mathchoice was a sledgehammer approach. using \mathpalette i couldn't get the spacings right, but maybe i should go back and give it another whirl. incidentally, without the sterling preview capabilities of TeXtures this would have been a nightmare: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \def\ut#1,\mathchoice %displaystyle ,\vtop,\ialign,##\crcr $\hfil\displaystyle,#1-\hfil$\crcr\noalign ,\nointerlineskip\vskip1pt- $\hfil\displaystyle\char'176\hfil$\crcr--- %textstyle ,\smash ,\vtop,\ialign,##\crcr $\hfil\textstyle,#1-\hfil$\crcr\noalign ,\nointerlineskip\vskip1pt- $\hfil\textstyle\char'176\hfil$\crcr--- ,\textstyle\vphantom,#1--- %scriptstyle ,\vtop,\ialign,##\crcr $\hfil\scriptstyle,#1-\hfil$\crcr\noalign ,\nointerlineskip\vskip0.7pt- $\scriptstyle\hfil\char'176\hfil$\crcr--- %scriptscriptstyle ,\vtop,\ialign,##\crcr $\hfil\scriptscriptstyle,#1-\hfil$\crcr \noalign,\nointerlineskip\vskip0.5pt- $\scriptscriptstyle\hfil\char'176\hfil$\crcr---- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % testing, testing % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% $$\ut,\bf X-\ut,1-\ut,\bf\Phi-abcaN,\ut,\aleph--b_,\ut,Q-_,\ut,.---$$ $$\ut,\oldstyle7-\ut,\cal A-$$ or even something ordinary $\ut,\alpha+\beta-$ but what happens in text mode when we go on and on and on long enough to complete at least two lines, will the baselines be the proper width apart, or will they have a bit extra added because of this tilde? $$\ut,\alpha+\beta\times\gamma-$$ \end %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% malcolm clark aka texline@uk.ac.ic.cc.vaxa (janet) ------------------------------ Date: Wed Feb 17 15:05:28 MET 1988 From: XITIJSCH%DDATHD21.BITNET@forsythe.stanford.edu Subject: Re: Search paths (font files) for drivers Please excuse the late reaction but we had some drop outs in our TeXhax delivery. Stephan Bechtolsheimer writes Does anybody have string feelings for search paths for fonts files of drivers? There are two extremes: one is to use the environment variable TEXFONTS as TeX does, the other extreme is use separate search paths like TEX_PK, TEX_GF, TEX_PXL. In our drivers we have choosen a third possibility because we think that both solutions are not adequate. TeX uses only one area because for all output devices the font metrics should be the same. (Minor differences as in the gray fonts are an other subject.) But for each printing engine there will be a different set of fonts. Character outlines and descriptions in those font files (be it GF, PK or PXL format) for one device should not differ because they should all be created from the GF file. (Converting PK files to PXL files with PKtoPX and back with PXtoPK can yield a new font with different horizontal escapements --- this is especially true for the cm font family.) So I would propose to distinguish the output devices but not the font formats. This will yield, e.g., to path names like RICOH_FONT, IMAGEN_FONT, etc. The formats can be indicated by a suffix (but only for the human --- device drivers should ignore the suffix and should {\it only\/} look at the magic two or four bytes at the beginning of the font file). Joachim TH Darmstadt Institut f\"ur Theoretische Informatik Joachim Schrod Alexanderstr. 24 Bitnet: XITIJSCH@DDATHD21 (Please try again if I don't answer --- D-6100 Darmstadt our Bitnet connection is very instable...) West Germany ------------------------------ Date: Wed Feb 17 14:51:31 MET 1988 From: XITIJSCH%DDATHD21.BITNET@forsythe.stanford.edu Subject: Re: file extensions John Ramsdell wanted other suffixes than `.tex' for input files (TeXhax #7/8) and Eric Berg has answered that this is impossible because the file type is ``hardcoded'' (TeXhax #14). Please note that the statement of Eric Berg [...] a different .FMT file by itself can't change the default file type [...] is wrong. The file type is a WEB string, i.e. a preprocessed string (see section 537 in TeX and remember that each preprocessed string is written once to the string pool file), and is written into TEX.POOL by TANGLE. TEX.POOL is read by INITeX and \dump'ed to the .FMT file --- therefore TeX knows about the default file suffixes from the .FMT file. So if you want different suffixes just keep several copies of TEX.POOL for each macro package and edit each copy (yes, search for `.tex' and don't forget to alter the length designator in front of the line). The different macro packages will have different file default suffixes after this. The same procedure can be used to alter the default input search area (TeXINPUTS) --- this enables the possibility to locate input files like style files for each macro package in an other area. (At least, in most TeX implementations.) But if you choose other file suffixes, don't make the extensions longer than three letters --- many systems (notably the PC's) don't allow more and file exchange will be unnecessarily difficult. (I.e., use `.cwb' instead of `.cweb'!) Joachim Schrod TH Darmstadt Institut f\"ur Theoretische Informatik Joachim Schrod Alexanderstr. 24 Bitnet: XITIJSCH@DDATHD21 (Please try again if I don't answer --- D-6100 Darmstadt our Bitnet connection is very instable...) West Germany ------------------------------ Date: Thu, 18 Feb 88 14:58:31 IST From: "Jacques J. Goldberg" Subject: Request for fonts for the Addison-Wesley Epson printer driver. Mark, 1. Quick solution to get them at 240dpi only: purchase the PC TeX Epson driver. It has CM fonts, and many more varieties than the MicroTeX package driver. However, no 120dpi for fast draft quality. They come PXL but PXL-EPF loves them 2. See TUG, may have what you need on stock, at least in PXL format. 3. If you still consider do-it-yourself, well, breathe in and read this: To make them is a real pain, for several reasons, not only the CPU cost. I have done that. The question is, how to ship them ? I have run Metafont for all Computer Modern fonts at 240dpi and 120dpi, at magsteps 0,1/2,1,2,3,4. This has taken 18 hours (yes) of IBM-3081D cpu. I had contemplated doing it on a VMS VAX785 : that would have taken about 120 hours of CPU. Then I turned GF into PXL files, on the mainframe. Then I downloaded the files to a PC at 9600 bauds, it took only approximately 48 hours. Then I had to strip off the trailing zeroes at the end of the TFM and PXL files which IBM's VM (and DEC's VMS) pad to make fixed size blocks. Then I had to PXL->EPF all the files with the Addison-Wesley (MicroTeX) utility (PXL-EPF) to make the EPF files. On my way I had to discover that Metafont's aspect ratio parameter should NOT be changed from 9/10 when going from 240dpi to 120dpi (unadvertized in the DOTPRNT documentation). If I hadn't purchased PersonalReXX before, I might still be busy typing commands: mind you, 85 files times 12 subdirectories. This was to make you aware, in case you were not, that Metafont CPU hours are not the end of it. Now if YOU, or for that matter anybody else still bound to the poor AM* fonts libraries distributed with MicroTeX, want those fonts, what is your suggestion about how to ship them ? That's about 50x360kb diskettes if in backup format with one backup per directory, or that's about 15 PS2 3inch1/2 diskettes. If I send you a magnetic tape, will you want to load it to your mainframe and then download with KERMIT ( which I used) or a similar file transfer utility? If any of those solutions makes sense for you, will a request for a $150 contribution sound exaggerate, to purchase the media and cover duplications costs and air mail ? (needless to say, check to my university, not personal to me, with receipt) . And what's going to happen to me if more people ask for that? Will I turn from being a Physics Prof. into a diskette duplicator ? Or should I consider shipping prerecorded hard disks anyway ? (this stuff takes up 1/2 at least of my 32MB hard disk on my self assembled machine, not an IBM of course). Jacques ------------------------------ Date: Wed, 17 Feb 88 18:02 EST From: Armann Ingolfsson Subject: Icelandic TeX I recently read an article in the TeXhax Digest in which the author refered to an Icelandic version of TeX. I could not find any mention of the Icelandic version of TeX in the issues of the TeXhax digest stored at this university (SUNY at Buffalo) at the time. What is the best way for me to obtain information about this version of TeX? Thanks, 'Armann Ing'olfsson. ------------------------------ Date: Wed, 17 Feb 88 17:03 EST From: "Jerry Leichter (LEICHTER-JERRY@CS.YALE.EDU)" Subject: DVIDIS on BITNET In a recent issue of TeXhax (V88 #15), Niels Walet asks whether there is any way to receive my DVIDIS previewer for VAXStations on BITNET. This jogged my memory, and I realized that I had forgotten to forward the following message I received, many weeks ago, from a kind soul who, in return for my getting the stuff out to him, has offered to provide it to other BITNET sites: Date: 6 Jan 88 12:59 +0800 From: Ed Sternin Subject: RE: DVIDIS files To: "Jerry Leichter (LEICHTER-JERRY@CS.YALE.EDU)" I would be most happy to serve as a supplier of these files to BITNET world. Those able to understand NETDATA encoding of binary files should send their requests to useredik@ubcmtsg.bitnet Those capable of accepting EAN files (which always travel AS IS, whether ascii or binary), send requests to edik@nmr.physics.ubc.cdn For now only by special arrangement, but this may change soon (I am trying to convince someone at TRIUMF to give the files a permanent home), VMSDUMP files can be mailed via BITNET. Send requests to the second address above. Please be kind to Ed; he's probably decided that serving as a source is pretty easy - no requests on 6 weeks, right? -- Jerry ------------------------------ Date: Thu, 18 Feb 88 15:24:28 EST From: dow@wjh12.harvard.edu (Dominik Wujastyk) Subject: Footnote rule macro A colleague of mine, Prof. Gary Tubb, is using TeX to set the next volume of the Harvard Oriental Series, of which he is the editor. He is required to make the volume comply with the style of previous volumes in the series, and the following macro was written in the course of doing this. Since Gary is not yet on the net, he is submitting this through me. ----------------------------------- cut here -------------------------------- % * The plain TeX format places a footnote rule above the % * footnotes on each page. It may be omitted by changing the % * height of \footnoterule to 0pt. But traditional book % * design often calls for the use of such a rule only above a % * continuation of a footnote broken on the previous page. % * Using a variation of a "the dirtiest trick of all" % * described on page 400 of The TeXbook, the following code % * adds to the plain.tex format so as to prevent the footnote % * rule when notes are printed, except when the previous page % * contains footnote material with no completed footnote in % * its last line. % * % * First a strut that will be 1sp deeper than the normal strut % * (and thus significant to TeX but invisible to the human % * eye) is provided, to be placed at the end of each completed % * footnote: \newdimen\fnendstrutdepth \fnendstrutdepth=\dp\strutbox \advance\fnendstrutdepth by 1sp \newbox\fnendstrutbox \def\fnendstrut{\unhcopy\fnendstrutbox} \setbox\fnendstrutbox=\hbox{\vrule height\ht\strutbox depth\fnendstrutdepth width0pt} % % * Then a portion of the footnote commands in plain.tex is % * redone with two changes, so that the strut is placed after % * each completed note and may appear in the last line of % * footnote material on a page: % \catcode`\@=11 \def\vfootnote#1{\insert\footins\bgroup \interlinepenalty=\interfootnotelinepenalty \splittopskip=\ht\strutbox \splitmaxdepth=\fnendstrutdepth % * This is one change. \floatingpenalty=20000 \leftskip=0pt \rightskip=0pt \spaceskip=0pt \xspaceskip=0pt \textindent{#1}\footstrut \futurelet\next\fo@t} \def\@foot{\fnendstrut\egroup} % * This is the other. \catcode`\@=12 % % * Next a new condition is provided, for checking to see % * whether the footnote material on the previous page ended % * with the special strut, and thus with a completed footnote: % \newif\ifbrokennote % % * Finally, the definition of \pagecontents is redone by % * surrounding the command for printing the footnote rule with % * a check and reset of this new condition: % \catcode`\@=11 \def\pagecontents{\ifvoid\topins\else\unvbox\topins\fi \dimen@=\dp255 \unvbox255 \ifvoid\footins\else \vskip\skip\footins \ifbrokennote\footnoterule\fi % * These lines replace the \ifdim\dp\footins=\fnendstrutdepth% * command \footnoterule \global\brokennotefalse % * in the original version \else\global\brokennotetrue\fi % * of plain.tex. \unvbox\footins\fi \ifr@ggedbottom \kern-\dimen@ \vfil \fi} \catcode`\@=12 % % * NB: This approach assumes that each footnote begins on a % * new line. If the plain.tex format has been enhanced to % * allow short footnotes to be printed continuously or in % * columns, the last line of footnote material on a page may % * contain a completed footnote, even if the final note is % * continued on the following page. % * % * % * Gary Tubb, % * Assoc. Professor of the Humanities (Sanskrit), % * Harvard. % * % * Snail: Quincy House #100, % * Cambridge, MA 02138. % * % * E-mail c/o Dominik Wujastyk % * Internet: dow@wjh12.harvard.edu % * Bitnet: dow@harvunxw.bitnet % * uucp: ...!ihnp4!wjh12!dow % * ------------------------------ Date: Thu, 18 Feb 88 11:04:53 PST From: Subject: Re: Flame of the week: Unix-style command interfaces Don Hosek writes in TeXhax V88#17 deprecating use of Unix-style command interfaces... > Why don't I like Unix-style interfaces? Because I'm not on a unix system! > ... Writing in C is not a sufficient excuse. He has a point in that Unix-style option letters don't sit comfortably beside the other commands on a non-Unix system with a well-defined way of setting command options, such as VMS. Looking at VMS in particular, there is another advantage in using the ``standard'' method, in that the command-definition language which is used to define command qualifiers also allows sophisticated checking of qualifiers and their parameters to be performed. All this happens *without* loading the executable image, since it's done in the command interpreter, so a bad qualifier or parameter is reported to the user before the program runs. Unix-style C programs which use minus-flagged options letters have to do their own checking at run-time, independently of the operating system. I'm a user of both Unix and VMS, implementing TeX and its supporting software on both systems, so I can see both sides of the argument, but I think VMS scores here in consistency and utility. I'd say that programs running under VMS should use these facilities where possible, but how do developers of portable software feel about this? I know that Nelson Beebe, for example, argues in the implementation details for his driver software on using Unix-style consistently across different systems. Dave. ------------------------------ Date: Thu, 18 Feb 88 16:28 GMT From: Peter Flynn UCC Subject: PCWRITEX conversion driver PC-WRITE==>TeX For those using (or with users using) the PC-WRITE editor/wordprocessor on PCs, I have developed an interface to TeX which retains most (not all) of their formatting and typeface attributes. This means people with documents written using PC-WRITE's wordprocessing facilities can export their document (assumed to be a .DOC file) into a .TEX file direct. The final cleanup is thus minimised and avoids tedious repeat-replaces and hunting for obscure characters. All the IBM PC character set is represented, excluding the line-drawing characters (I could add these, in \tt form, for use in \verbatim mode, I guess). The distribution file is a UUEncoded .ARC file of 108Kb containing: READ.ME instructions PR.DOC PC-WRITE print driver definitions PCWRITEX.DOC documentation file PCWSTY.TEX TeX file of redefinitions PCWRITEX.TEX documentation after running thru the driver PCWRITEX.DVI TeX output of documentation PCWRITEX.HP HPLJ printable documentation I can mail this to anyone who wants it, but I would prefer if some kindhearted moderator would stick it up on a server somewhere. For those on BITNET VAXen, I can send/file/vmsdump the .ARC, which is smaller; for those with Colour Book FTP (ie JANET and HEANET), the file is VAX1.UCC.IE::DB0:[FTP]PCWRITEX.ARC (uid FTP, psw FTP). I cannot claim it is 100% bugfree, and I do not have the time to provide full support, but anyone is free to modify it how they wish. A copy has also been sent to Kevin White (kevinw@bytecosy) on BIX for the IBM.ARC area. Peter Flynn ------------------------------ Date: Thu, 18 Feb 88 16:19:39 EST From: dow@wjh12.harvard.edu (Dominik Wujastyk) Subject: Drop initials for LaTeX I have made small modifications to David Cantor's macro for making a drop initial (or initials) at the start of a paragraph, in order to make the macro work easily in the LaTeX environment. The files DROP.DOC and DROP.STY which contain these modifications have been sent to Ken Yap's LaTeX style repository at Rochester. Dominik Wujastyk bitnet: user DOW on the bitnet node HARVUNXW arpanet: dow@wjh12.harvard.edu csnet: dow@wjh12.harvard.edu uucp: ...!ihnp4!wjh12!dow ------------------------------ Date: Thu, 18 Feb 88 12:28:38 EST From: Steve Campbell Subject: Bradfield comment I also thought the Lamport comment unreasonably critical for the following reason. I write scientific papers using LaTex. I have no desire to hack any- thing and would be happy with the style. However, I often have to produce camera ready copy for conference proceedings with a style specified by the conference organizers or their publishers. If I do not follow the style, my paper may not be included. Questions of greater beauty are irrelevant in this case. Steve Campbell ------------------------------ Date: Thu, 18 Feb 88 15:47 CST From: "John L. Huxtable" Subject: LaTeX version numbers: statis thereof. I am concerned about the way LaTeX is updated. Dr. Lamport seems to feel it is sufficient to change the date printed by the program when he makes changes. Most people (Dr. Knuth apparently included) find it reasonable to change the version number as well. In general, people do not remember dates---they remember version numbers, and few enough of those. What justification is there for keeping the version number at 2.09 when the source has changed many times? John L. Huxtable The University of Kansas huxtable@ukanvax.bitnet (Now) huxtable@kuhub.ukans.edu (Someday?) ------------------------------ Date: Thu, 18 Feb 88 15:17:22 EST From: "Karl Berry." Subject: multiplying cmssdc10 by 4 is not a good idea. I doubt that the resulting file will even make it through Metafont, let alone produce decent characters. As I think has been mentioned before, John Sauter at DEC has produced Metafont files that interpolate between Knuth's values for the parameters. Therefore, you can make any point size Computer Modern font you like, and the type looks better than magnification. The difference between, say, Sauter's cmr11 and cmr10 scaled \magstephalf is noticeable, perhaps even if you haven't had type design training. He also has VMS command files to help the development, and I have similar ones for Unix. But all the real work is done in Metafont, so his work shouldn't be any more operating system dependent than Metafont itself. Karl. karl@umb.edu ------------------------------ Date: Thu, 18 Feb 88 15:54:07 CST From: "Thomas J. Reid" Subject: Re: Dynamic \parskip computation Stephen V. Bechtolsheim asked (in TeXhax 88 # 17) about using \everypar to call a macro to set the \parskip glue to be placed before the paragraph. As he points out, the paragraph has already been started by the time the \everypar token list gets expanded. The solution is to "back-out" the paragraph, set \parskip, then restart the paragraph. One condition which requires special attention is that the paragraph may have been started using \noindent. This fact needs to be noted so that when the paragraph is restarted, the normal \parindent glue is not added. The remainder of this note contains the needed \everypar token list as well as some testing macros. Tom Reid % Test for response to Stephen v. Bechtolsheim's TeXhax note % about having a "\ComputeParSkip" call to compute the \parskip % to be placed before each paragraph. \newcount\parcount \parcount=0 % Define a simple \ComputeParSkip macro that cycles the \parskip glue % from 6pt to 36pt by 6pt intervals. A small amount of stretch and % shrink are included to prevent overfull/underfull vboxes. \def\ComputeParSkip{\global\advance\parcount by 6 \ifnum\parcount>36 \global\parcount=6 \fi \parskip=\parcount pt plus 1pt minus 1pt } % Save the old \everypar token list. \edef\oldeverypar{\the\everypar} % Define the new \everypar token list incorporating the old list. % First, set the default ("outer level") \parskip to 0pt. \parskip=0pt \everypar={\oldeverypar {\everypar={\relax}\setbox0=\lastbox \parindent=\wd0 \ComputeParSkip \par \leavevmode}} % Detailed Description of New \everypar: % % The function of this token list is to "back-out" the paragraph, set the % new \parskip glue (using \ComputeParSkip), then restart the paragraph. % The detailed function of each step follows: % % \oldeverypar..........Execute the token in the original \everypar token % list. % % {.....................Start a new group to localize the effect of the % commands which follow. % % \everypar={\relax}....Temporarily (since we're in a local group) % redefine \everypar to prevent endless recursion of the previous % \everypar token list. % % \setbox0=\lastbox.....Place the last hbox in \box0. At the time that % \everypar is executed, the "last" box is the paragraph indent glue % that started the paragraph. This may be the value of \parindent % if the paragraph was started in the normal way, or it may be a box % 0pt wide if the paragraph was started with \noindent. Execution of % \lastbox also causes the previous hbox to be removed from the % current horizontal list. % % \parindent=\wd0.......Assign the width of the paragraph indent box % to \parindent. % % \ComputeParSkip.......Call a macro to compute and same the desired % paragraph skip in \parskip. Note that this macro is called from % within an inner group, so some of its functions may have to be % made global (hence the \global\advance in the sample macro above). % However, the assignment of \parskip must NOT be made global: the % value of \parskip at the outer level must remain to be 0pt. % % \par..................This ends the "just-begun" paragraph. Since % \lastbox removed the paragraph indent glue from the horizontal % list, the only remaining trace that a paragraph existed is the % \parskip glue that was in effect at the outer level. This will % be a skip of 0pt. % % \leavevmode...........Restart the paragraph using the temporary % \parskip and \parindent. This effectively restarts the paragraph % using the original paragraph indentation and the newly computed % \parskip. % }.....................End the inner group and restore \parskip to 0pt % and \parindent to its original value. % -------------------------------------------------------------------- % Define some handy-dandy random text generating macros. For more % information on these, see "Floating figures at the right, and % Some random text for testing" (TUGboat Vol. 8 No. 3 pp. 315--320). % Note: The macros have been modified so that a blank is not output % before the first word of a sentence. \newcount\rndnum \newcount\rndval \newcount\rndtemp \rndnum=0 \def\rnd{\global\multiply\rndnum by 371 \global\advance\rndnum by 1 \ifnum\rndnum>99999 \rndtemp=\rndnum \divide\rndtemp by 100000 \multiply\rndtemp by 100000 \global\advance\rndnum by -\rndtemp \fi \global\rndval=\rndnum \global\divide\rndval by 1000 \relax} \newcount\ns \newcount\nw \newcount\nc \newcount\np \newcount\ASCII \def\randompar{\rnd \ns=\rndval \divide\ns by 10\advance\ns by 3 \loop \ifnum\ns>0 {\randomsent}. \advance\ns by -1 \repeat} \newif\ifsos % Flag for "start of sentence." \def\randomsent{\rnd \nw=\rndval \divide\nw by 7 \advance\nw by 5 \ASCII="41 \sostrue \loop \ifnum\nw>0 \ifsos \sosfalse \else \ \fi {\randomword}\advance\nw by -1 \repeat} \def\randomword{\rnd \nc=\rndval \divide\nc by 15 \advance\nc by 2 \loop \ifnum\nc>0 {\randomchar}\advance\nc by -1 \repeat} \def\randomchar{\rnd \multiply\rndval by 29 \divide\rndval by 100 \ifnum\rndval=26 \rndval=0 \fi \ifnum\rndval>26 \rndval=4 \fi \advance\rndval by \ASCII \char\rndval \global\ASCII="61} % Using the current time in minutes since midnight, skip a variable % number (0 to 99) of pseudo-random numbers. This way, the job % stands a good chance of being different every time it is run. \np=\time \ns=\np \divide\ns by 100 \multiply\ns by 100 \advance\np by -\ns \loop \ifnum\np>0 \rnd \advance\np by -1 \repeat \noindent \randompar % Generate a non-indented paragraph. % Generate 20 to 29 paragraphs of "text." \rnd \np=\rndval \divide\np by 10 \advance\np by 20 \def\dopar{\par} \loop \ifnum\np>0 \dopar {\randompar}\advance\np by -1 \repeat \noindent \randompar % Generate another non-indented paragraph. \bye % Thomas Reid / Texas A&M University / Computing Services Center ------------------------------ End of TeXhax Digest ************************** ------- 3-Mar-88 02:06:37-PST,30027;000000000000 Return-Path: <@RELAY.CS.NET:MAILER-DAEMON@sorak.kaist.ac.kr> Received: from RELAY.CS.NET by SCORE.STANFORD.EDU with TCP; Thu 3 Mar 88 02:06:15-PST Received: from relay2.cs.net by RELAY.CS.NET id aa10824; 3 Mar 88 4:33 EST Received: from sorak.kaist.ac.kr by RELAY.CS.NET id ae12655; 3 Mar 88 4:05 EST Received: by sorak.kaist.ac.kr (5.51/4.12) id AB00686; Thu, 3 Mar 88 13:27:00+0900 Date: Thu, 3 Mar 88 13:27:00+0900 From: Mail Delivery Subsystem Subject: Returned mail: Cannot send message for 1 week To: root%sorak.kaist.ac.kr@RELAY.CS.NET To: TeXhax-request@SCORE.STANFORD.EDU To: TeXhax-request@SCORE.STANFORD.EDU ----- Transcript of session follows ----- 421 ketri.etri.re.kr.ether... Deferred: Connection timed out during user open with ketri.etri.re.kr ----- Unsent message follows ----- Received: by sorak.kaist.ac.kr (5.51/4.12) id AA01629; Thu, 25 Feb 88 11:37:37+0900 Message-Id: <8802250237.AA01629@sorak.kaist.ac.kr> Received: from relay.cs.net by RELAY.CS.NET id am17180; 24 Feb 88 19:05 EST Received: from score.stanford.edu by RELAY.CS.NET id aa10360; 24 Feb 88 18:55 EST Date: Wed 24 Feb 88 07:42:50 PST Subject: TeXhax Digest V88 #20 From: TeXhax Digest Errors-To: TeXhax-request@Score.Stanford.EDU Maint-Path: TeXhax-request@Score.Stanford.EDU To: TeXhax Distribution List:; Reply-To: TeXhax@score.stanford.edu Received: from CSNet-Relay by kaist; 25 Feb 88 11:01:49-GMT+9:00 (Thu) TeXhax Digest Wednesday, February 24, 1988 Volume 88 : Issue 20 [SCORE.STANFORD.EDU]TEXHAX20.88 Editor: Malcolm Brown Today's Topics: Strange Interaction in Latex LaTeX style and indented 1st paras DVI2LN3 V12.3 Possible fix for VMS METAFONT V1.3(?) delatex Times Roman in Metafont tbl to TeX halign wanted generalizing \boxit with \leaders type construction for border More on transferring DVI files to VAX VMS cmnaro? LaTeX Notes (TeXhax V88 #18) standardizing dvi2ps TeX-to-C Padding dvi files hanging letters More Common TeX vs. TeX-to-C benchmarks Metafont mode_def settings for Dataproducts LZR-2665 Re: stripping comments from .sty files RE: Flame; LaTeX Notes indentation question ---------------------------------------------------------------------- From: VARDI%ALMVMA.BITNET@forsythe.stanford.edu Date: 18 Feb 88 17:30 PST Subject: Strange Interaction in Latex In the following example, there is a strange interaction between the \small, the theorem environment, and the enumerate environment. If you Latex it as it is, the items of the list are indentened to the left of the left margin. Take away the \small, and the items are indented properly. Moshe Vardi vardi@ibm.com, vardi@almvma.bitnet \documentstyle[12pt]{article} \begin{document} \newtheorem{theorem}{Theorem} Here is some text. This is simple text. There is nothing special about this text. There is absolutely nothing special about this text. \small Here is some text. This is simple text. There is nothing special about this text. There is absolutely nothing special about this text. \normalsize Here is some text. This is simple text. There is nothing special about this text. There is absolutely nothing special about this text. \begin{theorem} Here is some text. This is simple text. There is nothing special about this text. There is absolutely nothing special about this text. \begin{enumerate} \item Here is some text. \item Here is some text. \end{enumerate} \end{theorem} \end{document} ------------------------------ Date: Fri, 19 Feb 88 00:45 GMT From: Peter Flynn UCC Subject: LaTeX style and indented 1st paras Julian Bradfield takes Leslie Lamport to task for his abrasive style. That may be so, I happen to like some of his more caustic comments, but then that may just be *my* style. The issue is, who is the arbiter of typographic elegance? Is it the document designer or the reader? (I can't answer this one, I doubt if anyone can.) JB seems to be complaining that LL dislikes people requesting mods to LaTeX style, when in fact people are quite free to make the mods themselves, it's a question of whether *they* should ask LL to install those mods as standard or not. LaTeX as delivered is LL's baby: people who want it different should do it themselves, document it, and submit it to the list for general consumption, but not expect LL to accept it as a de facto standard. (I am excluding actual bug fixes from this, of course.) BTW, non-indented 1st paras are quite nice. They are an improvement to the appearance when \parindent is quite small (a few ems) because they lead to a less lop-sided feel when preceded by a lot of vertical white space, which you typically get (a) at the start of a document, (b) after an itemised list, (c) after a change in the \leftskip, (d) after display math. The (d) is done automatically by TeX, anyway, isn't it? I don't use LaTeX, so I can't say if (b) and (c) apply, but they ought to, if (a) applies. If, as some people do, you set \parindent=\hsize \divide\parindent by2 and then use a grouped \parindent=4em for \item etc, you can probably get away without de-indenting the 1st para, because the eye will pick up oddball formats like this more easily than more normal ones. Peter Flynn, University of Cork, Ireland ------------------------------ Date: Thu 18 Feb 88 21:37:54-PDT From: BELL%KUPHSX.SPAN@STAR.STANFORD.EDU (Did someone need a Subject: DVI2LN3 V12.3 Well, it seems that I didn't quite fix the problem with finding the correct PXL files under various magnifications in version 12.2 of DVI2LN3. I have now made DVI2LN3 figure out the correct magnification of the PXL files as best it can (given TeX's penchant for rounding off) and then checking that directory. If it can't find it there, it then checks directories with one more and one less than the magnification DVI2LN3 calculates. This means that it will check (for example) TeX$PXLDIR:[1643] first, and then [1644] and [1642] if it cannot find the file. This usually fixes the problem, as has been pointed out many times in past issues of TeXhax. I have already sent corrected versions of the necessary files to people who requested V12.2. If you requested the driver more than 2 weeks ago and have not yet received it, there are two possibilities: (1) You message got lost in the network; or (2) I tried to send the files, and the mailer(s) didn't like the address I gave. I only try once, so you might consider requesting the driver again. There have been no other enhancements of the driver, as my dissertation work has been taking up too much time lately. I'll try and keep everyone informed as to future upgrades. Ed Bell Dept. of Physics \& Astronomy The University of Kansas Lawrence, KS 66045-2151 (913)864-3610 Reply to (in order of preference for each net): ARPANET: Bell%KUPHSX.SPAN@STAR.STANFORD.EDU or Bell%KUPHSX.SPAN@JPL-VLSI.ARPA or Bell%KUPHSX.SPAN@128.8.250.4 BITnet: Bell%KUPHSX.SPAN@SU-STAR.ARPA or Bell@UKANVAX SPAN/HEPnet/ European Decnet: KUPHSX::Bell (7.220) or 7388::Bell THEnet: UTADNX::UTSPAN::KUPHSX::Bell ------------------------------ Date: Fri 19 Feb 88 07:25:49-PDT From: BELL%KUPHSX.SPAN@STAR.STANFORD.EDU (Did someone need a Subject: Possible fix for VMS METAFONT V1.3(?) I have noticed that several people have had some trouble lately generating a functional version of METAFONT V1.3 on VMS systems. Since our version has worked for some time now, I thought I would suggest something which I did last summer with V1.0. I was getting several PASCAL compiler errors and (at times) getting the program to outright blow-up in my face. It turned out that the VMS change file contained some lines that said something to the effect of "Change to fix V3.X bug". As soon as I deleted these sections of lines, the programs compiled and ran perfectly (at least it doesn't traceback). I don't know if the people having trouble have ever eliminated these lines from their change files, but it seems to me to be a good place to start. Ed Bell ------------------------------ Date: Fri, 19 Feb 88 07:27:22 PST From: jageorge@nla1.cs.utk.edu (J.ALAN GEORGE) Subject: delatex I would like to use spell on my LaTeX documents, and need the analog of deroff to remove the LaTeX control words, math, figures etc. from the file before running it through spell. Anyone have a sed script to do this? Alan George Mathematical Science Section Oak Ridge National Laboratory Oak Ridge, TN 37831 jageorge@ornl-msr.arpa ------------------------------ Date: 19 Feb 88 11:35:09 +1100 (Fri) From: munnari!wcc.oz.au!alw@uunet.UU.NET (Alex Warman) Subject: Times Roman in Metafont Does anyone know if a Times Roman has been produced in Metafont, either PD or for $$. I would be interested if some-one has Times Roman fonts for the Laserwriter too, even if they are not done with Metafont. In fact has any-one compiled a list of typefaces/fonts available, done in Metafont or with other tools, and availability/prices etc. ? thanks, Alex Warman (alw@wcc.oz) ------------------------------ Subject: tbl to TeX halign wanted Date: Fri, 19 Feb 88 12:33:23 PST From: Jeffrey Goldberg We have users running code that generates tbl input, but nobody here uses troff; we all use TeX. Does anyone have a filter that will take tbl input and generate useful TeX input? I may end up writing something myself, but I don't know tbl, and my TeX isn't that good either. Please send mail. I will post a summary of positive responses. (There is no need to post a summary of "Let me know what you find out" messages.) Thanks, jeff goldberg -- Jeff Goldberg Internet: goldberg@csli.stanford.edu ------------------------------ Date: Fri, 19 Feb 88 18:20 EST From: (Bob Jantzen, BITNET:JANTZEN@VUVAXCOM) Subject: generalizing \boxit with \leaders type construction for border Has anyone thought of putting together the Texbook \boxit macro (p.225) with a \leader type construction to replace the rules by repetitions of an arbitrary character, in such a way that the corners work out nicely, i.e., the corner copies of the character align both horizontally and vertically with the two leaders which meet there? Is this even possible? I must confess I haven't even solved the first problem which ignores corner effects. Bob Jantzen Villanova University Bitnet: jantzen@{villvm | vuvaxcom} Arpa: jantzen%{villvm | vuvaxcom}.bitnet@eddie.mit.edu UUCP: ...!vu-vlsi!excalibur!jantzen Snail: deptmathsciences villanova university villanova pa 19085 At&t: (215)645-7335 PS: rarely logon to ibm ------------------------------ Date: Thu, 18 Feb 88 09:36 DST From: Reid Rowlett Subject: More on transferring DVI files to VAX VMS Nelson Beebe reported his experience in TeXhax #16 with transferring DVI files from Unix to VAX VMS. I have encountered similar tribulations sending DVI files from a PC to a VMS system, and some TeXhax readers might be helped by what I discovered. Some of my problems may have been specific to the various software elements, so for the record, I was running Micro-TeX on my IBM-compatible PC, and using K&S IMPRINT (for VAX/VMS) to print the DVI files on an Imagen laser printer. The problem, as Beebe points out, is the over-elaborate (to my mind, anyway) record structure that VMS uses for all files. IMPRINT expects DVI files to have 512-byte fixed length records. Any other file format will cause IMPRINT to burp. Fortunately, there's a way out of the morass. I have two ways of transferring a DVI file from my PC to the VAX: Kermit and FTP (using Excelan Ethernet software). I use Kermit for reasonably short files, and FTP for longer ones, for reasons unimportant here. To use Kermit, one must tell the VAX Kermit to use "fixed" format, and the PC Kermit to use "binary" format. Kermit then luckily creates a VAX file with the proper record length. I was not so fortunate with FTP: a binary transfer from PC to VAX creates a file with "undefined, maximum 1024-byte length records", which IMPRINT cannot handle. The solution is to use the VMS FDL (File Definition Language) CONVERT utility to create a new file with the correct record structure from the old file after it has been FTP'd to the VAX. Being generally lazy and forgetful of VMS's endearingly multitudinous /THIS/THAT syntax, I created a one-line command file FIXUP.COM to do the work for me: $! FIXUP.COM -- Convert file to fixed-length 512-byte records $! Usage: @FIXUP $ convert/fdl=fixup 'P1'/pad 'P1' The CONVERT utility reads a file FIXUP.FDL which contains the specification for the new file (512-byte fixed length records) and then creates a new version of the file in that format. The FIXUP.FDL file should look like: RECORD BLOCK_SPAN yes CARRIAGE_CONTROL none FORMAT fixed SIZE 512 This can also be done interactively using EDIT/FDL (for masochists only). Of course, the DVI file on the PC must originally have a length which is a multiple of 512 bytes, which for Micro-TeX (or any TeX, I suspect) it does. I have other PC software that creates DVI files which do not have N*512-byte lengths, and I simply use DEBUG on the PC to pad them with zeroes out to a 512-byte multiple length before transferring. I hope this will be of use to some TeXhax-er out there. Reid Rowlett Unisys Corporation Reston Technology Center CSNet: rowlett@reston.unisys.com ------------------------------ Date: Fri, 19 Feb 88 16:43:04 CST From: hrp%windsor.CRAY.COM@uc.msc.umn.edu (Hal Peterson) Subject: cmnaro? When I first got a TeX tape, it contained a font called ``amnaro'': a bold, sans-serif font with tall, antique letters. It's ideal for chapter heading quotes. What happened to it? I haven't seen a cm equivalent, nor any parameter files. I can still use the old one, but I'd like more variety in size---there's only one amnaro. Hal Peterson / Cray Research / 1440 Northland Dr. / Mendota Hts, MN 55120 hrp%hall.CRAY.COM@umn-rei-uc.ARPA ihnp4!cray!hrp (612) 681-3145 ------------------------------ Date: Mon, 22 Feb 88 11:11 N From: (Nico Poppelier) Subject: LaTeX Notes (TeXhax V88 #18) This is a small response to the discussion between Julian Bradfield and Leslie Lamport. In his reply, Lamport states "I can't recall anyone disagreeing with me in TeXhax." In the first two issues of 1988, a few European TeX users, e.g., Hubert Partl (V88 #1), Oliver Schoett (V88 #2), attempted to discuss foreign-language modifications to LaTeX, following a suggestion by Renzo Beltrame (V87 #106). Leslie Lamport had made it very clear, in V88 #1, that he disagreed with Renzo Beltrame, and never replied to the submissions of the two European users, who clearly disagreed with him. Could Mr. Lamport please comment on the foreign-language matter again? Regards, Nico Poppelier ------------------------------ Date: Mon, 22 Feb 88 14:36:09 GMT From: Sebastian Rahtz Subject: standardizing dvi2ps Ken Yap's plea for standards in dvi2ps filters is appropriate; the version on the current Unix tape is well out of date in terms of features, for instance, so one has to hack ones own. What happened to Stephan v Bechtolsheim's? I was shown some output from it last summer, and there were announcements, but it seems to have gone dead. If anyone DOES merge all the offerings together, could I make a pathetic plea NOT just to make it available on that mysterious anonymous FTP you have other there? On two occasions when I have mentioned dvi2ps on TeXhax, people have contacted me for copies because they have no access to USA networks for FTP. In reference to Ken's wishlist, he does not specifically mention MacDraw files, which present special problems; I would also suggest that many features could be provided as TeX macros, once a basic PostScript-passing mechanism is in place (the approach that 'psfig' takes, inserting \specials without you knowing about it. ------------------------------ From: Sebastian Rahtz Subject: TeX-to-C at the risk of being boring, where does one get Tim Morgan's TeX-to-C? sebastian rahtz ------------------------------ Subject: Padding dvi files Date: Mon, 22 Feb 88 10:15:35 PST From: Richard Roy I had the need a few years ago to kermit some dvi files from a UNIX VAX to a VAX VMS 4.1 OS. I wrote the following program to pad the dvi file so it would successfully print using the IMPRINT system of Kellerman and Smith. --------------------- #define BUFSIZE 512 #define PADCHAR '\337' #include /* * dvipad is a simple program to generate dvi files which are multiples * of 512 characters in length, padding the last bytes with 233 or * 337 octal, a character which the IMPRINT spooler on VAX/VMS 4.1 * apparently wants to see at the end of the dvi files (the postamble). * Written 10/16/85 by rhr q */ main() { char buf[BUFSIZE]; int n,cnt=0; while ((n=read(0,buf,BUFSIZE)) == BUFSIZE ) { cnt++; if ( write(1,buf,n) != n ) fprintf(stderr,"write error on buffer %d!\n",cnt); } if ( n <= 0 ) { fprintf(stderr,"read error\n"); exit(1); } fprintf(stderr,"%d buffers copied!\n",cnt); if ( write(1,buf,n) != n ) fprintf(stderr,"write error on last buffer!\n"); fprintf(stderr,"padding file with %d 0337's\n",BUFSIZE-n); while ( n++ < BUFSIZE ) putchar(PADCHAR); } ------------------------- It's not a work of art, but for 10 minutes of work, it solved the problem. RR ------------------------------ Date: Mon, 22 Feb 88 16:08 EDT From: DAVIS%scrvx2.sdr.slb.com@RELAY.CS.NET Subject: hanging letters There have been a couple of messages about hanging letters at the beginning of a paragraph. Sadly, none of the answers seen so far appears to have done it correctly. Having been playing with it for a few days, I don't think that I know enough about TeX to solve it, but can provide one specification for what is *really* needed - coming from inspection of about 15 books which use such devices: 1) Its important that the bottom of the hanging letter (in the case of a capital, its baseline I imagine) lines up exactly with the baseline of the lowest indented line. ie; 2) It is desirable that the hanging letter be of sufficient point size to meet condition (1) and extend vertically above uppermost indented line (or at least, above a reference line drawn across the tops of the tail-less letters like n, m, o etc.) by at least 1em. I tried two approaches to (2) - firstly, having the macro accept an argument that uses the number of lines into which the hanging letter should hang, and then using scalable PostScript fonts (scalability being a virtue here, for once!) to generate a letter of the appropraiate point size. Secondly, I tried just taking a given \largefont, and hanging an appriate number of lines fr that size. The problem is - interline glue. You cannot just lower the box that contains the letter by NoOfHangingLines*\baselineskip, because there is no guarantee that this will line it up with the lowest line, because of interline glue, which we don't want turned off.... It seems to me that one theoretical approach is to get a number of lines to hang (either as an argument or determined by a font size) and then to \hangindent (NoOfHangingLines - 1) before setting the box containing the letter (and modified to have zero height....). So here's a pseudo-algorithm: get number of lines to \hangindent into NumLines LinesBoxed = 0 while (LinesBoxed < NumLines) box up a line set the hanging letter box set the final indented line and continue...... I do not know how to do this....... can anyone out there do this, or at least converge on the same aim - the setting of hanging letters in a way that does justice to TeX ? Don Knuth made it easy by designing his bend signs with a reference point that sets them in the right place automatically....... or so it seems..... Paul Davis davis%m_blue%sdr.slb.com@relay.csnet "whoever does not understand Unix is condemned to reinvent it.. badly!" ps: please reply direct while Malcolm is out of town... thanks ------------------------------ From: ekrell@ulysses.att.com Date: Mon, 22 Feb 88 17:13:28 EST Subject: More Common TeX vs. TeX-to-C benchmarks I was surprised by the figures showing Common TeX being faster than TeX-to-C. I have recently built both versions, and I got quite different results. The following are my figures, obtained on a lightly loaded Vax 8650 running 4.3 BSD Unix. I have Common TeX version 2.1 and TeX-to-C applied to TeX 2.9. I ran both programs on two different documents, one is a paper I am writing and it is currently 6 pages long. The second document is another paper, 18 pages long. The results of timing several runs of both programs under the same enviromental conditions yields the following: Document 1 Document 2 CommonTeX TeX-to-C CommonTeX TeX-to-C real 11.00 13.00 25.92 23.93 user 6.25 6.10 16.90 16.27 sys 0.50 0.60 1.28 1.20 The numbers are in seconds and I believe the meaning of these numbers has been previously explained. As you can see, there is no much difference between the two, and in the longer document, TeX-to-C is about 5% faster. Furthermore, CommonTeX is about twice as big as TeX-to-C (1.5 MB vs 750 KB). ------------------------------ Date: Mon, 22 Feb 88 23:55:17 EST From: elwell@tut.cis.ohio-state.edu (Clayton Elwell) Subject: Metafont mode_def settings for Dataproducts LZR-2665 The Dataproducts LZR-2665 laser printer is a high-speed PostScript printer that uses a Toshiba write-white engine. So far the best settings I've found for this marking engine are the ones John Gourlay proposed for the Xerox XP-12 engine in TUGboat V8N2: pixels_per_inch := 300; blacker := .6; fillin := -.3; o_correction := .6; With fonts generated using these settings, you can use 'dvi2ps' and still be able to read your output... It's not perfect, but it sure beats using fonts generated for the Canon engine. Clayton M. Elwell / elwell@tut.cis.ohio-state.edu ------------------------------ Subject: Re: stripping comments from .sty files Date: Tue, 23 Feb 88 11:44:34 -0500 From: Ken Yap I'm taking the liberty of forwarding this: > Some user's experience follows: > > As suggested by LL in TEXHAX #16, I measured the times for loading > .sty versus .doc files. I used an `empty' LaTeX document: > > \documentstyle{siam} > \begin{document} \end{document} > > I am using an ATARI ST with 20 MB harddisk. The results are: > > After .. seconds | happens > -------------------------------------------------------------------------- > siam.sty+siam10.sty|siam.doc+siam10.doc| > |(renamed to *.sty) | > -------------------------------------------------------------------------- > 6 | 6 | ``This is TeX ...'' > -------------------------------------------------------------------------- > 16 | 16 | ``(e:test.tex \\LaTeX Version..\\ > | | (siam.sty\\Documentstyle 'siam'..\\ > | | (siam10.sty'' > -------------------------------------------------------------------------- > 19 | 22 | ``)'' (siam10 finished) > -------------------------------------------------------------------------- > 25 | 29 | ``)'' (siam finished) > -------------------------------------------------------------------------- > 32 | 35 | Everything finished. > -------------------------------------------------------------------------- > > Conclusion: There is really no noticeable difference. > > A more serious problem is disk space: > siam10.doc+siam.doc take up 42 KB vs. 14 KB for the *.sty files! > Is this really necessary? Maybe some less verbose section headings > would be sufficient. (Suggestion to the authors?) A 6 MB partition > is so quickly filled... Interesting... > Finally something which annoyed me several times: The .doc files contain > or characters which, during the migration through netland, > keep getting translated into something else which either my editor or > TeX won't eat. Last time they ended up as question marks which were > greeted by LaTeX with a ``missing \begin{document}'' error message. > (But then also the backslashes in TEXHAX digests use to show up as > question marks at this site...) OK, I have edited the style files with form feeds so that they are preceeded by %. Future submitters to the collection please note. Also try to stay within 80 columns. You'd think card readers have been junked by now, sigh. :-) > Martin Costabel > TH Darmstadt, W.Germany Ken ------------------------------ Date: Tue, 23 Feb 88 16:22:47 -0800 From: Alastair Milne Subject: RE: Flame; LaTeX Notes indentation question As the questioner to whom Dr. Lamport's reply was addressed, I'm afraid I have to agree about the quality of the reply. While I have done enough ridiculous things in my life, and promptly been told so, that one more or less is of no grave consequence to me, I was rather disappointed with the relative lack of new information. It was always my assumption that a major phototypesetter would indeed be designed by people who knew about typography, and I did not particularly require confirmation of it. It is possible, however, that I was unclear about my particular need for exceptional indentation rules; and that I was perhaps the 572nd person to imply, however unintentionally, that the standard indentation rules in LaTeX's article style are in error. I can imagine that would quickly get on one's nerves. For the most part, I don't think they are so. I have in fact been very pleased overall with my results from LaTeX, which is the main reason I'm willing to invest some time (of which, like most of us, I have much too little) in learning its more sophisticated features. Certainly, being able to treat a large printing job as a programming problem has made things much easier when it really counted. Nevertheless, I can't suddenly start using different indentation styles from what have been our practise for years, even when different ones are recommended by typesetters. LaTeX's usefulness will therefore be compromised if I can't induce it to maintain our indentation practices. So I had hoped for a reasonably informative reply, and did feel rather let down by what I did get. I am not eager to invest the time in learning and modifying .sty files; but if there is no simpler way that somebody can show me, I suppose I'll have to try. BTW: for anybody still interested, the indentation problem I have is this: I need paragraphs to be formatted for technical documentation with an overhang like this. Several people were already kind enough to demonstrate how to use \leftskip and \parindent to do so, but these are not applied to the first paragraph in a [sub[sub]]section. With the overhang on all succeeding paragraphs, this looks rather silly. I've tried defining a special sectioning command that includes both \section and \indent, but the space that results between the section head and the first paragraph is much too big. So for the moment, it looks as if I'm off to explore the wilderness of .sty files. Hope the comments are good -- I'll need them. Alastair Milne ------------------------------ %%% %%% subscriptions, address changes to: texhax-request@score.stanford.edu %%% please send a valid arpanet address!! %%% %%% BITNET distribution: subscribe by sending the following %%% line to LISTSERV@TAMVM1.BITNET: %%% SUBSCRIBE TEX-L %%% %%% submissions to: texhax@score.stanford.edu %%% %%%\bye %%% ------------------------------ End of TeXhax Digest ************************** -------