TeXhax Digest Wednesday, June 24, 1987 Volume 87 : Issue 52 [SCORE.STANFORD.EDU]TEXHAX52.87 Editor: Malcolm Brownn Today's Topics: Address Correction - CANON LBP-8 Driver LATEX for non-english languages Oversized proof sheets Repeat offering of AutoLetter and LN03 driver. Missing fonts for the LN03 ytex -> plain tex 11x14 camera-ready conference papers Tex on the MacIntosh or Sun Workstation Dubious WEAVE behavior under VM/CMS TeX server? tree macros ---------------------------------------------------------------------- From: PEB%DM0MPI11.BITNET@forsythe.stanford.edu To: TEXHAX@score.stanford.edu Return-Receipt-To: PEB@dm0mpi11.bitnet Date: 20 June 1987, 19:26:15 GMT From: Peter Breitenlohner (089) 31893-412 PEB at DM0MPI11 Max-Planck-Institut fuer Physik (Werner-Heisenberg-Institut) Foehringer Ring 6 D-8000 Muenchen 40 Subject: Re: Wolfgang Appelt's puzzle + General Remark Wolfgang Appelt has posed the following ``Puzzle for TeXhackers'' in TeXhax 87/47: > Develop a TeX macro \printhyphens{#1} which does the following > If your input is > The word hyphenation is hyphenated as \printhyphens{hyphenation} > your ouyput on paper should be > The word hyphenation is hyphenated as hy-phen-ation The definition \def\printhyphens#1{hy-phen-ation} obviously does just that but I'm sure that's not what he had in mind. This is such a nice puzzle because it first sounds so easy; isn't there a macro \showhyphens in plain! But then the idea used in \showhyphens doesn't seem to work. Thus I couldn't resist to cook up a solution which is below after this general remark. Some of us TeXhackers don't live in arpa-land but in earn/bitnet (as I do) or in XYnet. Since I certainly don't want to send a message from bitnet via arpa to bitnet (I wouln't even know how to do that) I would like to ask all TeXhax submittors to give their address in {\bf their} network(s), e.g. @. or similar. This allows us to use the most convenient path/gateway. The general idea is to first build a paragraph inside a \vbox with parameters set such that the `argument' is hyphenated as much as possible. This turned out to be the most difficult part.Probably not all of the parameters used below are necessary but I had to make sure that for the crucial ones I don't use some nonstandard values inherited from the environement.My actual solution uses some (fairly standard) \afterassignment/\aftergroup trickery in order not to treat the `argument' as an argument in the technical sense. \catcode changes inside the `argument' are therefore allowed (probably useless?). In a second step the \vbox is taken apart, the \hbox'es inside it are extracted and taken apart as well and the whole thing is put together in an \hbox. The basic idea of this can be found in the \TeXbook pages 398ff (\makefootnoteparagraph). Finally this \hbox is \unhbox'ed. The coding with \let\n@xt\... (don't use \next, this is used in \loop...\repeat) together with various \unskip/\unpenalty's ensures that \printhyphens{} acts exactly as {} does. Unfortunately \printhyphens{ } also acts as {} and not as { }, I was too lazy to fix that. The macro definitions are as follows: \catcode`\@=11 % use plain macros but be careful \def\printhyphens{\bgroup \afterassignment\pr@hyphens \setbox\z@\vbox} \def\pr@hyphens{\aftergroup\pr@@hyphens \hsize\z@ \hfuzz\maxdimen \leftskip\z@skip \rightskip\z@skip \parfillskip\z@skip \hyphenpenalty-\@M \doublehyphendemerits\z@ \pretolerance-\@M \finalhyphendemerits\z@ \noindent \hskip\z@skip} \def\pr@@hyphens{\setbox\z@\vbox{\global\setbox\@ne\null \unvbox\z@ \let\n@xt\relax \loop \setbox\z@\lastbox \unskip\unpenalty \ifhbox\z@ \global\setbox\@ne\hbox{\n@xt{\unhbox\z@\unskip\unskip \unpenalty}\allowbreak \unhbox\@ne}\let\n@xt\hbox \repeat}% \unhbox\@ne \unpenalty\unskip \egroup} \catcode`\@=12 Peter Breitenlohner ( peb@dm0mpi11.bitnet ) ------------------------------ Date: 18 Jun 87 09:02:00 EST From: "IAN EVANS" Subject: Address Correction - CANON LBP-8 Driver To: "texhax" Reply-To: "IAN EVANS" Regarding the announcement of the CANON LBP-8 DVI driver CANPRINT by Igor Metz (Dept. of CS, CH-Bern): The address given for all non-Europeans is incorrect. It should read The Wordworks The Boulevard City Walk Canberra, ACT 2601 <--- *** correction *** Australia Phone: 61-62-572893 Ian Evans (Yeah. I lived in Canberra for the last five years.) ------------------------------ Date: Sun, 21 Jun 87 18:19:57 MEZ From: Z3000PA%AWITUW01.BITNET@forsythe.stanford.edu Subject: LATEX for non-english languages To: texhax@score.stanford.edu As some of you may have noticed already, there exist several strange places on earth where people have the very strange habit, indeed, of speaking, writing, and even printing in lanuguages other than English. Now, here is a suggestion how LaTeX might be made useful for the poor people in those countries, too. Extensions to many more languages are encouraged and could be propagated via TEXHAX like this one. Let's make TeX and LaTeX a bit more international and cosmo-polite! % \adate, \ddate, \edate, \fdate redefine \today to use the Austrian, % german, english or french date format, resp. % \dcaptions, \ecaptions, \fcaptions switch to german, english or french % chapter captions etc. This will have an effect only % if the document style files use the symbolic names % \chaptername etc. instead of the original english words. \gdef\adate{\def\today{\number\day.c\ifcase\month\or J\"anner\or Feber\or M\"arz\or April\or Mai\or Juni\or Juli\or August\or September\or Oktober\or November\or Dezember\fi \space\number\year}} \gdef\ddate{\def\today{\number\day.c\ifcase\month\or Januar\or Februar\or M\"arz\or April\or Mai\or Juni\or Juli\or August\or September\or Oktober\or November\or Dezember\fi \space\number\year}} \gdef\edate{\def\today{\ifcase\month\or January\or February\or March\or April\or May\or June\or July\or August\or September\or October\or November\or December\fi \space\number\day, \number\year}} \gdef\fdate{\def\today{\number\day\space\ifcase\month\or janvier\or f\'evrier\or mars\or avril\or mai\or juin\or juillet\or ao\~ut\or septembre\or octobre\or novembre\or d\'ecembre\fi \space\number\year}} % Here is, how you can modify the LATEX document style files and option % files, to benefit from the following \xcaptions commands. Lines like % \def\tableofcontents{\section*{Contents\markboth{CONTENTS}{CONTENTS}} % \@starttoc{toc}} % should be replaced by lines like % \def\contentsname{Contents} % <--- % \def\tableofcontents{\section*{\contentsname % \markboth{\uppercase{\contentsname}}{\uppercase{\contentsname}}} % \@starttoc{toc}} % and of course, you should modify the change date in the file header and % in the \typeout command. \gdef\dcaptions{ \def\refname{Literatur} \def\abstractname{Zusammenfassung} \def\bibname{Literaturverzeichnis} \def\chaptername{Kapitel} \def\appendixname{Anhang} \def\contentsname{Inhaltsverzeichnis} \def\listfigurename{Abbildungsverzeichnis} \def\listtablename{Tabellenverzeichnis} \def\indexname{Index} \def\figurename{Abbildung} \def\tablename{Tabelle} \def\partname{Teil}} \gdef\ecaptions{ \def\refname{References} \def\abstractname{Abstract} \def\bibname{Bibliography} \def\chaptername{Chapter} \def\appendixname{Appendix} \def\contentsname{Contents} \def\listfigurename{List of Figures} \def\listtablename{List of Tables} \def\indexname{Index} \def\figurename{Figure} \def\tablename{Table} \def\partname{Part}} \gdef\fcaptions{ \def\refname{R\'ef\'erences} \def\abstractname{R\'esum\'e} \def\bibname{Bibliographie} \def\chaptername{Chapitre} \def\appendixname{Appendice} \def\contentsname{Table des mati\`eres} \def\listfigurename{Liste des figures} \def\listtablename{Liste des tables} \def\indexname{Index} \def\figurename{Figure} \def\tablename{Table} \def\partname{Partie}} Hubert Partl Technical University of Vienna Austria (W.Europe) ------------------------------ Date: Sun, 21 Jun 1987 23:56 PDT From: GFA001K%CALSTATE.BITNET@wiscvm.wisc.edu Subject: Oversized proof sheets To: texhax@score.stanford.edu I recently wrote a paper for a British conference that required the large format proof sheets that seem to be causing others so much trouble. I was able to solve my problem very easily by noting that the actual printing area on the sheet was smaller than a 8.5 x 14 inch (i.e. legal size) sheet of paper. All I did was to use some negative horizontal and vertical offsets, and give TeX the correct page lengths and widths and all was well. Actually, in my case, I just use a negative horizontal offset because the dvi driver I use blew up on the negative vertical offset for some reason. In any event, print the document on legal size paper, and then just paste it onto the large proof sheets. The publisher loved the way it looked! Brad Finney Humboldt State University gfa001k@calstate.bitnet ------------------------------ From: BELL%KUPHSX@STAR.STANFORD.EDU Subject: Repeat offering of AutoLetter and LN03 driver. To: STAR::"texhax@score.stanford.edu"@KUPHSX.SPAN I have received a number of requests for both my AutoLetter and LABELS macros(cf. TUGboat V8, #1 or TeXhax V87, #'s 24 and 30), but also for my modified version of the Rose LN03 driver(cf. TeXhax V87, #44). I have (I believe) answered all requests, but apologize if you have been overlooked. Our BITnet link has been a bit flaky of late and your message may have gone undelivered. As a result, I am reiterating my earlier offers and providing those of you who may have had troubles with some alternate routes to send mail to me should others fail. Ed Bell Dept. of Physics and Astronomy University of Kansas ARPANET: Bell%KUPHSX.SPAN@128.8.250.4 or Bell%KUPHSX.SPAN@JPL-VLSI.ARPA or Bell%KUPHSX.SPAN@STAR.STANFORD.EDU BITnet: Bell@UKANVAX or Bell%KUPHSX.SPAN@SU-STAR.ARPA SPAN: KUPHSX::Bell ------------------------------ Date: 22 Jun 87 12:31:00 EDT From: "FALCON::NIELAND" Subject: Missing fonts for the LN03 To: "texhax" Reply-To: "FALCON::NIELAND" Does anyone know where I can get the line and circle fonts for the LN03? I have the compiled CM fonts that work, but I don't have the line and circle fonts and I have a need for them. Also, we've been hearing about this new DVI2PS driver in the public domain, but where can we can a copy? Is it available on the ARPANET? Ted Nieland TNIELAND@WPAFB-AAMRL.ARPA NIELAND%FALCON.DECNET@WPAFB-AAMRL.ARPA Dayton, Ohio (513) 255-5156 ------------------------------ Date: Mon, 22 Jun 87 18:41:46 n To: TEXHAX@SCORE.STANFORD.EDU From: Subject: ytex -> plain tex As one path to follow in getting some documentation printed for Scheme, does anyone have a conversion program to run a YTeX source file on the standard Plain TeX processor ? Immediate aid would be appreciated... paul davis bitnet: davis@embl arpa: davis%embl.bitnet@wiscvm.wisc.edu uucp: ...!psuvax!embl.bitnet!davis ps: OR EVEN - something to simply process a YTeX source file directly ? ------------------------------ Date: Mon, 22 Jun 87 11:45 EST From: WAMPLER%gmr.com@RELAY.CS.NET To: TeXHax@SCORE.STANFORD.EDU Subject: 11x14 camera-ready conference papers Here's one more way to produce 11x14 camera-ready conference papers that's easier than pasting up columns and works on 8.5x11 printers. Simply modify the output routine to print out each page TWICE in landscape mode: once with the normal voffset (usually 1in), and once shifted up by 5.5in as follows. \voffset=1in \shipout\copy\printpage \voffset=-4.5in \shipout\box\printpage \advancepageno etc. If the printing were perfect, the two pages could be overlapped and taped together to reconstruct the entire mat page. On the printer I use, the edges fade and distort enough to make that approach unattractive, so I trim one page first before attaching them. Since there is a 3 inch overlap, I can usually make the cut at a paragraph break or at a displayed equation which avoids the problem of making an accurate baseline skip at the seam. A benefit of printing the original in the large size is that the final image will be sharper with an effective resolution of nearly 400 dpi for a 300dpi printer. (Your figures will look better too!) This approach requires a printer that can handle landscape mode and that discards any letters printed off the page. Charles Wampler ------------------------------ Date: Sun, 21 Jun 87 09:31:45 +0300 From: Carol Weintraub Subject: Tex on the MacIntosh or Sun Workstation To: texhax@score.stanford.edu Dear TeX Community, We have been using TEX now for 5 years at the Weizmann Institute on the mainframe computer (IBM). Lately, our computer is very heavily overloaded and we are checking out options of running TEX independently of the "long-waiting queue". The MacIntosh has an incredible (EASY) user interface and one is able to SEE the output file with easy access for correcting after running TeX. It promises other plusses, such as the ability to imbed graphics (and pictures) into your files, from their MacDraw, MacPaint or CricketDraw packages. The MacIntosh can be used as a monitor of the mainframe for sending and receiving messages, e-mail, etc. or can be run independently. I would like to ask a few questions. 1. The version we received here is called TEXtures (preliminary version 0.9). I wanted to know if this is the compatible version to TEX v.1? It seems to me that a lot of relevant information is still missing, such as how to implement pictures etc. 2. Since we have nobody to ask in Israel (the MacIntosh people just heard of TEX because of us!) does one have to run a TEX file under the TEXtures icon? On the IBM there is a file name and a file TYPE. On the Macintosh, there is just a file name. How does the MacIntosh know that this is a TEX file and not a MacWrite file etc? 3. We received Texfonts (very few indeed). Are there all the CM fonts available for the MacIntosh? We use boldface and math extension fonts a lot here, are they available? We seemed to have received only cmr, cmmi, cmsy and cmsans. There are no magnifications for these fonts bigger than 10 point. Is this considered the standard package of fonts? 4. I transfered my TEX files from the IBM onto the MacIntosh and came across a peculiar bug. When editing my TEX file (after running typeset within the TEXtures mode), I wanted to save changes made to my source file and found that I I couldn't. The Mac claimed that I couldn't save changes to a file of a different type. How could I tell the MacIntosh that this was not a MacWrite document, but rather a TEX document? 5. Finally, is there a way to print a file on the MacIntosh and be able to work on something else while the file is being printed? We have the MacIntosh hooked up (temporarily) to a dot matrix printer and it took "forever" to print one page of output. This is a BIG drawback for us. I'm sure there is a way that enables one to print while working on something else (we can do it here on the IBM by running batch mode). I would also like to know if there is anybody out there using TEX on the MacIntosh II. Is there a full version of TEX (V.2 with ALL the CM fonts)? How are the color features? How fast does one receive his output? (How many pages per minute). I have also just heard (thru the TUGboat) of a new system "The Publisher" from Arbortext which interacts with TEX on a Sun Workstation. Is anybody out there using this? I understand one can edit his output file on the screen and the corrections will be saved in the DVI file. If anybody could advise me on either of these two systems/machines, please write to: Carol Weintraub, Dept. of Applied Math. & Computer Science The Weizmann Institute of Science Rehovot, 76100 Israel Bitnet: maweintr@weizmann Arpanet: maweintr%weizmann.bitnet@WISCVM.ARPA.WISC.EDU Thank you very much! Carol ------------------------------ Date: Mon, 22 Jun 87 10:55:22 PLT From: Dean Guenther Subject: Dubious WEAVE behavior under VM/CMS To: TeXhax Digest Don, I have noticed it too. Perhaps a true fix is in order, but until then you can try what I've been using. I define a macro called ccat which is used in place of || and will both tangle and weave properly. @ The macro ``ccat'' is used to concatenate using a double vertical bar. @d ccat==@t\hskip2em@>@=||@>@t\hskip2em@> ------------------------------ Date: Mon, 22 Jun 87 19:53:41 PDT From: dorab@CS.UCLA.EDU (Dorab Patel) To: texhax@score.stanford.edu Subject: TeX server? we are thinking of running TeX on a "server" and having all TeX jobs on other machines (hopefully transparently) actually run on the server. has anyone already done this that would be willing to share experiences? offhand, it seems rather difficult to do if you use BiBTeX or \includeonly in LaTeX. all i can think of is to rcp all the relevant (... this would be hard to determine automatically ...) files over to the server and then rcp them back when TeX was done. by the way, this would be between Un*x machines without NFS or some such network file system. please respond via mail ... i'll summarize if necessary. thanks 'dorab dorab@cs.ucla.edu {sdcrdcf,ucbvax,randvax}!ucla-cs!dorab ------------------------------ Date: Tue, 23 Jun 87 01:52:47 EDT From: Bill Kaster To: Texhax@score.stanford.edu Subject: tree macros Hideki Isozaki asks about macros for producing tree structures. Such a package was being distributed by Dan Zurin (ZAR @ CITCHEM.BITNET). Send some mail for the macro but beware that he may be on summer break. ------------------------------ %%% %%% subscriptions, address changes to: texhax-request@score.stanford.edu %%% %%% submissions to: texhax@score.stanford.edu %%% %%% BITNET redistribution: TEX-L@TAMVM1.BITNET (list server) %%% %%%\bye %%% ------------------------------ End of TeXhax Digest ************************** -------