Subject: TeXhax Digest V90 #32 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 Sunday, March 18, 1990 Volume 90 : Issue 32 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: Re: Bug in LFONTS.TEX, \mathbold Fonts for Classical Greek LaTeX, line LaTeX and PiCTeX macros LaTeX, scientific journals Re: section headings Escapable Verbatim Environment Metafont help ---------------------------------------------------------------------------- Date: Thu, 8 Mar 1990 14:34:23 CET From: Rainer Schoepf Subject: Re: Bug in LFONTS.TEX, \mathbold Keywords: bug, lfonts.tex On 02/15/90 11:25:37 GMT+1 F. Kammer said >Trying to get bf letters in math formulas I ran across a bug in >lfonts.tex (in all versions I have seen). The cmmibXX fonts are >usually not preloaded (commented out in the definition part of >lfonts.tex). The \mathbold command, as defined in this file, works >only for that case. If you think you need these fonts more frequently >and modify it to preload them (so that they are known by LaTeX) the >\mathbold command runs into a recursive loop: the program seems >to freeze and you see what happens if you add \typeout{something} >at the top of the \mathbold definition. (This holds only for the >definitions for larger sizes, such as \xiipt, where \boldmath is >really defined). F.Kammer It is true that \boldmath goes into an infinite recursion when you preload the bold math italic and symbol fonts. However, the important point here is that there is no need to preload them since they are loaded on demand. If you preload the bold math fonts you also have to change the definition of the \boldmath macros. I don't think that this `bug' is worth correcting it. The new font selection scheme and its interface to LaTeX are ready for use, and I don't see any point in putting much work into an obsolete piece of software. Rainer Sch\"opf -------------------------------------------------------------------------- Date: Wed, 7 Mar 90 15:01:35 PST From: young@sierra.Stanford.EDU (James F. Young) Subject: Fonts for Classical Greek Keywords: fonts, classical Greek Can anyone point me to a source for fonts for classical greek, as opposed to mathematical greek, including all its strange iota subscripts, accents, breathing marks, etc.? A set of macros would do; I don't need to typeset a book, just passages of a few lines at a time. I am using MicroTeX on an IBM PC, a Textset dvi -> postscript driver, and an Apple laserwriter. Ideally, I would like tfm files and 300 dpi pixel files. Thanks, Jim Young, young@sierra.stanford.edu EE Dept, Stanford Univ. 415-723-1674. ----------------------------------------------------------------------------- Date: Thu, 8 Mar 90 10:21:08 GMT From: Martin Ward Subject: LaTeX, line Keywords: LaTeX, line How can I tell if I am at the beginning of a line in LaTeX? I am trying to set up a \proof macro which starts a new line, does a \medskip to leave a small space, typesets $\bf Proof: and switches to roman font. This is so I can write: \begin{theorem} Every even number is the sum of two primes. \proof Consider the even number $2n$ where $n>1$ ... \end{theorem} For this I use: \newcommand{\proof}{\medskip\newline{\bf Proof: }\rm} However, if the theorem finishes with an equation such as: \begin{theorem} \begin{equation} a+b = b+a \end{equation} \proof By induction on b... \end{theorem{ then I get an extra blank line after the equation. In this situation what I want \proof to do is: \newcommand{\Proof}{{\bf Proof: }\rm} But it's annoying to have to choose between \proof and \Proof. Martin. My ARPANET address is: martin%EASBY.DUR.AC.UK@CUNYVM.CUNY.EDU OR: martin%uk.ac.dur.easby@nfsnet-relay.ac.uk UUCP:...!mcvax!ukc!easby!martin JANET: martin@uk.ac.dur.easby BITNET: IN%"MARTIN@EASBY.DURHAM.AC.UK" ------------------------------------------------------------------------------ Date: Wed, 7 Mar 90 22:35:30 PST From: "Bill Anderson" Subject: LaTeX and PiCTeX macros Keywords: LaTeX, PiCTeX Dear TeX Folks, Last month I ordered Tex for my PC from TeX Users Group in Providence, RI. I've been please with the quality typesetting after converting a 400 page manual to TeX input form. The next task is a 2000 page engineering materials handbook for Chemical Abstract Service. The TeX input will be generated automatically after extracting information from a database. However, a number of questions have arisen when using both the LaTeX and PiCTeX macros. I have made my living writing software for 15 years, and so could engross myself into TeX format and style files. But with deadlines to meet, it's more efficient to tap the minds of TeXperts. I was advised by the TeX User's Group that texhex@score.stanford.edu was the community of users that discuss TeX issues from the "production" point of view. If this is the case, is there an electronic mail subscription service that I can join? I am particularly interested in merging text and graphics. The immediate problem is the string pool size when using both LaTeX and PiCTeX macros. Is there a way to fix this: should plain.tex be used in lieu of LaTeX, can string pool size be increased, etc.? Thank you, Bill Anderson xb.n64@forsythe.stanford.edu ---------------------------------------------------------------------------- Date: Wed, 7 Mar 90 20:21 N From: Subject: LaTeX, scientific journals Keywords: inforamtion, scientific journal On 5 Feb 90, Dave Love asked the TeX community > In the physics world, the Physical Review series and the Journal of > Physics series accept TeX -- the former LaTeX, the latter a rather nasty > set of macros for plain. Springer Verlag (Zeitschrift F\"ur Physik) > also either do or will shortly and there is a rumour that Nuclear > Physics do, although they haven't advertised the fact. The rumour about Nuclear Physics is quite old. NP -- abbreviation of journal, not my initials! -- is published by Elsevier Science Publishers (Amsterdam, the Netherlands), where I am currently working on document styles for ESP journals and book series: NP is one of these journals. Later this year ESP will start accepting LaTeX compuscripts for some of their journals. TeX compuscripts and other types of compuscripts will follow! 1. This is not an official announcement 2. More about this at the TeX'90 meeting in Cork Nico A.F.M. Poppelier -------------------------------------------------------------------------- Date: Thu, 8 Mar 90 05:53 PST From: DHOSEK@hmcvax.claremont.edu Subject: Re: section headings Keywords: LaTeX, style files > I tried looking around ARTICLE.STY, ART10.STY, etc > but cannot get a solution. It is very likely that > the solution is quite trivial. > The problem: How do I get section headings \centerlined > instead of left aligned? Also I want the beginning of > the section to begin \noindented, and all subsequent > paragraphs begin \parindented. Same for subsections etc. > A related query: if I make any change to ART--.STY, can > I make a separate "patch" file, call it MY.STY, include it > with \documentstyle[my]{article} statement, and at the > same time continue using the other features of the original > ART--.STY? Please ignore this question if it doesn't > make sense! First, if you are modifying styles or just trying to see how they work, rather than look at the .sty file, you will want to look at the .doc file which is simply the .sty file with comments (most of the contributed style files above skip the distinction and use the .doc files as .sty files--the need for two kinds of files is for the most part a historical relic). This distinction is described in the LaTeX book. The rest of this answer is not. The standard interface for creating section headers with LaTeX 2.09 is a macro called \@startsection. Most, but not all section headings are defined using this command which is documented in each of the art--.doc, bk--.doc, and rep--.doc files where it is used. A typical definition for a sectioning command looks like the following (from art10.doc): >\def\section{\@startsection {section}{1}{\z@}{-3.5ex plus -1ex minus > -.2ex}{2.3ex plus .2ex}{\Large\bf}} The first argument to \@startsection is the name of the sectioning unit. This is used for such things as determining the proper macro to write the table of contents entry, selecting the counter for numbering that unit, etc. The second argument is the level of the sectioning unit. In the article style, for example, part=0, section=1, subsection=2, ... in report or book it becomes part=-1, chapter=0, section=1, ... This is used in conjunction with the value of the counter secnumdepth to determine whether section numbers are to be printed. For example, \setcounter{secnumdepth}{-10} will prevent any numbering on parts, sections, etc. The third argument is the indentation of the heading from the left margin. Choosing a negative value allows one to have headings that "jut out" into the left margin. The fourth argument is the amount of space to leave above the heading. If the value is negative, the absolute value of the fourth argument gives the space and paragraph indentation is suppressed. The fifth argument contains the same sort of switch based on the sign of its value. A positive value indicates the amount of space to be left below the heading, a negative value indicates the horizontal space to be left between a run=in heading and the text which follows it. Finally the sixth value indicate the style of the heading. This typically only contains commands like "\large\bf" and the like, but it can also contain other LaTeX commands as well, e.g., \centering. The effect you desired can be achieved using the following definition for ten point text: >\def\section{\@startsection {section}{1}{\z@}{-3.5ex plus -1ex minus > -.2ex}{2.3ex plus .2ex}{\centering\Large\bf}} This leaves the issue of writing size-specific code, which you would doubtless want to do for something of this nature. There are two options for doing this: the first is to simply mimic what the article, book, and report styles do and insert a line along the lines of \input my1\@ptsize.sty with my10.sty, my11.sty, and my12.sty containing the relevant code. The alternative, lifted from letter.doc is to do something like the following (this works well if the amount of code is small and you want to keep the number of files down): \ifcase\@ptsize\relax \or \or \fi However, since your code is also style-specific, you may want to set up your style file (let's call it myarticle.sty) as follows: %-----Beginning of myarticle.sty--------------------- %If you want to add any document style options, put them here %by defining \ds@OPTION where OPTION is the name of the option, %e.g., to define an option himom which sends a message to the %terminal, I could define: \ds@himom{\message{Hi Mom!} % With LaTeX 2.09, it is not possible to use this technique to % redefine options. On the other hand, the common technique of % defining these things as an option doesn't even give us this % capability. %--- % Here, we will bring in the document style upon which we are % building our style: \input article.sty %--- % And at this point, everything that we would have put into the % document style option should follow. %------End of myarticle.sty This style would then be used via \documentstyle{myarticle}. Some of the benefits are outlined above. Style hackers will realize others as they experiment with this technique. As an added aside, people interested in writing LaTeX style files "correctly" will be interested to know that the TeX Users Group will be having a course in LaTeX style file design the week before the TUG meeting at Texas A&M University. For more details, contact the TeX Users Group: P.O. Box 9506 Providence, RI 02940-9506 (USA) 401-751-7760 tug@math.ams.com -dh ------------------------------------------------------------------------- Date: Wed, 7 Mar 90 17:04:23 EST From: Denys Duchier Subject: Escapable Verbatim Environment Keywords: LaTeX, environment, font changes I wrote the example environment a long time ago to do verbatim-like output with font changes. Last week, I added the comment environment (available only inside example) to allow the insertion of comments, processed like normal text and possibly offset from the left margin, in an example listing. Perhaps others will find this useful too. --Denys %-----File: example.sty---------------------------------------------- % Copyright Denys Duchier, Yale University, 1988. % % \begin{example}...\end{example} is very much like verbatim, except % that it doesn't change the meaning of \, { or }. This makes it % possible to include commands (such as font changes) in otherwise % verbatim text. % % \begin{example*}{OFFSET}...\end{example*} is the same except that % everything is indented by OFFSET. This works even inside other list % environments. % % inside example, you can use \begin{comment}...\end{comment} to % include normal TeX text. \begin{comment}[OFFSET] will offset the % comment by the specified offset. \newdimen\exampleleftmargin \exampleleftmargin\z@ \def\examplesavespecials{\let\xmpl@space\ \let\xmpl@dollar\$ \let\xmpl@amper\&\let\xmpl@hash\#\let\xmpl@caret\^\let\xmpl@cntlK\^^K \let\xmpl@underscore\_\let\xmpl@cntlA\^^A\let\xmpl@percent\% \let\xmpl@tilde\~} \def\examplerestorespecials{\let\ \xmpl@space\let\$\xmpl@dollar \let\&\xmpl@amper\let\#\xmpl@hash\let\^\xmpl@caret\let\^^K\xmpl@cntlK \let\_\xmpl@underscore\let\^^A\xmpl@cntlA\let\%\xmpl@percent \let\~\xmpl@tilde} \def\exampledospecials{\do\ \do\$\do\&\do\#\do\^\do\^^K\do\_\do\^^A\do\%\do\~} \def\example@verbatim{\let\comment\xmpl@comment\let\endcomment\xmpl@@endcomment \list{}{\parsep\parskip \leftmargin\exampleleftmargin \labelwidth\z@ \itemindent\z@ \def\makelabel##1{##1}}\item[]\if@minipage\else\vskip\parskip\fi \leftskip\@totalleftmargin \rightskip\z@ \parindent\z@ \parfillskip\@flushglue \parskip\z@ \@tempswafalse \def\par{\if@tempswa\hbox{}\fi\@tempswatrue\@@par}\obeylines\tt \examplesavespecials \let\do\@makeother\dospecials} \def\@example{\let\dospecials\exampledospecials \example@verbatim\frenchspacing\@vobeyspaces} \def\example{\exampleleftmargin\z@\@example} \let\endexample\endlist \@namedef{example*}#1{\exampleleftmargin#1\@example} \expandafter\let\csname endexample*\endcsname\endexample % \def\xmpl@comment{\@ifnextchar [{\xmpl@@comment}{\xmpl@@comment[0pt]}} \def\xmpl@@comment[#1]{\begingroup \examplerestorespecials \catcode`\ =10 \catcode`\^^M=5 \list{}{\leftmargin\exampleleftmargin \advance\leftmargin #1}\item[]\rm\ignorespaces} \def\xmpl@@endcomment{\endlist\endgroup\vskip-\baselineskip} --Denys ---------------------------------------------------------------------------- Date: Thu, 08 Mar 90 08:27:08 GMT From: Mr. Stephen Culshaw Subject: Metafont help Keywords: METAFONT I have been using METAFONT to generate various fonts for the Atari TeX previewer SHOWDVI.TTP. I have hit a problem and with only very limited knowledge of METAFONT, I would appreciate any suggestions as to the cause of the fault. I have been able to generate the 144gf and 249gf sizes but when I try to generate the 173gf, this is what I get. This is METAFONT, C Version 1.5 (no base preloaded) ** \mode=catari;\mag=1.802;input cmss10 (.\cmss10.mf (.\cmbase.mf) (.\roman.mf (.\romanu.mf [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90]) (.\romanl.mf [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108] [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122]) (.\greeku.mf [0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]) (.\romand.mf [48] [49] [50] [51] [52] [53] [54] [55] [56] [57]) (.\romanp.mf [36] [38] [63] [62]) (.\romspl.mf [16] [17] [25] ! bad pos. ; pos->...XPR3)<=currentbreadth:errmessage"bad pos"; fi.fi(x(SUFFIX2)r-x(SUFFIX... l.84 pickup tiny.nib; pos11(right_curve,0) ; ? [26] ! bad pos. ; pos->...XPR3)<=currentbreadth:errmessage"bad pos"; fi.fi(x(SUFFIX2)r-x(SUFFIX... l.138 pickup tiny.nib; pos11(right_curve,0) ; ? Also does any one have the neccessary .MF file for generating the fonts for the Atari SLM804. Someone posted me a .MF file previously but it required a couple of files that I've not been able to find - ie. PLAIN.MF version 1.0a and the corresponding CMBASE.MF - does anyone have them. The problem relates (I think) to the Atari laser being 'write-white' % stlaser mode: to generate fonts for the Atari ST laser printer SLM804 mode_def stlaser = proofing:=0; % no, we're not making proofs fontmaking:=1; % yes, we are making a font tracingtitles:=0; % no, don't show titles at all pixels_per_inch:=300; % that's pretty low resolution blacker:=-.25; % less blackness fillin:=.5; % compensate for diagonal fillin o_correction:=0; % normal overshoot write_white_engine:=true; % You have to use the modified PLAIN.MF V1.0a % and the corresponding CMBASE.MF, which has % to be modified according to TUGboat 1/1987) enddef; Thanks for any help Steve C. ----------------------------------------------------------------------- %%% 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 ************************** -------