Subject: TeXhax Digest V90 #1 From: TeXhax Digest Errors-To: TeXhax-request@cs.washington.edu Maint-Path: TeXhax-request@cs.washington.edu To: TeXhax-Distribution-List:; Reply-To: TeXhax@cs.washington.edu TeXhax Digest Friday, January 5, 1989 Volume 90 : Issue 1 Moderators: Tiina Modisett and Pierre MacKay %%% The TeXhax digest is brought to you as a service of the TeX Users Group %%% %%% in cooperation with the UnixTeX distribution service at the %%% %%% University of Washington %%% Today's Topics: The TeX Users Group is pleased to announce its March, 1990 Course Schedule TeX Tex for VMS MicroPress VTeX Producing tfm files METAFONT magnifications LaTeX, lfonts files LateX, \uppercase Re: bug or feature in \uppercase{\bf } ? Standardising \language values Re: Supercited reference numbers in LaTeX LaTeX, citations, superscripts --------------------------------------------------------------------------- The TeX Users Group is pleased to announce its March, 1990 Course Schedule: Intensive Beginning/Intermediate TeX, University of Michigan, March 5-9 Advanced TeX/Macro Writing, Vanderbilt University, March 5-9 Intensive Beginning/Intermediate TeX, Texas A&M University, March 12-16 Inten Beginning/Intermediate TeX, Univ of Illinois at Chicago, March 19-23 Intensive Course in LaTeX, Harvard University, March 26-30 Intensive Beginning/Intermediate TeX, Northeastern University, March 26-30 Please send mail to Charlotte for additional course information: cvl@math.ams.com Information about the Annual Meeting at Texas A&M is available also. ------------------------------------------------------------------------------- Date: Tue, 12 Dec 89 19:03:34 +0100 From: soulard@sor.inria.fr Subject: TeX Keywords: TeX, general questions %%%The following was originally addressed to Don Hosek, who passed %%%it on to TeXhax. You seem to know all about TeX and I'm a new user, so I hope you could answer to this : - what is LaTeX, SliTeX, bibTeX, XeT, and all around ..TeX.. - is there TeX and Co on PC, and where ? Thanks. Herve. ------------------------------------------------------------------------ Date: Mon, 11 Dec 89 14:37 EDT From: James Dryfoos- PostMaster Subject: Tex for VMS Keywords: TeX, VMS I am a new comer to TEX and am trying to get TEX up on a VAX-VMS system. I am on BITnet and INTERnet. What is best way to get TEX? I FTP'ed to YMIR.CLAREMONT.EDU and found to executables for VMS TEX but am not sure what I need? There are a lot of files and directories. What do I need to set things up? Is there any easier way of getting the files except for ftping each one by one? What is diff between TEX, MF, BIBTEX, TEXWARE, MFWARE, and WEB? I pulled some doc but they are in .TEX format. How can I look at them in a more readable format? Also, what printers are supported. Thanks for your help. -Jim ----------------------------------------------------------------------------- Date: Mon, 11 Dec 89 17:06:05 PST From: JSLee Subject: MicroPress VTeX Keywords: VTeX, MicroPress Has anyone tried this out and what do you think about it? ------------------------------------------------------------------------------- Date: Tue, 12 Dec 89 01:56:51 EST From: Allan Adler Subject: Producing tfm files Keywords: METAFONT, tfm files I have finally figured out how to get metafont to work on the SUN3 I am using. Now I am trying to figure out how to get gftodvi to work. I'm practicing on the file grayf.mf which comes with this distribution of TeX. METAFONT produces gray.2602gf but it doesn't produce gray.tfm . According to the METAFONT book, Appendix F, plain METAFONT usually sets METAFONT's internal variable fontmaking to an appropriate value to produce a .tfm file. I ran grep and found that grayf.mf does indeed contain the command mode_setup. So how come I don't get a .tfm file and what can I do to get one ? Allan Adler ara@lom1.math.yale.edu ------------------------------------------------------------------------- Date: Wed, 13 Dec 89 08:44:57 PST From: wagman%praxis.hepnet@Csa5.LBL.Gov (Gary S. Wagman (415)486-6610) Subject: METAFONT magnifications Keywords: METAFONT, magnifications Robert Bruner asked for simple instructions to generate new magnifications. I generate PK files (rather than pixel files as he, perhaps inadvertantly, requested) for use with Arbortext's DVIPS which requires that files be distributed among subdirectories named dpixxx where xxx is the resolution multiplied times the scale divided by 1000. Our DVIPS then requires new entries in the DVIPS.FNT file for these magnifications. I show UNIX examples below of cmr10 being scaled 666, 1000, 1440, and 1728 first at 300dpi for the "localfont" default printer and then at 900dpi for a linotronics. Note that Metafont produces GF (generic format) files but that most DVI-to-whatevers require another file format like PXL or PK so you must run GFTOPK like I do or maybe GFTOPXL. This required procedure is so tedious for making a new resolution of common fonts at common magnifications that I wrote a little FORTRAN program to generate statements like those shown below. Gary Wagman Lawrence Berkeley Lab Berkeley, CA 94720 (415)486-6610 BITNET: Wagman@LBL INTERNET: Wagman@LBL.Gov HEPNET: LBL::GSWagman %====================================================================== 300DPI FOR LOCALFONT alias rm rm cmmf '\mode=localfont; mag=0.66600;' input cmr10 mkdir dpi200 gftopk cmr10.200gf mv cmr10.200pk dpi200/cmr10.pk rm cmr10.200gf cmmf '\mode=localfont; mag=1.00000;' input cmr10 mkdir dpi300 gftopk cmr10.300gf mv cmr10.300pk dpi300/cmr10.pk rm cmr10.300gf cmmf '\mode=localfont; mag=1.44000;' input cmr10 mkdir dpi432 gftopk cmr10.432gf mv cmr10.432pk dpi432/cmr10.pk rm cmr10.432gf cmmf '\mode=localfont; mag=1.72800;' input cmr10 mkdir dpi518 gftopk cmr10.518gf mv cmr10.518pk dpi518/cmr10.pk rm cmr10.518gf 900DPI FOR LINOTRONICS alias rm rm cmmf '\mode=linonine; mag=0.66600;' input cmr10 mkdir dpi599 gftopk cmr10.599gf mv cmr10.599pk dpi599/cmr10.pk rm cmr10.599gf cmmf '\mode=linonine; mag=1.00000;' input cmr10 mkdir dpi900 gftopk cmr10.900gf mv cmr10.900pk dpi900/cmr10.pk rm cmr10.900gf cmmf '\mode=linonine; mag=1.44000;' input cmr10 mkdir dpi1296 gftopk cmr10.1296gf mv cmr10.1296pk dpi1296/cmr10.pk rm cmr10.1296gf cmmf '\mode=linonine; mag=1.72800;' input cmr10 mkdir dpi1555 gftopk cmr10.1555gf mv cmr10.1555pk dpi1555/cmr10.pk rm cmr10.1555gf ------------------------------------------------------------------------------ Date: Tue, 12 Dec 89 07:56:09 EST From: INHB000 Subject: LaTeX, lfonts files Keywords: LaTeX, lfonts files I wanted to warn all LaTeXers out there of an undocumented change in the lfonts file (at least I have never heard about it and spent a lot of time uncovering it) that happened at some point in the last three or four years. My coauthor and I repeatedly were getting different results as far as linebreaks, overfull boxes, etc. We were using identical style files and macros and, of course, the identical text. The result, in a 450 page book, was that my run was five pages longer than his. After much investigation, we compared lfont.tex files and discovered that they were different. Specifically, in 12pt text, the older version (mine) uses cmr10 \magstep 1 as its textfont 1 and the newer version uses cmr 12. The latter puts slightly less space between letters and is not intended to be reduced, while the former is so intended. In general, I think most people use 12pt for the larger type and don't reduce it, although as it happens ours will be. Still, it is a little odd that such a change would be made without warning. Michael Barr ----------------------------------------------------------------------- Date: Wed, 13 Dec 89 08:59:17 EST From: INHB000 Subject: LateX, \uppercase Keywords: LateX, \uppercase Hubert Partl suspects that there is a bug in that the line \rm a \uppercase{\bf b } c causes the `c' to be printed in bold. But this is just what one should expect since it is well documented that the braces around macro parameters are peeled off. In fact, the situation is a bit different with \upppercase since, as documented in the first \doubledangerous paragraph at the top of p. 41 of the TeXbook, the \uppercase command (it is a kernel command) requires the argument to be delimited by braces. I cannot figure out how to do this with defined macros, by the way, although I am reluctant to say it is impossible. At any rate, either of \rm a \uppercase{{\bf b}} c \rm a {\bf\uppercase {b}} c will have the desired effect. The first works because the inside set of braces remains and delimits the effect of \bf and the second is the obvious solution. Michael Barr ----------------------------------------------------------------- Date: Wed, 13 Dec 89 11:35:47 CET From: Rainer Schoepf Subject: Re: bug or feature in \uppercase{\bf } ? Keywords: LaTeX, \uppercase >If I write something like > > \rm a \uppercase{\bf b } c > >then I get the following: > > a is printed in lower case roman > > b is printed in upper case bold face > > c is not printed in lower case roman (as I would expect) > but in lower case bold face! > >(This happened within LaTeX, but \uppercase seems to be a Plain TeX command.) > >Now, why does the closing bracket that ends the argument of \uppercase >not end the scope of the \bf command? Is this a bug or a feature? > --------------------------- \uppercase is neither a LaTeX nor a plain TeX command, it's a TeX primitive. The behaviour is exactly as explained in the TeXbook: the result of \uppercase{} is the token list, with all lower case characters replaced by their upper case equivalent (as specified by their \uccode), all other tokens remain unchanged. So the result of the \rm a \uppercase{\bf b} c above is \rm a \bf B c and that is what comes out. >(For me, anyway, it is a behaviour that contradicts what I am used to know >about grouping rules, so even if it were a feature hidden in some manual, >I would consider it a bad one.) > > Hubert Partl So your knowledge of the meaning of the curly braces is incomplete. During macro expansion they are only delimiters. Consider for example the macro definition \def\mmm#1{#1} If you now write \rm a \mmm{\bf b} c the curly braces around \mmm's argument are removed during the expansion and you end up with both a bold b and c. So the behaviour of \uppercase is not exceptional. Rainer Sch\"opf ------------------------------------------------------------------- Date: Wed, 13 Dec 89 00:29:24 GMT From: Chris Thompson Subject: Standardising \language values Keywords: TeX 3.0, language values I think that the postings about allocating `written on the wall' numbers to particular languages (Tor Lillqvist in #101, Dominik Wujastyk in #103, Tor Lillqvist again in #109) rather miss the point. Users are not going to refer to languages by numbers (surely?) but by control sequences; e.g. \language=\swedish (or maybe \swedish which expands into \language=). Imagine if macro package writers had to fight over \count register number like this. (``No, you can't use \count217, that one's reserved for Giles Murchison's additions to LaTeX.'') What is needed is an allocation macro \newlanguage, and I don't see any insuperable difficulties about designing it. One question is that referred to above: what sort of definition of \swedish should \newlanguage\swedish perform? If it is the number (like \newbox) you have to say \language=\swedish (tedious) but you can do \setlanguage\swedish if you have to; if it is the macro that expands into "\language=..." then you will have difficulty with the latter. Maybe a scheme like \newif's is called for, by which \swedish is the macro, but \swedishnumber is also defined in case you need to to do \setlanguage. Another wrinkle is that if a language is to have \patterns (and there is only one interesting language that doesn't: the ``don't you hyphenate any of my words, thank you very much'' one) then these \newlanguage calls have to be done at INITeX time; and (worse) in runs of INITeX that don't start from an existing format file (at least, that is the state of affairs in TeX 2.992). Chris Thompson JANET: cet1@uk.ac.cam.phx Internet: cet1%phx.cam.ac.uk@nsfnet-relay.ac.uk ------------------------------------------------------------------------ Date: Wed, 13 Dec 89 09:27 CDT From: U2591AA@VMS.UCC.OKSTATE.EDU Subject: Re: Supercited reference numbers in LaTeX Keywords: LaTeX, supercited reference numbers A file "supercite.sty" follows this message. It was written by Charles LaBrec when he was a grad student at Purdue. He is now employed by Sun (last I heard anyhow). If this isn't quite what you want, you might want to get the file "aip.sty" from the Clarkson archives via anonymous ftp. Charles Karney of the Princeton Plasma Physics Lab wrote this style file for American Institute of Physics (AIP) journals, and supercited references are a part of this style. Karney is a first class TeX expert, and his implementation is excellent. His TeX "code" is so easy to read that you could strip out just the relevant parts and make your own .sty file if you desired. The full path name on sun.soe.clarkson.edu for aip.sty is pub/tex/latex-style/aip.sty You use ftp and login as anonymous (any password), then "cd pub/tex/latex-style", then "get aip.sty". Scott McCullough u2591aa@uccvms (bitnet) Dept. of Physics u2591aa@vms.ucc.okstate.edu (internet) Oklahoma State University Stillwater, OK 74078-0444 405-744-5801 "An enemy can partly ruin a man, but it takes a well meaning and injudicious friend to complete the job and make it perfect." Pudd'nhead Wilson's Calendar %---------------cut here---------------------------- % SUPERCITE DOCUMENT-STYLE OPTION FOR ANY STYLE % RELEASED 6 December 1987 -- for LaTeX version 2.09 % Written by C. LaBrec @ newton.physics.purdue.edu % % This redefines the \@cite macro to perhaps produce raised citations % while keeping the spacefactor unchanged. This is so that a citation % can properly follow a sentence-ending punctuation mark. A kluge is % involved since the macro that calls this puts the citation in an \hbox % which causes it not to be made smaller in math mode % \newif\if@raisedcite \def\@cite#1#2{\if@raisedcite\leavevmode\penalty10000 \ifhmode \edef\@x@sf{\spacefactor\the\spacefactor}\else\let\@x@sf\relax\fi \hbox{\let\hbox\relax $^{\rm #1\if@tempswa, #2\fi}$}\@x@sf{}\else #1\if@tempswa , #2\fi\fi{}} % % this redefines \cite to have a *-option. This option uses \if@raisedcite % to produce either an unadorned citation, i.e., just the number, or a % raised citation % \def\cite{\@ifstar{\@raisedcitefalse\@@citex}{\@raisedcitetrue\@@citex}} \def\@@citex{\@ifnextchar [{\@tempswatrue\@citex}{\@tempswafalse\@citex[]}} ------------------------------------------------------------------------- Date: Wed, 13 Dec 89 11:57:28 EST From: tla@bartok.att.com (Terry L Anderson) Subject: LaTeX, citations, superscripts Keywords: LaTeX, citations, superscripts In TeXhax Digest 89:10, John Yates would like to make citations appear as superscripts rather than in brackets, but finds that the definition is "built into the LaTeX executable and perhaps inaccessible". The modification you desire is quite easy. The default definition of the appearance of citations is indeed in latex.tex so sort of "buit into" into the executable, but the beauty of TeX is that almost nothing is really "inaccessible" in the sense that it can't be changed. All macros can be redefined -- with only the latest definition being used. \cite{} eventually refers to a macro \@cite that defines the appearence. The default definition is: \def\@cite#1#2{[{#1\if@tempswa , #2\fi}]} I have changed this to: \newif\ifraisedcite%raises citations [1] above line \def\raisedcitations{\raisedcitetrue} \def\noraisedcitations{\raisedcitefalse} \raisedcitations% default % \def\@cite#1#2{% \ifraisedcite\raisebox{3pt}{\footnotesize [{#1\if@tempswa , #2\fi}]} \else [{#1\if@tempswa , #2\fi}]\fi} in a style I designed to allow the option of raising the citations above the lines like footnotes. This option keeps the `[' and `]' but they could just as easily be removed as: \def\@cite#1#2{% \ifraisedcite\raisebox{3pt}{\footnotesize {#1\if@tempswa , #2\fi}} \else [{#1\if@tempswa , #2\fi}]\fi} Then raised citations would not have the brackets. The change DOES require redefining a macro that contains the `@' symbol, normally only done in *.sty files. You can easily put into a file called raisedcite.sty or something and then use \documentstyle[raisedcite]{whatever-style-you-use} -- Terry L Anderson AT&T Bell Laboratories -- Liberty Corners UUCP: ...!att!bartok!tla NET: tla%bartok@RESEARCH.ATT.COM ATTMAIL: mozart!tla (201) 580-4428 ----------------------------------------------------------------------- %%% Further information about the TeXhax Digest, the TeX %%% Users Group, and the latest software versions is available %%% in every tenth issue of the TeXhax Digest. %%% %%% Concerning subscriptions, address changes, unsubscribing: %%% %%% BITNET: send a one-line mail message to LISTSERV@xxx %%% SUBSCRIBE TEX-L % to subscribe %%% or UNSUBSCRIBE TEX-L %%% %%% Internet: send a similar one line mail message to %%% TeXhax-request@cs.washington.edu %%% JANET users may choose to use %%% texhax-request@uk.ac.nsf %%% All submissions to: TeXhax@cs.washington.edu %%% %%% Back issues available for FTPing as: %%% machine: directory: filename: %%% JUNE.CS.WASHINGTON.EDU TeXhax/TeXhaxyy.nn %%% yy = last two digits of current year %%% nn = issue number %%% %%%\bye %%% End of TeXhax Digest ************************** -------