TeXhax Digest Monday, May 23, 1988 Volume 88 : Issue 49 [SCORE.STANFORD.EDU]TEXHAX49.88 Moderator: Malcolm Brown Today's Topics: Wanted: Info on 'IdxTeX', automated index generation for LaTeX Problems with Canon LBP8II dr Re: TeXhax Digest V88 #45 Two-sided documents in LaTeX Re: underlining; problem with nested footnotes ? BibTeX Style File (.bst) wanted for Annotated Bibliographies ? RE: Displaying text within large square brackets BibTeX 0.99c is a big win! announcement in TeXHaX of start of Dutch Users Group CMS changes for BibTeX Re: TeXhax Digest V88 #46 (LaTeX notes) RE: TeXhax Digest V88 #45 Expanding Tex and Latex memory Wanted: Info on 'IdxTeX', automated index generation for LaTeX LaTeX font set A problem with LaTeX re: David F. Rogers's message, V88 #47 TransFig Version 1.4 Available Spanish hyphenation patterns psfig/tex TeXhax Digest V88 #47 ---------------------------------------------------------------------- Date: Mon, 16 May 88 07:16:48 CDT From: shell!rgh@Sun.COM (Richard G. Hash) Subject: Wanted: Info on 'IdxTeX', automated index generation for LaTeX In TUGboat, Volume 8 (July 1987), No. 2, the program IdxTeX is described as an automated index generation for LaTeX from .idx files. It has been distributed to the TeX Users Group and to the DECUS library, since it was written for VAX/VMS. Has anyone out there got this running on a Sun? (I've got a 3/50). I only read the group periodically, so please mail directly. Thanks, ====================================================================== Richard G. Hash Shell Oil Company, Bellaire Research Center (713) 663-2311 ...!{sun,rice,psuvax,ut-sally,ihnp4,soma}!shell!rgh rgh@shell.com ------------------------------ Date: 05/11/88 1732 From: Subject: Problems with Canon LBP8II dr Hello, I'm doing a period of probation in the "Institut National Agronomique Paris-Grignon" in Paris (France). TeX/LaTeX has been installed, and works very well (controled by several means) and I'm in charge to install the DVI driver for a Canon LBP8II (not LBP8A2) laser printer, on our Unix system. Two kinds of DVI program have been received from the LISTSERV -at DHDURZ1.BITNET : DVICAN.C from BEEBE and DVICA2.C from PEKKA PIETILAINEN (TFYS-PP.FINOU). Both DVICA*.C can be compiled after some changes in the makefile.unx as well as in machdefs.h, using 7 or 8 bits option. Our LPB8II is connected to the Unix computer via a V24 serial line but through a serial/parallel converter (for an unknown reason the computer is unable to receive XON/XOFF (or others) signal from the LBP8II, which serial/parallel converter does). * USE of DVICAN (7 or 8 bits option) : ================================== The text is printed but : - All roman letters are cut by vertical "white" (= without dots) bands. Such a problem does not to seem to exist using sans serif letters. - Two letters (roman capital M and N) are cut, at the top, by an horizontal "white" line. - Moreover when a N appears in the text, the laser printer stops to print the current page and begins to print the rest one on the next page. - Finally the letters (mainly roman) doesn't look very dark (resolution lower than 300 dpi or something like that?). Faced to these problems we are trying to use DVICA2.C which is included in the BEEBE's DVI package. * USE of DVICA2 (7 or 8 bits option) : ================================== - Use of the testpage.TEX and .DVI file resulted in : ------------------------------------------------- . No horizontal nor vertical straight lines. . No numbers. . Some letters (W g cc W g ck and dots) in place of the text of the minipage. . Resolution looks to be better than with dvican.c but vertical "white" lines in the roman letters are still present. . A lot of letters are lacking. - Use of an other .TEX and .DVI resulted in : ----------------------------------------- . Letters cut by vertical "white" lines. . A lot of letters are lacking. . N and M capital letters are cut by an horizontal line and N cut the printed text on two pages. Thus as you can understand I have a lot of problems. As the Institute where I'm working doesn't have Unix computer people (and mainly C programming and hardware people) I'm a little lost. Could you help me? I need some precisions on : ========================= - What kind of connection are to be used : parallel or serial (which configuration : 7 or 8 bits, XON/XOFF, ...)? - Which is (are?) the file(s) concerned by the vertical lines? - Why are, and only these one, the roman N and M cut by horizontal line followed by a page ejection? Is it a problem with the DPI? All informations or files are welcome. Thanks a lot. Your's sincerely. Yves BERTHEAU Please send mail directly to the following address : (as well as a copy to TEXHAX) EARN/BITNET : BERTHEAU.FRINRA72 ------------------------------ Date: Mon, 16 May 88 16:51:57 PDT From: lamport@src.dec.com (Leslie Lamport) Subject: Re: TeXhax Digest V88 #45 In response to Michael J. Porter's query about the VMS manuals. They are produced by a system that has been used inside Digital for a while and is now available as a product called "Document"--see your local DEC salesperson. I have spoken to the people who wrote Document and they seemed to be taking a very reasonable approach. However, I have not used the system myself, so I don't know how good it is. Leslie Lamport ------------------------------ From: wu@shade.STANFORD.EDU (Kevin Wu) Subject: Two-sided documents in LaTeX Date: Mon, 16 May 88 20:33:03 PDT When I switch my LaTeX document style from the default of one-sided to two-sided, I get warnings on several pages of the type: Underfull \vbox (badness 10000) has occurred while \output is active. I don't get this warning for the one-sided document style. For the one-sided case, LaTeX uses the normal spacing between chapter and section titles and paragraphs. Then it leaves some space at the bottom of the page when it can't fit the next item (say, a big matrix or section heading) at the bottom. For the two-sided case, LaTeX puts the last item that fits on a page at the bottom and stretches the vertical spaces between items. Then it complains about the underfull \vbox. I think that this behavior is inconsistent. Is there anything that I can do to get the two-sided case to function like the one-sided case? Details: TeX, Version 2.7 for SUN 3.4 UNIX (Pascal), LaTeX Version 2.09 <15 Dec 1987> Document Style `report' <12 Oct 87>. \documentstyle[twoside,12pt,suthesis]{report} -- Kevin Wu ------------------------------ Date: Tue, 17 May 88 05:52:22 EDT From: Chris Torek Subject: Re: underlining; problem with nested footnotes Ken Hill writes: >Certain legal documents are required to use underlined text, for >blocks of up to paragraph size. ... >Thus: how can I underline a large block of text (up to a paragraph) > properly in normal paragraph mode? Most likely the `requirement' is a holdover from the inability to italicise with most typerwriters. Lawyers being unusually stubborn creatures, however, you may not be able---or even desire---to convince them that italics is proper. So: What you need is an underlined font. I have no idea whether any such thing exists, but it would probably not be terribly difficult to muck about with the Computer Modern METAFONT files and come up with one. Steve Kelem writes: >Subject: Problem with nested footnotes > >...the intermediate form IVAN% >\footnote{SVIF stands for Standard VHDL% >\footnote{VHDL stands for VHSIC% >\footnote{VHSIC stands for Very High Speed Integrated Circuits} >Hardware Description Language} >Intermediate Format} is ... > >The resulting footnote looks like: > >1 SVIF stands for Standard VHDL(2) Intermediate Format >4 another footnote > >So the footnotes about VHDL and VHSIC are missing. >Is there a clean way to fix this? The best way to fix it is not to do it. Nested footnotes are an Official Typesetter's No-No. Speaking as an editor, I would rewrite this as IVAN\footnote{SVIF stands for Standard VHDL Intermediate Format, where VHDL stands for VHSIC Hardware Description Language, and VHSIC for Very High Speed Integrated Circuits.} or similar. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris ------------------------------ Date: Tue, 17 May 88 11:30:34 EDT From: csrobe@icase.arpa (Charles S. Roberson) Subject: ? BibTeX Style File (.bst) wanted for Annotated Bibliographies ? I appologize if this isn't the correct place to post this request, but I don't know who else to ask. We are in need of a BibTeX style file that allows for annotated bibliographies. I checked in our local btxbst.doc and it appears as if someone started to incorporate the annotated code but then stopped and commented it out. Our version of btxbst.doc is 0.98c -- is there a newer version, or could someone please send me a copy of a style file that does annotated bibliographies? Many many thanks, -chip +-------------------------------------------------------------------------+ |Chip Roberson ARPANET: csrobe@icase.arpa | |1105 London Company Way BITNET: $csrobe@wmmvs.bitnet | |Williamsburg, VA 23185 UUCP: ...!uunet!pyrdc!gmu90x!wmcs!csrobe| +-------------------------------------------------------------------------+ "One world is enough, for all of us..." - The Police. ------------------------------ Date: Tue, 17 May 1988 11:25 EDT From: Jim Walker Subject: RE: Displaying text within large square brackets In TeXhax88 vol. 45, Peter Flynn asks about displaying a paragraph of text within square brackets produced using \left and \right in display math mode. The reason that \vbox didn't work is that \vbox creates a box whose baseline is near the bottom, whereas \left and \right are designed to work with things that have more or less centered baselines. The solution is to use \vcenter, as in the following example. $$\left[\vcenter{\hsize=2in \raggedright \strut There's a lady who's sure all that glitters is gold, and she's buying a stairway to heaven. When she gets there she knows if the stores are all closed, with a word she can get what she came for.\strut}\right]$$ -- Jim Walker, Dept. of Math., Univ. of S.C. ------------------------------ Date: Tue, 17 May 88 11:13:31 CDT From: William LeFebvre Subject: BibTeX 0.99c is a big win! YAHOO! (no, I'm not a Texan, but I do live there) I can FINALLY cite papers that appear in things like the "Lecture Notes in Mathematics" series. I used to have to stand on my head and pull a few tricks in the "organization" field to get it to come out right. But the new BibTeX lets me do it the right way. Take for example Haore's often cited paper "Procedures and parameters: an axiomatic approach". The problem is that it is a paper in a book, the book has it's own title but it is also volume 188 in the LNM series. I could not find a way to generate a satisfactory bibtex entry under 0.98. But in 0.99, "incollection" will actually do something with the "volume" and a "series" fields. Problem solved. In fact, cross-referencing makes it even easier to do all this. Thanks Mr. Patashnik! BibTeX is now a much more useful tool. William LeFebvre Department of Computer Science Rice University ------------------------------ Date: Wed, 18 May 88 16:45 N From: Subject: announcement in TeXHaX of start of Dutch Users Group Subject: Dutch TeX Users Group Nederlandse TeX-gebruikersgroep. Op 23 juni wordt er in Groningen een Nederlandse afdeling van de TeX Users Group opgericht. De bedoeling van deze gebruikersgroep is ervaringen uit te wisselen en samen te werken op het gebied van electronisch publiceren via (La)TeX op de korte termijn. Nadere informatie en opgave voor deelname: C.G. van der Laan Rekencentrum RUG Landleven 1, 9700 AV Groningen 050-633374/3440 EARN: cgl@hgrrug5 DECnet: rugr::cgl telefax: 050-633406 G.J.H. van Nes ENR Technisch wetenschappelijk rekencentrum bv. Westerduinweg 3, 1755 ZG Petten NH 02246-4505 DECnet 19505::vannes ------------------------------ Date: Wed, 18 May 88 12:18:14 CDT From: Don Hosek Subject: CMS changes for BibTeX Has anybody created a CMS change file for BibTeX v.0.99c ? -dh ------------------------------ Date: Wed, 18 May 88 10:35:09 PDT From: lamport@decwrl.dec.com (Leslie Lamport) Subject: Re: TeXhax Digest V88 #46 (LaTeX notes) Paul Davis writes requesting help in creating a document style for his Local Guide. I want to commend him on two accounts: putting effort into creating a good Local Guide (there are people SELLING LaTeX without providing any Local Guide), and for consulting with more knowledgeable people when designing a style. As for his remark I have to say that I think that the PostScript manuals are the only books I've seen that have been done with `our-type' of computer typesetting that I find pleasing to the eye, and TeX didn't even get a look in... I think that one can't draw any conclusions by comparing different kinds of books. For example, you can't fault a graduate-level math text because it's not as eye-catching as a grammar-school arithmetic text. Publishers sell more grammar-school texts and are willing to put a lot more effort into their production. Since there probably aren't any writers of grammar-school texts using TeX, the only examples of TeX you tend to find are graduate-level texts. There's no good reason why TeX-produced advanced texts shouldn't be as good-looking as traditionally typeset ones. Good typography is largely a matter of economics. Manual methods, applied by skilled artisans, will always produce a better result than automatic tools. They're just more expensive, so the highest quality typesetting is justifiable only for best sellers. Unfortunately, instead of using TeX to produce better books for the same price or at least books that are as good for cheaper, many publishers are using it to produce even worse quality dirt cheap. I saw one book done with TeX--a regular, hardcover statistics book that I think was published by Wiley--that appears to have been phototypeset from 300 dot per inch laser printer output. If publishes are willing to accept any camera-ready copy, and authors are left to their own devices, the results are bound to be pretty bad. Meanwhile, back to Davis' question. He seems to say that he has "kludged" most everything he needs. I suspect that the more he uses TeX the more satisfied he will be with "kludges". My observation has been that what Knuth considers an elegant solution other people would consider a kludge. It's easy for purists to rail against Knuth for his "bad taste", but it's not so easy to find really practical alternatives. A working kludge is a lot more useful than an elegant paper design. The only thing Davis mentioned that he seems to be lacking is "proper" table-of-contents entries for sections. It's easy for his macros to produce these entries with the \addcontentsline macro, so I don't understand his problem. Anita Hoover writes Is there a simple solution to getting a large left parenthesis ({) preceding a multilined numbered equation? Something like this large { surrounding y = 2ab + c (12) a = 4b (13) b = 25 (14) c = 5b (15) There's an easy way to produce a single such multiline equation. * First, I assume that you know how to use an eqnarray environment to produce the desired equation with a small `{' at the left of the first equation. * Next, I assume that you can figure out how to make a very big `{' all by itself. (One way is something like \(\left\{ \rule{0pt}{2in}\).) * The next problem is to replace the small `{' by the big one, but to make TeX typeset everything the same as if the small one were still there. This is done with the \raisebox command. * Finally, you'd better make sure that TeX doesn't try to break the page in the middle of this set of equations. Use the \samepage declaration. It's a bad idea to put these kinds of formatting commands in the text. The best approach--especially if you have several such sets of equations--is to define some commands and environments to do what you need. For example, you might define a new environment that's the same as eqnarray but prevents page breaking. (The new environment is, of course, defined in terms of eqnarray and \samepage.) You'll also need to define a command \bigbrace, so that \bigbrace{7} produces a brace that surrounds a seven-line eqnarray. Leslie Lamport ------------------------------ Date: Wed, 18 May 88 11:38:50 PDT From: parmenter%wrongo.DEC@decwrl.dec.com Subject: RE: TeXhax Digest V88 #45 The VAX VMS manuals are produced using a production system called VAX DOCUMENT. It does indeed use TeX as its engine, and no the macros are not currently available. The basic features of VAX DOCUMENT are a generic markup language which serves as the front end to TeX, a modified version of TeX, device converters (LN03, PS, and mono-spaced output are currently supported), a pretty good indexer, a nice bookbuilding tool, an LSE interface to the markup language. You can perform limited modifications to the doctypes, changing fonts, numbering styles, fooling around with running footers and headers etc. We are moving toward SGML compliance. The tool was originally developed for in-house use, and we only recently decided to market it. It has been used for VMS documentation for a number of years, and is being used by many if not most of Digital's software documentation. If you would like more information contact a digital sales rep. David Parmenter Digital Equipment ------------------------------ Date: Wed, 18 May 88 12:25:21 PDT From: hildum@iris.ucdavis.edu (Eric Hildum) Subject: Expanding Tex and Latex memory I am currently using the Kellerman and Smith version of TeX and LaTeX on a VAX/VMS system(version 4.5). Recently, I have begun some work on figures using the pictex figure drawing package, and have discovered that I am starting to use large amounts of memory (eg, 80 to 90 percent of the memory). I would like to expand the amount of memory available, but have run into the note that mem_max must be strictly less than max_halfword. I know that at one time the UNIX Pascal compiler was limited to 16 bit values for the indexes in arrays - is this the reason for the note? What are the real limits (eg, hidden limits in the code, assumed compiler limits, etc.) that I need to worry about? (I did check the back issues of TeXhax, but did not find any references - and the powers that be have decided that we will not receive the Tugboat). Eric ------------------------------ Date: Fri, 13 May 88 14:10:16 CDT From: ihnp4!shell!rgh@EDDIE.MIT.EDU (Richard G. Hash) Subject: Wanted: Info on 'IdxTeX', automated index generation for LaTeX In TUGboat, Volume 8 (July 1987), No. 2, the program IdxTeX is described as an automated index generation for LaTeX from .idx files. It has been distributed to the TeX Users Group and to the DECUS library, since it was written for VAX/VMS. Has anyone out there got this running on a Sun? (I've got a 3/50). I only read the group periodically, so please mail directly. Thanks, Richard G. Hash Shell Oil Company, Bellaire Research Center (713) 663-2311 ...!{sun,rice,psuvax,ut-sally,ihnp4,soma}!shell!rgh rgh@shell.com ------------------------------ Date: Tue, 17 May 88 18:24:34 PDT From: Kent_Wada@mtsg.ubc.ca Subject: LaTeX font set In Personal TeX's latest PcTeX distribution (2.1), the lfonts.tex file for LaTeX defines a handful of fonts at 12pt and higher to be design-size fonts, in contrast to the previous version, which consistently used magnified fonts at sizes 11pt and higher. For example, cmr12 is now used instead of cmr10 scaled\magstep1. I would greatly appreciate it if someone could tell me if the use of design-size fonts at 12pt and higher represents a universal change to the font set all `standard' LaTeXs use, or if it is a `local' change made for PcTeX only. (We don't have Internet FTP capabilities, and can't check this easily.) What is the reason behind this change? Aesthetics of design-size versus magnified fonts? Is there an algorithm to decide which fonts at which sizes are design-size, and which are magnified? Kent Wada Computing Centre, The University of British Columbia ------------------------------ Date: Thu, 19 May 88 13:04 EET From: TIMOSUHONEN%JYLK.JYU.FI@forsythe.stanford.edu Subject: A problem with LaTeX I'm writing a brief finnish summary of LaTeX and now I have a BIG problem. I'd like to have a macro to produce same kind of examples as is in LaTeX- book: This is how it looks This is how it is written when printed. into the .TEX-file The usage might be something like \example{\( x~2 = 4 \)} and the output 2 x =4 \( x~2 = 4 \) I have no problems with the left part but (and that is a BIG one) I have no idea how to work with the right part. Is there anyone who can help me? Thanks, Timo Suhonen INTERNET: TIMOSUHONEN@JYLK.JYU.FI ------------------------------ Date: Thu, 19 May 88 09:03:11 EDT From: berman@edsel.siemens.com ( A. Michael Berman ) Subject: re: David F. Rogers's message, V88 #47 >However, if >he chooses to remain involved, then he must answer each and every question: >simple, stupid, intelligent, or interesting completely, in detail and >politely. >If he does not want to do this, then I for one suggest that he adopt the >first choice. Please allow me to politely disagree with Mr. Rogers. I am very interested in Mr. Lamport's comments, even if the tone may offend someone. When did he agree to answer each and every question? Let him answer the questions that he wants to answer, and hopefully the rest of us will pitch in and tackle the easy ones. A. Michael Berman Siemens Research and Technology Labs 105 College Road East Internet: berman@siemens.com Princeton, NJ 08540 Usenet: {allegra,princeton}!siemens!berman 609/734-3325 ------------------------------ Date: Thu, 19 May 88 09:16:16 EDT From: beck@svax.cs.cornell.edu (Micah Beck) Subject: TransFig Version 1.4 Available Release 1 of TransFig Version 1.4 is now available for anonymous FTP from svax.cs.cornell.edu as transfig.tar.Z. TransFig Version 1.4 is compatible with Version 1.4 of the Fig graphics editor and is also backward compatible with Fig 1.3. TransFig is a package for translating figures from Fig code (which is produced by the Fig graphics editor) to other graphics languages: PiCTeX and PostScript. It also provides a convenient mechanism for integrating such figures with TeX. Also included is a program which translates the PIC graphics language into Fig code. The TransFig manual has been expanded to include a detailed description of Fig code as a graphics description language. This reference guide should enable graphics tool designers to generate TransFig-compatible Fig code, and thus achieve convenient integration with TeX. Fig Version 1.4 is available for anonymous FTP from sally.utexas.edu. Fig runs on Sun workstations under the Suntools windowing system. The TransFig distribution is quite Unix-dependent, although it can be ported. Users without access to Arpanet FTP can contact me for mail distribution (using tar, compress, and btoa). In Europe and Australia, please contact the following people who have agreed to serve as redistribution points: shapiro@inria.inria.fr France sjl@uk.ac.ukc UK mjj@mimr.dmt.oz Australia Finally: I'm collecting nice examples of TransFig figures to put into the documentation. If you'd like to contribute one, please send me the Fig file. Micah Beck beck@svax.cs.cornell.edu Dept of Computer Science Cornell University ------------------------------ Date: Thu, 19 May 88 14:24 GMT From: Subject: Spanish hyphenation patterns Does anybody know where could I get the hyphenation patterns for Spanish? Thanks in advance Goncal Badenes Centre Nacional de Microelectronica Bellaterra, Spain INFORMA@EB0UAB51.BITNET ------------------------------ Date: Thu, 19 May 88 09:32:17 EDT From: Mike DeCorte Subject: psfig/tex Does anyone have a copy of Stephan Bechtolsheim's dvi2ps that is compatible with psfig/tex? According to the README of psfig/tex, Stephan Bechtolsheim has made the changes, but I have not been able to reach Stephan Bechtolsheim and l.cc.purdue.edu:/pub is empty. thankyou Michael DeCorte // (315)268-3704 // P.O. Box 652, Potsdam, NY 13676 Internet mrd@clutx.clarkson.edu // Bitnet mrd@clutx.bitnet ------------------------------ Date: Thu, 19 May 88 08:33:19 PDT From: mackay@june.cs.washington.edu (Pierre MacKay) Subject: TeXhax Digest V88 #47 Is the LN03R a write-white or a write-black device? If it is a write-white device you really need to start with an adjusted font_setup. I sent this out through TeXhax a while ago, and probably ought not to clog up the communications lines with it again. It is small enough to mail. More information can be found in recent issues of TUGboat, where there is a regular feature on mode_def settings. Email: mackay@june.cs.washington.edu Pierre A. MacKay Smail: Northwest Computing Support Group TUG Site Coordinator for Lewis Hall, Mail Stop DW10 Unix-flavored TeX University of Washington Seattle, WA 98195 (206) 543-6259 ------------------------------ %%% %%% Concerning subscriptions, address changes, unsubscribing: %%% BITNET: send a one-line mail message to LISTSERV@TAMVM1.BITNET: %%% SUBSCRIBE TEX-L % to subscribe %%% %%% All others: send mail to %%% texhax-request@score.stanford.edu %%% please send a valid arpanet address!! %%% %%% %%% All submissions to: texhax@score.stanford.edu %%% %%%\bye %%% ------------------------------ End of TeXhax Digest ************************** -------