TeXhax Digest Monday, August 15, 1988 Volume 88 : Issue 72 Moderator: Malcolm Brown Today's Topics: Music in TeX and WEBtoC. Re: TeXhax Digest V88 #66 (LaTeX notes) Re: TeXhax Digest V88 #67 (LaTeX notes) TeX/VMS installation Question and answer math mode is tieing me down Xerox 2700 II DVI Driver Modifying LETTER.STY for our department letterhead. HP Laserjet II DVI postprocessor for Sun ? one page calendar Latex: Indentation after Sectioning TeX on SUNOS version 4 Re: MEtafont question LaTeX "short verbatim" mode Re: BibTeX 98 vs. BibTeX .99 Increasing TeX's memory limits TeXhax Digest V88 #70 ---------------------------------------------------------------------- Date: Wed, 03 Aug 88 15:33:23 PDT From: S John Banner Subject: Music in TeX and WEBtoC. Hello, I have a couple of questions. First, I recall once seeing posted on USENET (I think) some stuff for typesetting music in TeX. Does anyone know anything about this? I have a freind who wants to produce a book of the Music he plays, and would like to get it typeset properly. Second, does anyone know where I can get WEBtoC (and anything else that might go with it)? I don't have ftp access, so that option is out. Thanks, sjb. ------------------------------ From: lamport@decwrl.dec.com (Leslie Lamport) Date: 3 Aug 1988 1629-PDT (Wednesday) Subject: Re: TeXhax Digest V88 #66 (LaTeX notes) Erich Neuwirth writes: I want to make a variant of LETTER.STY also printing the letterhead. The letterhead has to be higher up on the first page, but I want the bottom lines flushing on the "titlepage" and on the following pages. Therefore ^textheight has to be different on the first and on the following pages. But ^textheight seems to be a VERY GLOBAL variable. It always uses the first assigned value and changing its value in a ^pagestyle definition (using ps@newstyle) does not produce the desired results. I know that usually one does not want to fiddle with ^textheight within a document, but on the other hand I do not think my wishes are completely stupid. The easy solution to his problem is not to change \textheight, but simply to place the top of the first page higher by inserting a negative vertical space at the beginning. Paul Davis writes: Has anyone hacked together a more accurate version of Leslie Lamport's wondrous \oval ? I'm a little distressed with the visual inaccuaracy of its results on our system when \thinlines is in effect. I can improve matters very slightly by using \thicklines, but given TeX's habit of working in sp's, can't we get the junctions between the elements of the oval to line up a little better ? As I recall, this is a bug in the Metafont code for the quarter and half circles used by the \oval command. I have in the past asked for volunteers to fix it, but with no luck. Leslie Lamport ------------------------------ From: lamport@decwrl.dec.com (Leslie Lamport) Date: 3 Aug 1988 1642-PDT (Wednesday) Subject: Re: TeXhax Digest V88 #67 (LaTeX notes) Mike DeCorte writes In the local guide on line 182 there is the command \hbox{\verb|\input|} I find this odd as the LaTeX manual says that \verb cannot be used in the argument to a command. I also don't see why the \hbox is needed. Why did Leslie Lamport do this? I'm not sure... I think it's left over from an earlier version in which \verb'ed text could be hyphenated. I believe that the \hbox'es can all be removed. He continues Also, in an itemize env, if I have a \item \hbox{a} b c the "a" will be put to the above the bullet to the left. As I expected a \leavevmode fixes it but, I would still like to know if this is expected (read documented) behavior and I have missed something obvious. The obvious thing he's missing is that \hbox is not a LaTeX command, there is no reason to expect it to do anything reasonable. I presume he means to use \mbox. Leslie Lamport ------------------------------ Date: 3 Aug 88 22:10 EST From: SPACIL H S Subject: TeX/VMS installation Help! We have the TeX VAX/VMS distribution and 300 dpi font tapes (Stanford version from Maria Code) for our microVAX II runnning VMS 4.6 with output to an LN03+ laser printer. Attempts to convert a GF font to a PXL font with CPtoPXL for use by the LN03 result in an error message to the effect that the GF font file contains an erroneous byte. Earlier attempts to generate GF fonts from MF files were generally unsuccessful; only a few of the MF files could be converted. Our problem may not be unique, but are we doing something really dumb here? Steve Spacil/spacil@ge-crd.arpa ------------------------------ From: INHB%MCGILLC.BITNET@Forsythe.Stanford.EDU Date: WED AUG 03, 1988 20.51.01 Subject: Question and answer I have a question and an answer. First the question. I am providing camera-ready copy to a (British) publisher who insists that no hyphenation shall come after only two characters (or before two, but TeX already does that). Is there any way of doing that short of changing the pattern dictionary? During the two months or so I have been subscribing to TeXHaX, there have been at least two, perhaps more, questions of the form, ``Isn't there any way of changing margins in LaTeX?'' Here's one way that seems to work, although you cannot change in the middle of paragraph. Simply set \textwidth to the largest width you want anywhere in the ms. Then if you want a narrower margin, say by 1/2" on the left and 1-1/2" on the right, simply insert \begin{list}{}{\topsep0pt \leftmargin.5in \rightmargin1.5in}\item Somewhere the TeX documentation suggests that you should have at least two items, but it doesn't seem to matter. To go yet another margin, first insert \end{list} and then begin another list. The LaTeX documentation syas explicitly that the parameters to \leftmargin and \rightmargin must be non-negative, althugh I haven't experimented with negative values. This is why I said to begin with the largest margins that appear anywhere in the ms. More precisely, the margins should be set so that they are as far left as you ever want and also as far right, even if these extreme settings are not actually used anywhere. (By the way, although somewhere the LaTeX manual suggests that you cannot reduce the margins to less than an inch all around, this is not so. I had to produce an ms for a European publisher that wanted it 17 by 25 cm and I had no trouble by using \textheight 25cm \textwidth 17cm \oddsidemargin -.25cm \evensidemargin -.25cm \topmargin -1cm). This can be made into a macro that takes the desired margins changes as two args and issues the necessary begin{list} command. Another approach is to read the latex.tex file and find out how the margins are really changed, but I haven't had the time to do that. Now, is there any way of changing \textheight? ------------------------------ Date: Wed, 3 Aug 88 22:08:25 EDT From: Jeff Norden Subject: math mode is tieing me down Is there any use at all to use a tie ( ~ ) in math mode?? Since a tilde is often used to denote equivalence relations, wouldn't it be better for it to expand to itself in math mode? Certainly, $a~b$ looks alot closer to what is meant than $a \sim b$. This becomes even more aparent when considering quotients: $X/~$ vs $X/\sim$ (actually, you need $X/{~}$ to get the spacing right, but its still easier to type and proofread than $X/{\sim}$.) Amstex.tex defines ~ more intelligently than plain.tex as \def~{\unskip\nobreak\ \ignorespaces} But, it seems to me, an even better definition would be \def~{\ifmmode\mathtilde\else\unskip\nobreak\ \ignorespaces\fi} \def\mathtilde{\sim} This would also allow the ``user'' to re-define what ~ will expand to in math mode (\thicksim or \approx would be likely candidates). Is there any good reason for NOT doing this? Or is this something which simlply didn't occur to Knuth, Spivac, et al.? -Jeff Norden jeff@colgate.csnet Dept of Mathematics, Colgate University, Hamilton, NY 13346. ------------------------------ Date: Thu, 4 Aug 88 15:34 EDT From: Subject: Xerox 2700 II DVI Driver I recently received a Xerox 2700 II laser printer to have as my own. Does anyone know if DVI drivers are available for this klunker? Any information will be appreciated. Salvatore Saieva Queens College Academic Computer Center Flushing, N.Y. 11367 bitnet: SAIEVA@QCVAX ------------------------------ Date: Thu, 4 Aug 88 18:49 EST From: "Thomas G. Abernathy" Subject: Modifying LETTER.STY for our department letterhead. We here at Mount Sinai are very new to TeX and LaTeX. I would like to modify the letter style sheet so that it will work with our letterhead, but I can't make heads or tails of the letter.doc file. The minimal solution for use would be to make the top margin on the first page greater (needs to be about 2.75 inches) so that the date etc. do not print on the letterhead. I would also like to be able to place the professor's name and extension in the correct location. I would also like to be able to include the appropriate codes for feeding the first sheet from a different bin on our QMS PS800 (post script) printer. Tom Abernathy Director of Research Computing Unit Department of Biomathematical Sciences Mount Sinai School of Medicine New York, New York 10029 tom@msrcvax.BITNET or TGAMS@CUNYVM.CUNY.EDU ------------------------------ Date: Wed, 3 Aug 88 12:31:45 +0200 From: gutorm@ifi.uio.no Subject: HP Laserjet II DVI postprocessor for Sun ? Where can i get (FTP is ok) a DVI postprocessor that will support HP Laserjet II, and that will run on a Sun 3? In advance: Thanks! | gutorm thomas hogasen | Internet: gutorm@ifi.uio.no | | University of Oslo | Bitnet: gutorm@oslo-vax.arpa | | Inst. of Mathematics | | | Box 1053 Blindern | | | N-0316 OSLO | | | NORWAY | Tlf: +47 2 455879 | ------------------------------ Date: 5 Aug 88 10:53 -0500 From: Michael Doob Subject: one page calendar In TeXhax (v88/68) Chip Roberson asks for a block calendar. The following allows messages to be inserted on given days. %%% The following TeX input will produce a one page calendar. Each %%% %%% date is in a shadow box with a (possibly nul) message. The %%% %%% counters \blankdays and \daysinmonth must be set initially. The %%% %%% value of \message should be set before \daybox is called. %%% %%%%%%%%%%%%% dimensions for the box containing the date %%%%%%%%%%%%% \newdimen\dayht \dayht=70pt %%% height of the box containing each date \newdimen\daywidth \daywidth=60pt %%% width of the box containing each date \newdimen\rulewidth \rulewidth=1pt %%% width of rules around date box \newdimen\padwid \padwid=6pt %%% width of shadow boxing \newdimen\interrowspace \interrowspace=8pt %%% space between weeks \newdimen\shortwid \shortwid=\daywidth \advance\shortwid by -\padwid \newdimen\longwid \longwid=\daywidth \advance\longwid by 2\padwid \advance \longwid by 2\rulewidth %%%%%%%%%%%% set counters for numbering days %%%%%%%%%%%%%%%%%%%% %% \blankdays is the number of blank positions before the first of the month %% \blankdays=0 ... \blankdays=6 for the first on Sunday ... Saturday \newcount\blankdays \blankdays=5 \newcount\daynumber \daynumber=-\blankdays \newcount\daysinmonth \daysinmonth=31 %%%% 31, 30, 29, or 28 \advance \daysinmonth by 1 %%%% macro that prints a box containing \the\daynumber and \message %%%% \def\daybox{% \global\advance\daynumber by 1 \ifnum \daynumber < \daysinmonth \ifnum \daynumber > 0 \offinterlineskip% \hbox{% \hskip\padwid \vrule height\dayht width\padwid \vbox{% \hbox{% \vrule height\dayht width\rulewidth \vbox to \dayht{% \hrule width\daywidth height\rulewidth \vskip\padwid \hbox to \daywidth{% \hfil\the\daynumber\hskip\padwid} \vfil \hbox to \daywidth{\hfil \message \hfil} \vfil \hrule width\daywidth height\rulewidth}% \vrule height\dayht width\rulewidth}% \moveleft \padwid \vbox{\hrule height\padwid width\daywidth}}}% \else \hskip \longwid \fi \fi } \nopagenumbers \parindent=0pt \hoffset=-.75in \hsize=7.5in \hsize = 7\longwid %%%%% ready to go -- print a title banner %%%% \centerline{\bf July 1988} \vskip .5in %%%%% here comes a line with the days of the week %%%%% \leftline{ \hbox to \longwid{\hfil Sunday \hfil}% \hbox to \longwid{\hfil Monday \hfil}% \hbox to \longwid{\hfil Tuesday \hfil}% \hbox to \longwid{\hfil Wednesday \hfil}% \hbox to \longwid{\hfil Thursday \hfil}% \hbox to \longwid{\hfil Friday \hfil}% \hbox to \longwid{\hfil Saturday \hfil}% } \vskip 2\interrowspace \def\message{} %inserted message is initially nul %% week 1 %% \hbox{% \daybox \daybox \daybox \daybox \daybox \daybox \daybox } \vskip \interrowspace %% week 2 %% \hbox{% \daybox \daybox \daybox \daybox \daybox \daybox \daybox } \vskip \interrowspace %% week 3 %% \hbox{% \daybox \daybox \daybox \daybox \daybox \daybox \daybox } \vskip \interrowspace %% week 4 %% \hbox{% \daybox \daybox \def\message{\vbox{\hbox{\TeX hax}\vskip 3pt\hbox{arrives!}}}% \daybox \def\message{}% \daybox \daybox \daybox \daybox } \vskip \interrowspace %% week 5 %% \hbox{% \daybox \daybox \daybox \daybox \daybox \daybox \daybox } \vskip \interrowspace %% week 6 %% \hbox{% \daybox \daybox \daybox \daybox \daybox \daybox \daybox } \bye ------------------------------ From: Walter Olthoff Subject: Latex: Indentation after Sectioning Date: Fri, 05 Aug 88 13:21:41 PDT I know some people call it ``bad style'', but I would like to have an \parindent already in the first paragraph of a section. The article.sty and art12.sty macro packages seem to have no provision for it (for example, \section is defined by \@startsection, but I can't find the latter). What I get is 1. Introduction First paragraph starts without indent and continues like this. Second paragraph start indented and continues leftaligned like this. What I want is 1. Introduction First paragraph starts indented and continues leftaligned like this. Second paragraph start indented and continues leftaligned like this. Some hacks work, but I am interested in /@startsection or a similar solution. Thanks for your help. Walter Olthoff Hewlett-Packard 1501 Page Mill Road Palo Alto,CA 94304-0971 415-857-7877 olthoff@hplabs.HP.COM ------------------------------ Date: Tue, 2 Aug 88 16:54 CST From: Dick Brown Subject: TeX on SUNOS version 4 I got TeX to work with SUNOS version 4 without a problem. I had to change from am* fonts to cm* fonts (for reasons other than the OS change), and I found that the executables for initex, virtex and even undump which worked for version 3 still worked for version 4. (I was pretty surprised about the undump). The executables referred to were generated from some version of the Univ. of Wash. tape (about a year ago, I think), if that makes any difference. Dick Brown (rbrown@carleton.edu, {ihnp4, umn-cs}!stolaf!ccnfld!rbrown) Department of Math and Computer Science Carleton College Northfield, MN 55057 ------------------------------ From: ekrell@ulysses.att.com Date: Fri, 5 Aug 88 22:41:01 EDT Subject: Re: MEtafont question I think your problem is with the assignment to "mag" in the command line for Metafont. It should be "mag:=magstep(1)" instead of just "mag:=1". ------------------------------ Date: Sat, 6 Aug 88 02:28:32 PDT From: Jonathan_Thornburg@mtsg.ubc.ca Subject: LaTeX "short verbatim" mode I'm looking for a LaTeX "short verbatim" macro, rather like \verb|...|, but which can be used in chapter/section titles, figure captions, inside a box in math mode, and generally in arguments to other macros. \tt alone almost does the job because I'm really only worried about computer program names, which don't have many special characters in them, *but* I don't want to have to say \_ to get an underscore. I have played around with \catcode-ing the underscore so it's not active, but this seemes to come too late in TeX's digestive process if we're inside a macro argument. (Can a macro wizard do it right?) Ideally, I'd like a LaTeX-compatible (this is essential) macro \ct ("computer type") such that I can say \section{How the {\ct compute_F()} subroutine computes $F_{ij}$} or \begin{figure} ... \caption[Architecture of the {\ct compute_F()} subroutine] { The {\ct compute_F()} subroutine computes $F_{ij}$ via the intermediate quantities $\mbox{\ct Q_dd}^k_{ij}$, ... } \end{figure} At the moment I'm using \tt with \_ as needed, but surely there's a more elegant solution? -- Jonathan Thornburg thornburg@mtsg.ubc.ca userbkis@ubcmtsg.bitnet userbkis%ubcmtsg@um.cc.umich.edu uunet!ubc-vision!ubcmtsg.bitnet!thornburg ------------------------------ Date: Sat 6 Aug 88 08:00:08-PDT From: Oren Patashnik Subject: Re: BibTeX 98 vs. BibTeX .99 > From: anita@astro.as.utexas.edu (Anita Cochran) > Subject: BibTeX 98 vs. BibTeX 99 > > We are currently running BibTeX (C Version) 0.98i. I understand there > are some major improvements to BibTeX in version 0.99 but that 0.99 is > {\bf not} compatible with 0.98. Since we have designed some style > files here (for the astronomy journals Astrophysical Journal and Icarus > if anyone is interested), we are reluctant to upgrade our BibTeX. > > Could someone please outline the following: > 1) Advantages of BibTeX 0.99 > 2) Differences in the bst files from 0.98 to 0.99 > 3) Procedures for converting bst files from 0.98 to 0.99 > 4) Anything else you think is needed for an informed choice between > the two BibTeX programs The two documents "BibTeXing" and "Designing BibTeX styles" reside as files BTXDOC.TEX and BTXHAK.TEX on [score.stanford.edu] in the directory ; they are available via FTP and they address points 1) through 4). In short, to update an old (.98) style, or to create a completely new style, it's best to start with an existing .99 style (such as PLAIN.BST) that's close to yours, and then modify that. This takes between 15 minutes and a day, depending on how far your style is from the existing style. ************************************************************************** * This is the last time you'll have to convert your style, however, * * since all future versions of BibTeX will be compatible with style-file * * versions .99 and beyond. (BibTeX 1.00 will be the frozen version; * * subsequent versions will simply fix bugs.) * ************************************************************************** --Oren Patashnik (BibTeX implementor) ------------------------------ Date: Sat, 6 Aug 88 09:09:48 PDT From: hildum@iris.ucdavis.edu (Eric Hildum) Subject: Increasing TeX's memory limits Some time ago, I posted a similar question about TeX's memory limits. Based on the responses, I made several changes to the TeX change file (we are using the Kellerman and Smith TeX 2.9 for VAX/VMS). I am including a copy of the differences file, plus the SLP file (for the SLP editor). I was suprised at how few changes are actually needed to increase the memory limits. Change file differences: ************ File TEX_ROOT:[TEX]TEX.CH;1 169 @!mem_max=65000; {greatest index in \TeX's internal |mem| array; 170 must be strictly less than |max_halfword|; ****** File TEX_ROOT:[TEX]BIGTEX.CH;1 169 @!mem_max=400000; {greatest index in \TeX's internal |mem| array; 170 must be strictly less than |max_halfword|; ************ ************ File TEX_ROOT:[TEX]TEX.CH;1 225 @d mem_top==65000 {largest index in the |mem| array dumped by \.{INITEX}; 226 must be substantially larger than |mem_bot| ****** File TEX_ROOT:[TEX]BIGTEX.CH;1 225 @d mem_top==400000 {largest index in the |mem| array dumped by \.{INITEX}; 226 must be substantially larger than |mem_bot| ************ ************ File TEX_ROOT:[TEX]TEX.CH;1 735 On VAX/VMS, we use some hackery to cause floating point numbers stored in 736 |mem| to be |single|, but other |real| variables and expressions are 737 done as |double| length reals. 738 739 @d set_glue_ratio_zero(#) == #:=0.0 {store the representation of zero ratio} 740 @d set_glue_ratio_one(#) == #:=1.0 {store the representation of unit ratio} 741 @d real == double {use double precision reals for computation} 742 @d float(#) == dble(#) {convert from |glue_ratio| to type |real|} 743 {FIX ME} 744 @d unfloat(#) == sngl(1.0@&D0 * #) {convert from |real| to type |glue_ratio|} 745 @d float_constant(#) == #.0@&D0 {convert |integer| constant to |real|} ****** File TEX_ROOT:[TEX]BIGTEX.CH;1 735 @d set_glue_ratio_zero(#) == #:=0.0@&D0 {store the representation of zero ratio} 736 @d set_glue_ratio_one(#) == #:=1.0@&D0 {store the representation of unit ratio} 737 @d real == double {use double precision reals for computation} 738 @d float(#) == # {convert from |glue_ratio| to type |real|} 739 @d unfloat(#) == # {convert from |real| to type |glue_ratio|} 740 @d float_constant(#) == #.0@&D0 {convert |integer| constant to |real|} ************ ************ File TEX_ROOT:[TEX]TEX.CH;1 748 @!glue_ratio=r@&e@&a@&l; {one-word representation of a glue expansion factor} 749 @z ****** File TEX_ROOT:[TEX]BIGTEX.CH;1 743 @!glue_ratio=real; {one-word representation of a glue expansion factor} 744 @z ************ ************ File TEX_ROOT:[TEX]TEX.CH;1 752 @d qi(#)==#+min_quarterword ****** File TEX_ROOT:[TEX]BIGTEX.CH;1 747 @d max_quarterword=255 {largest allowable value in a |quarterword|} 748 @d min_halfword==0 {smallest allowable value in a |halfword|} 749 @d max_halfword==65535 {largest allowable value in a |halfword|} 750 @y 751 @d max_quarterword=1023 {largest allowable value in a |quarterword|} 752 @d min_halfword==0 {smallest allowable value in a |halfword|} 753 @d max_halfword==@"3FFFFFFF {largest allowable value in a |halfword|} 754 @z 755 756 @x 757 @d qi(#)==#+min_quarterword ************ ************ File TEX_ROOT:[TEX]TEX.CH;1 768 @!word_file = file of memory_word; 769 @y 770 @!word_file = record ****** File TEX_ROOT:[TEX]BIGTEX.CH;1 773 @!two_halves = packed record@;@/ 774 @!rh:halfword; 775 case two_choices of 776 1: (@!lh:halfword); 777 2: (@!b0:quarterword; @!b1:quarterword); 778 end; 779 @!four_quarters = packed record@;@/ 780 @!b0:quarterword; 781 @!b1:quarterword; 782 @!b2:quarterword; 783 @!b3:quarterword; 784 end; 785 @!memory_word = record@;@/ 786 case four_choices of 787 1: (@!int:integer); 788 2: (@!gr:glue_ratio); 789 3: (@!hh:two_halves); 790 4: (@!qqqq:four_quarters); 791 end; 792 @!word_file = file of memory_word; 793 @y 794 @!two_halves = [@=quad@>] packed record@;@/ 795 @!rh:halfword; 796 case two_choices of 797 1: (@!lh:[@=long@>] halfword); 798 2: (@!b0:[@=word@>] quarterword; @!b1:[@=word@>] quarterword); 799 end; 800 @!four_quarters = [@=quad@>] packed record@;@/ 801 @!b0:[@=word@>] quarterword; 802 @!b1:[@=word@>] quarterword; 803 @!b2:[@=word@>] quarterword; 804 @!b3:[@=word@>] quarterword; 805 end; 806 @!memory_word = [@=quad@>] record@;@/ 807 case four_choices of 808 1: (@!int:integer); 809 2: (@!gr:glue_ratio); 810 3: (@!hh:two_halves); 811 4: (@!qqqq:four_quarters); 812 end; 813 @!word_file = record ************ ************ File TEX_ROOT:[TEX]TEX.CH;1 804 var t:packed array[1..7] of halfword; {raw year, month, day and time} 805 begin @= $numtim@>(t);@/ ****** File TEX_ROOT:[TEX]BIGTEX.CH;1 847 var t:packed array[1..7] of 0..@"FFFF; {raw year, month, day and time} 848 begin @= $numtim@>(t);@/ ************ Number of difference sections found: 7 Number of difference records found: 64 DIFFERENCES /IGNORE=()/MERGED=1/OUTPUT=SYS$USERS:[HILDUM]CHANGES.DIF;1- TEX_ROOT:[TEX]TEX.CH;1- TEX_ROOT:[TEX]BIGTEX.CH;1 End of change file differences. SLP editor input: - 169, 169 <@!mem_max=400000; {greatest index in \TeX's internal |mem| array; - 225, 225 <@d mem_top==400000 {largest index in the |mem| array dumped by \.{INITEX}; - 735, 744 <@d set_glue_ratio_zero(#) == #:=0.0@&D0 {store the representation of zero ratio} <@d set_glue_ratio_one(#) == #:=1.0@&D0 {store the representation of unit ratio} <@d real == double {use double precision reals for computation} <@d float(#) == # {convert from |glue_ratio| to type |real|} <@d unfloat(#) == # {convert from |real| to type |glue_ratio|} - 748, 748 <@!glue_ratio=real; {one-word representation of a glue expansion factor} - 751 <@d max_quarterword=255 {largest allowable value in a |quarterword|} <@d min_halfword==0 {smallest allowable value in a |halfword|} <@d max_halfword==65535 {largest allowable value in a |halfword|} <@y <@d max_quarterword=1023 {largest allowable value in a |quarterword|} <@d min_halfword==0 {smallest allowable value in a |halfword|} <@d max_halfword==@"3FFFFFFF {largest allowable value in a |halfword|} <@z <@x - 768, 769 <@!two_halves = packed record@;@/ @!rh:halfword; case two_choices of 1: (@!lh:halfword); 2: (@!b0:quarterword; @!b1:quarterword); end; <@!four_quarters = packed record@;@/ @!b0:quarterword; @!b1:quarterword; @!b2:quarterword; @!b3:quarterword; end; <@!memory_word = record@;@/ case four_choices of 1: (@!int:integer); 2: (@!gr:glue_ratio); 3: (@!hh:two_halves); 4: (@!qqqq:four_quarters); end; <@!word_file = file of memory_word; <@y <@!two_halves = [@=quad@>] packed record@;@/ @!rh:halfword; case two_choices of 1: (@!lh:[@=long@>] halfword); 2: (@!b0:[@=word@>] quarterword; @!b1:[@=word@>] quarterword); end; <@!four_quarters = [@=quad@>] packed record@;@/ @!b0:[@=word@>] quarterword; @!b1:[@=word@>] quarterword; @!b2:[@=word@>] quarterword; @!b3:[@=word@>] quarterword; end; <@!memory_word = [@=quad@>] record@;@/ case four_choices of 1: (@!int:integer); 2: (@!gr:glue_ratio); 3: (@!hh:two_halves); 4: (@!qqqq:four_quarters); end; - 804, 804 var t:packed array[1..7] of 0..@"FFFF; {raw year, month, day and time} ------------------------------ Date: Sat, 6 Aug 88 14:57:33 PDT From: mackay@june.cs.washington.edu (Pierre MacKay) Subject: TeXhax Digest V88 #70 WEB-to-C is a more general version of TeX-to-c. We are moving very close to the complete elimination of pascal compilation for all parts of the Unix TeX distribution. Only MFware is still compiled in pascal. If you are getting satisfactory performance out of TeX 2.9 you needn't be in any great rush for a new distribution, but just for the record, the versions are now: web2c 2.20 TeX 2.93 plain.tex 2.92 METAFONT 1.5 bibtex 99c 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 %%% %%% Back issues available for FTPing as: %%% machine: directory: filename: %%% [SCORE.STANFORD.EDU]TEXHAXnn.yy %%% nn = issue number %%% yy = last two digits of current year %%%\bye %%% ------------------------------ End of TeXhax Digest ************************** -------