Date: Fri 22 May 87 17:42:25 PDT Subject: TeXhax Digest V87 #39 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 Friday, May 22, 1987 Volume 87 : Issue 39 [SCORE.STANFORD.EDU]TEXHAX39.87 Editor: Malcolm Brown Today's Topics: Comment environment for LaTeX raggedright in section headings? TeXhax Digest V87 #36 Re: TeX: The Movie dvi -> ps including Macintosh drawings Re: Latex comment facilities CMS Distribution Tape latex "remark" environment really really lowres metafont output Re: Help with large LaTex tables... ~~~~~~~~VorTeX... bug in texindex ---------------------------------------------------------------------- Date: 13 MAY 87 15:00:01.56-GMT From: RADFORD@FRGAG51.BITNET To: TEXHAX@SCORE.STANFORD.EDU Subject: MacMETAFONT caveat emptor Date: 13-MAY-1987 14:57:01.33 From: RADFORD@FRGAG51 To: texhax@score.stanford.edu Subj: MacMETAFONT caveat emptor The implementor of MacMETAFONT (texhax 87.33), Mr. Ostromoukhov, is asking $200 for his package. Thought people would like to know before writing him. Simon Radford ------------------------------ Date: Wed, 13 May 87 06:44:37 PDT From: KARNEY%PPC.MFENET@nmfecc.arpa To: TeXhax@Score.Stanford.EDU Subject: Comment environment for LaTeX Here is a comment environment for LaTeX obtained by modifying the definition of the verbatim environment. This is useful for commenting small pieces of text (up to a few paragraphs). You'll exceed TeX's memory if you try to comment larger pieces of text. You can't nest comments. %% Comment enviroment \begingroup \catcode `|=0 \catcode `[=1 \catcode`]=2 \catcode `\{=12 \catcode `\}=12 \catcode`\\=12 |long|gdef|@xcomment#1\end{comment}[|end[comment]] |endgroup \def\@comment{\begingroup \let\do\@makeother \dospecials} \def\comment{\@comment \@xcomment} \def\endcomment{\endgroup} Charles Karney MFENET: Karney@PPC.MFENET ARPANET: Karney%PPC.MFENET@NMFECC.ARPA BITNET: Karney%PPC.MFENET@ANLVMS.BITNET ------------------------------ Date: Wed, 13 May 87 10:06:30 EDT From: gil@svax.cs.cornell.edu (Gil Neiger) To: texhax@score.stanford.edu Subject: raggedright in section headings? I'm preparing a document in twocolumn mode, and am finding that many of my section end up being about a column and a half wide. As a result, the first line of these headings ends up being stretched out a lot, yielding very underfull hboxes. Is there any way I can modify \@startsection or something like that so that just the section heading is raggedright? I've tried a number of things, but nothing seems to work properly (i.e., leaves the rest of the text right justified, and doesn't destroy the section* commands). - Gil ------------------------------ Date: Wed, 13 May 87 10:14:18 EDT From: Charlie Martin To: TeXhax@score.stanford.edu Subject: TeXhax Digest V87 #36 On the proof environment David Chase asked about -- I simply build a new environment with {\bf Proof} before the text, and either a framebox blob or a little box from mathmode at the end. It stays in the last font, and otherwise seems to look fine. ------------------------------ Date: 13 May 1987 11:21:21 EDT From: 00e3 brian utterback Reply-To: To: texhax%su-score.stanford.edu@umn-rei-uc.arpa Subject: Re: TeX: The Movie In reply to William LeFebvre musing about the movie version of TeX in TeXHaX 34.87 I would like to point out that it has already been done. Specifically, the movie "Tex" starring Matt Dillion from the story by S.E. Hinton. I have not seen it, but I suspect that the screenplay differed somewhat from Knuth's version. :-) Brian Utterback Cray Research Inc. ------------------------------ Date: Wed, 13 May 87 16:32+0100 From: Ralph Subject: dvi -> ps including Macintosh drawings To: texhax <@Cs.Ucl.AC.UK:texhax@score.stanford.edu> Does anyone have a dvi to postscript converter that can include drawings made on the Mac at an appropriate point using the \special command? dvi2ps used to do this, but with the latest v49 of Apples LaserPrep, it seems to put the included drawing at the end, not at the point where the \special command specifies. Perhaps this is because some definitions have been changed within the LaserPrep file. Anyhow, if anyone has means of doing this, and wants to share them with me, I'd be grateful! Ralph ------------------------------ Date: Wed, 13 May 87 10:57:03 CDT From: William LeFebvre Subject: Re: Latex comment facilities To: TeXhax@score.stanford.edu Michael Matlack writes: > I assume one reason for the "%" comment prefix comments is so that the > reader of a LaTeX source file can immediately distinguish between text > to be processed and text meant as comments. A comment environment (with > \begin{comment} \end{comment}) would force a reader to continually > search for the begin/end delimiters....For example, one might set the > prefix to be "% " while commenting a LaTeX file. I don't know about Frank Reashore, but I would use a "comment" environment much in the same way that I use a "#ifdef notdef" statement in C: to TEMPORARILY prevent a block of text (code) from being processed, while still retaining that block in the file. I wuld not use it as a general commenting facility, for the reasons Michael points out. But it is kind of a hassle to prepend "%" to a whole block of existing text, and then to remove them later (although, I guess one could write a pair of emacs macros to make it easier). William LeFebvre Department of Computer Science Rice University ------------------------------ Date: Wed, 13 May 87 09:30:54 PDT From: To: texhax@score.stanford.edu Subject: CMS Distribution Tape Received: by WSUVM1 (Mailer X1.23) id 5706; Wed, 13 May 87 09:29:01 PLT Date: Wed, 13 May 87 09:24:21 PLT From: Dean Guenther 509-335-0411 Subject: CMS Distribution Tape To: Texhax column In TeXhax V87 #36 Chris Carruthers asks about the CMS distribution. Maria Code now has the most recent CMS distribution tape, dated 5/87. If you have a 6 month old tape, the major differences will be the new one has TeX 2.1; Allows use of the command line for MF; And many upgrades to the driver programs for the IBM series printers (3812, 3820, 3800-3, 4250, and APA6670). There are other changes, but not very significant. All changes will be outlined in the next TUGboat. Dean Guenther TeX IBM VM/CMS Site Coordinator Washington State University Pullman, Wa. 99164-1220 phone: 509-335-0411 BITnet: GUENTHER@WSUVM1 ------------------------------ Date: Wed, 13 May 87 12:26:51 PDT From: rusty@weyl.Berkeley.EDU (Rusty Wright) To: texhax@score.stanford.edu, rbbb@rice.edu Subject: latex "remark" environment In response to your query about a "proof" environment: I made a new command/environment called "remark" that's identical to the newtheorem command except (1) it's called newremark, and (2) it doesn't set the whole thing in italics. The name of the file that I use is remark.sty and people can pull it in via the optional arg to the \documentstyle command; e.g. \documentstyle[remark,12pt,twoside]{article} It was created simply by copying all of the code for the newtheorem command and changing all occurences of "theorem" with "remark" and "thm" (I think) with "rmk", and deleting the \it. I have mailed it to latex-style@cs.rochester.edu so you should be able to ftp it from there shortly. To get a real proof environment you'll also need to add code to make the rectangle at the end; I never got around to doing that although Lamport gave an explanation in a previous TeXhax about how to do it so that the rectangle gets "pulled up" onto the end of the last line of the proof. ------------------------------ Date: Wed, 13 May 87 13:37:35 PDT From: rusty@weyl.Berkeley.EDU (Rusty Wright) To: texhax@score.stanford.edu Subject: really really lowres metafont output Has anybody successfully generated very lowres output with Metafont? Date: Wed, 13 May 87 08:33 EDT From: Robert Scheifler Subject: have you had problems with Metafont? To: rusty@weyl.Berkeley.EDU Have you had any similar problems? Any advice would be appreciated. From: Chris Lindblad I'm having problems with some broken screen-resolution fonts. Metafont as standardly configured produces garbage font files for some fonts that are smaller than 10pt at 80 dpi, and I don't know how to hack Metafont parameters to fix it. The GF files that metafont produces causes GFtoPXL to blow up, resulting with PXL files that are totally unreadable. So I'm trying to frob with Metafont a little each day in some of my free time to try to get it to do something reasonable. The problem is that I don't understand anything about it, so I'm not getting anywhere. The fonts that I have generated at 118 dots per inch that we use with the dvitool SUN TeX previewer program that Jeff McCarrel wrote get pretty bad at small point sizes. 80 dots per inch must look really awful. I tried generating something at 80 dots per inch and like Chris I had problems, but different ones; metafont stopped 2 times with a "strange path (turning number is zero)" error in the file romanp.mf when I tried to run it on cmr8.mf with the following mode: % previewlow mode: for Textset previewer at lowest resolution mode_def previewlow = % for Textset previewer at lowest resolution proofing := 0; % no, we're not making proofs fontmaking := 1; % yes, we are making a font tracingtitles := 0; % no, don't show titles pixels_per_inch := 80; % really REALLY lowres blacker := 0.65; % make the pens a bit blacker fillin := 0.2; % compensate for diagonal fillin o_correction := 0.4; % don't overshoot as much enddef; I just hit return twice and then it finished up with no more complaints and gftopxl and gftopk didn't have any problems with the gf resulting file. ------------------------------ Mail-From: BEETON created at 13-May-87 15:17:45 Date: Wed 13 May 87 15:17:45-PDT From: Barbara Beeton Subject: Re: Help with large LaTex tables... To: SYSTEM%CUGSBVAX.BITNET@WISCVM.WISC.EDU In-Reply-To: Message from "SYSTEM%CUGSBVAX.BITNET@wiscvm.wisc.edu" of Tue 12 May 87 21:35:00-PDT the memory sizes in various implementations of tex were published in tugboat 7#1 (1986), pp 68-69. the stanford version of tex for vax/vms has a main memory size of 58000, but other vax/vms implementations have increased that to 65000 or 65500 (the absolute maximum is 2**whatever-1). you can safely use any of the vax/vms values given in that list; all the implementations cited passed the trip test. latex itself uses a very large chunk of memory. if latex is going to be a heavy user of your local tex, you should indeed give it all the memory you can. regarding `landscape' tables, you might consider just leaving blank pages (generating a table caption and a large empty box for each, to get the list of figures and cross-references correct) and producing the tables separately, entirely in landscape mode. don't know of anyone who's tried to make mixed modes work, and don't think it's realistically possible. -- barbara beeton ------------------------------ Date: Thu 14 May 87 00:01:08-PDT From: Philip M. Pitner Subject: ~~~~~~~~VorTeX... To: TeXhax@Score.Stanford.EDU I've read the Tex vs WYSIWYG (e.g. Word 3.0) debate with interest as I am undertaking the writing of my thesis this quarter. I came across the meeting notice below which describes a program which would give us the best of both worlds. I can't attend but anyone from the net which can please post your summary to the net. Phil IBM Almaden Research Center 650 Harry Road San Jose, CA 95120-6099 CALENDAR May 18-22, 1987 VORTEX AND BEYOND P. Chen, Computer Department, University of California at Berkeley Comput. Sci. Sem. Tues., May 19 2:00 P.M. Room: Rear Audit. VorTeX is a new document preparation system being developed at Berkeley that supports composite objects and multiple representations. By composite objects, we mean text and various types of graphical objects (bitmap, structured, data-driven, etc.) are all considered first-class citizens. In VorTeX, a document can be edited at both the source and target levels, changes made to one will propagate to the other automatically. For text, the source language is TeX; for graphics, it is PostScript. The system's major components include an Emacs-like source language editor, a target editor with a WYSIWYG user interface, an incremental TeX compiler, an interactive PostScript engine and presumably a variety of special-purpose editors. This talk will cover the basic design of VorTeX as well as some general issues surrounding interactive document preparation. Some thoughts will also be given about the next generation of VorTeX which will support multiple media and document dynamics. Host: D. Chamberlin ----------------------------------------------------------------------- For further information on individual talks, please contact the host listed above. Visitors, please arrive 15 minutes early. IBM's new Almaden Research Center (ARC) is located adjacent to Santa Teresa County Park, between Almaden Expressway and U.S. 101, about 10 miles south of Interstate 280. From U.S. 101, exit at Bernal Road, and follow Bernal Road west past Santa Teresa Blvd. into the hills (ignoring the left turn for Santa Teresa Park). Alternatively, follow Almaden Expressway to its southern terminus, turn left onto Harry Road, then go right at the ARC entrance (about a quarter of a mile later) and go up the hill. For more detailed directions, please phone the ARC receptionist at (408) 927-1080. ------------------------------ Posted-Date: Thu, 14 May 87 11:31:41 cdt Date: Thu, 14 May 87 11:31:41 cdt From: ables%pp.mcc.com@mcc.com (King Ables) To: texhax@score.stanford.edu, unix-tex@washington.arpa Subject: bug in texindex I don't know if this has been talked about before or not, but if so, please forgive my missing it and ignore... I found a slight bug in texindex that causes certain "correctly" positioned index entries to be generated without a page reference. For example: \indexentry{def}{35} \indexentry{abc}{30} \indexentry{def}{31} \indexentry{def}{32} \indexentry{def}{34} \indexentry{ghi}{18} \indexentry{jkl}{35} \indexentry{def}{33} should come out to look like: \item abc, 30 \item def, 31-35 \item ghi, 18 \item jkl, 35 but instead, it looks like: \item abc, 30 \item def, 31-35 \item ghi, 18 \item jkl The bug is in index1.awk (probably installed in /usr/lib/tex). The problem is that the variable lasttop is not reset when a line is finished, so when it processes the def line, lasttop is left at 35. Later, when jkl comes along, it checks to see if lasttop = the last entry and if it DOES NOT, then it prints out an entry. Since lasttop (only coincidentally) is still 35, it skips printing anything out for that line. The fix is to set lasttop to zero in the initialization line of the awk script: 13c13 < {toprange = 0; field = 2; botrange = $field; field1 = 1+field} --- > {toprange = 0; field = 2; botrange = $field; field1 = 1+field ; lasttop = 0} King Ables Microelectronics and Computer Technology Corporation (MCC) 3500 West Balcones Center Drive Austin, TX 78759 (512) 338-3494 (office) (512) 343-0978 (switchboard) ARPA: ables@mcc.com UUCP: {gatech,ihnp4,nbires,seismo,ucb-vax}!ut-sally!im4u!milano!mcc-pp!ables ------------------------------ %%%\bye End of TeXhax Digest ************************** -------