Subject: TeXhax Digest V90 #43 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, May 6, 1990 Volume 90 : Issue 43 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: Real number symbol Denoting the real line in LaTeX postscript previewer dvitovdu previewers oldstyle in latex mailinglabels macro Re: Response to BibTeX question (V90 #40) Re: BibTeX question tex query Control sequences that gobble spaces and <'s that expand to \csname Change typeface completely? TeX and LaTeX TeXhax Digest V90 #41 script macros Latex footnotes raising Plain \big, \Big etc. macros -- problem -------------------------------------------------------------------------- Date: Thu, 26 Apr 90 16:45:33 MEZ From: Erich Neuwirth Subject: Real number symbol Keywords: AmSTeX, real number symbol Answer to Murad Taqqu's question: The symbol you need is contained in the Blackboard bold font for AMSTeX. These fonts usually are made available with style options like amstex.sty or amsfonts.sty available from many TeX related file servers. One of these servers is LISTSERV@DHDURZ1 Erich Neuwirth ---------------------------------------------------------------------------- Date: Fri, 27 Apr 90 08:30 EDT From: "John Charnes, (305) 284-6595" Subject: Denoting the real line in LaTeX Keywords: LaTeX, real number symbol Anand Mehta writes that Murad Taqqu writes: > 3. LaTeX provides a symbol for the real numbers, $\Re$. This is the > symbol for the real part of a complex number. (There is also \Im). But > I need a symbol for the real line, usually denoted R with a double > vertical bar, something like IR. Is there a latex font for this > somewhere. > Murad Taqqu murad@math.bu.edu For my dissertation last year, I used the following kludge in the absence of a blackboard-bold character to denote the real line: \def\Real{\hbox{I\kern-.1667em\hbox{R}}} I tried a similar definition with {\bf I} and {\bf R}, too, but liked the non-boldface version of \Real better. John Charnes jcharnes@umiami.miami.edu Coral Gables, FL ----------------------------------------------------------------------------- Date: Fri, 27 Apr 90 10:08:15 -0400 From: weir@PRC.Unisys.COM Subject: postscript previewer Keywords: Postscript previewer Now that our group has finally managed to acquire a postscript printer, and to print TeX/LaTeX documents on it via one of the various dvi2ps routines, we are now looking for an X-windows based postscript previewer. Does anyone on the this list have any recommendations? If so, could you please recommend an appropriate ftp site? Carl Weir --------------------------------------------------------------------------- Date: Thu, 26 Apr 90 08:49:32 MDT From: gunter@rdsun.STAT.ColoState.Edu (gunter hartel) Subject: dvitovdu previewers Keywords: dvitovdu previewers I have just installed u of washingtons tex on a sparcstation. In the DVIware subdirectory were some dvitovdu previewers that look like they would allow previewing on the likes of TEK4010's. But they were written in modula and dated about 1986. Is there any c-version of this somewhere? gunter hartel dept of statistics csu gunter@euler.stat.colostate.edu thx --------------------------------------------------------------------------- Date: Wed, 25 Apr 90 23:28:23 -0700 From: aho@ucbarpa.Berkeley.EDU (alex ho) Subject: oldstyle in latex Keywords: laTeX, oldstyle how does one get oldstyle numbers in latex? thanks alex ------------------------------------------------------------------------------ Date: Wed. 25 April 1990 From: Paul R. Sternberg Subject: mailinglabels macro Keywords: mailinglabel Does anyone have a macro or .sty file which produces mailing labels in a 3 wide by 11 deep format for an 8.5 by 11 inch sheet? ----------------------------------------------------------------------------- Date: Tue, 24 Apr 90 13:13:12 EDT From: "James C. Alexander" Subject: Re: Response to BibTeX question (V90 #40) Keywords: TiB >Date: Fri, 6 Apr 1990 8:27:55 PDT >>From: George D. Greenwade, Bitnet: BED_GDG@SHSU >Subject: Response to BibTeX question >Keywords: BibTeX > >This is how we generate and maintain rather >lengthy bibliographic databases here (some are in excess of 2,500 entries). >The main problem we have is identifying specific keys to specific cites. >Presently, this is done by hand using the VMS SEARCH command (routine, >whatever; some of the more computer literate know the specific terminology). I will stick in another little blurb here for the bibliographic processor Tib. Tib does not use identifying labels--anything that identifies the item is sufficient--and handles large databases easily and rapidly. It also has a fast lookup utility. The largest database I know of is a laboratory-wide database of some 16,000 entries (in 1988), updated weekly by a secretary with articles appearing in major life-sciences/medical journals. Tib is available from the standard TeX archives. ---------------------------------------------------------------------------- Date: Mon, 23 Apr 90 23:46:22 EDT From: Denys Duchier Subject: Re: BibTeX question Keywords: BibTeX The command \nocite{*} will include all entries of the bibliography file in your bibliography. --Denys --------------------------------------------------------------------------- Date: Thu, 19 Apr 90 06:51:07 PDT From: jdp@ucrmath.ucr.edu (john depillis) Subject: tex query Keywords: TeX, macro I would like to design a macro which would be called as follows: \DoWork{abc} The result within the macro is: 1. Counter \abc is created 2. A new macro, \xabc , is created. After calling macro \DoWork{abc}, I would like to call the induced macro \xabc Can you tell me how dto do this? I am having trouble with the all the backslashes among other things. Thanks, John de Pillis --------------------------------------------------------------------------- Date: Tue, 24 Apr 90 11:25:44 From: Mike Piff Subject: Control sequences that gobble spaces and <'s that expand to \csname Keywords: TeX, control sequences Philip Taylor writes: In the simplest case, one simply defines < and > as \csname and \endcsname respectively: \catcode `\< = \active \catcode `\> = \active \def <{\csname} \def >{\endcsname} One can then write or , with or without trailing punctuation, and the spacing is invariably correct. Of course, this na\"ive approach inhibits the use of less-than and greater-than in other contexts, particularly within the scope of an \ifnum or \ifdim and within maths groups; a better solution is therefore: \def \lt {<} \def \gt {>} \catcode `\< = \active \catcode `\> = \active \def <{\ifmmode \lt \else \csname \fi} \def >{\ifmmode \gt \else \endcsname \fi} which allows such constructs as \ifnum 1 \lt 2 ... \else ... \fi $ 1 < 2 $ In doesn't work! Unfortunately, anyone trying this approach will encounter some pretty weird error messages when using one of these control sequences in, say, a LaTeX array environment, as the very first item in an entry, where a relational operator is certainly possible! The reason is explained on p240 of The TeXbook. The only solution seems to be to use \def<{\relax\ifmmode\lt\else\csname\fi} but that will just mess something else up---a common occurrence with TeX. Mike Piff -------------------------------------------------------------------------- Date: 13 Apr 90 13:58:24 GMT From: krf@venus.ral.rpi.edu (Keith R. Fieldhouse) Subject: Change typeface completely? Keywords: Font, Sans Serif What is the accepted, clean way of causing a LaTeX document to consistently use a Sans Serif font? Most of the users here are happy with the Roman type face produced by LaTeX. One user however strongly prefers a Sans Serif typeface. This user is not particularly sophisticated so what I'm looking for is a simple directive or two that will cause his documents to consistently use this type of font. By consistent I mean the the \em directive will use a slanted SS font, section headings will be in SS, footnotes will be set in a small SS font and so on. I'm aware that this *might* be very ugly but in the interests of giving this user a chance to decide for himself... The \sf directive at the beginning of the document will cause the standard body type to be SS but everything else uses the Roman typeface. In my attempts to achieve this goal it appears that I have been lead to hack at the individual style files which doesn't seem quite right. I've looked at lfonts.tex but I'm not sure where to proceed there either. Has anybody solved a similar problem? If so I'd like to hear from you. Thanks, - Keith F. -- Keith R. Fieldhouse krf@ral.rpi.edu Center for Intelligent Robotic (518) 276-6758 Systems for Space Exploration (CIRSSE) CII 8313 Rensselaer Polytechnic Institute Troy, New York 12180-3590 ------------------------------------------------------------------------------- Date: Thu, 26 Apr 90 08:56:43 EDT From: INHB000 Subject: TeX and LaTeX Keywords: TeX, LaTeX In his question concerning the use of some AMSTeX fonts in LaTeX, Dale Gerdemann shows that he also believes that there is something about LaTeX (or AMSTeX) that is not quite TeX. Well that is simply not true. LaTeX, like AMSTeX and indeed like Plain TeX is nothing but a package of macros that run under TeX. I think it is safe to say that Knuth did not anticipate that Plain would become any sort of standard, merely it was a package that made it possible to use TeX until some more elaborate package came along. It is perhaps unfortunate that the AMS chose to run AMSTeX on top of it, but they did and one result is that it has now become a standard. Now I didn't know that there was a script font in AMSTeX, but a crude way of accessing it is illustrated in the following that accesses the Euler Fraktur fonts: \font\tenfrak=eufm10 scaled\magstep1 \font\sevenfrak=eufm7 scaled\magstep1 \font\fivefrak=eufm5 scaled\magstep1 \textfont12=\tenfrak \scriptfont12=\sevenfrak \scriptscriptfont12=\fivefrak This is followed by a series of definitions of the sort: \mathchardef\Afk="0C41 \mathchardef\Bfk="0C42 \mathchardef\Cfk="0C43 . . . . . . (Note that C is hex for decimal 12.) This gives me characters that scale properly in asscripts (that is, super and subscripts), but do not respond to the LaTeX size changing macros (and in fact are for the 12pt size only). I would have to redefine all \xpt, \xipt, ... macros. One of these days I will work out what has to be done, but so far, it has not been important enough. What someone ought to do is work out an \addfont macro so that we could say something like \addfont{eufm}{frak}{12} and get all the definitions done automatically. There's a nice problem for all the LaTeX haxxers out there. Of course, there are always the calligraphic characters that are already loaded in LaTeX. They can be accessed by {\cal A}, etc, but I also have some definitions: \mathchardef\Asc="0241 \mathchardef\Bsc="0242 \mathchardef\Csc="0243 . . . . . . which causes them to scale properly in asscripts. These are not really script letters, but they are what we have. ========================================================================= I have been meaning to write to TeXhax ever since I heard about TeX 3. So far, I have seen two negatives about TeX 3. First, and most important to me, is the fact that it is going to allow even fewer names than TeX 2. An announcement for TeX 3 in the lates TeXhax mentioned that it would allow only 3050 words, down from 3500. I just finished a book composed using LaTeX with several definitions of my own (for commutative diagrams) and over 500 cross references and we were constantly banging up against that 3500 word barrier (in the end we removed a hundred or so little used macros and replaced them by their definitions everywhere). Reducing the limit by 450 words would have made it impossible to use TeX at all for this project! (Or, more precisely, to use automatic cross references). I think the time has come that a large TeX has to be made mandatory. The second downside is something that I am surprised no one has mentioned. It is that TeX documents done in 8 bit will no longer be able to be sent over email. There is already enough problems with the 96 characters that the networks claim they will transmit. Any time an IBM site is involved there is some chance that some of the 96 will be destroyed. I recall well how the email administrator here reacted with horror when I suggested that it might be reasonable to change their translation tables so that the ebcdic brace characters be translated to the ascii brace characters instead of spaces as is done now. Change their translation tables indeed! Unthinkable. At any rate, someone ought to be seriously thinking how we will manage full 8 bit transmission when version 3 has become generally available. Michael Barr inhb@mcgillb.bitnet inhb@musicb.mcgill.ca -------------------------------------------------------------------------- Date: Thu, 26 Apr 90 09:44:08 EDT From: mernst@theory.lcs.mit.edu (Michael Ernst) Subject :TeXhax Digest V90 #41 Keywords: LaTeX, width, text Regarding my query of a month ago: > Date: Tue, 27 Mar 90 17:21:50 EST > From: mernst@theory.lcs.mit.edu (Michael Ernst) > Subject: Determining width of text > Keywords: LaTeX, width, text > > Howdy! > > I have a macro to draw a box around its argument. > * If the argument is short, I just \fbox it and set it in the running text. > * Otherwise, I set the argument in a \parbox and then \fbox that, > typesetting it on a new line (obviously) and with the following text > typeset on the next line, without paragraph indentation. Three weeks ago I received a solution from a kind reader of comp.text.tex. The problem was that I'd forgotten that hbox'es are set in RESTRICTED horizontal mode, so vertical material such as LaTeX lists are forbidden. The quick and dirty solution is to first set the text in vertical mode; if it's only one line high, I assume it contains no vertical material and reset it in horizontal mode to check the width. Excerpts of the solution appear below. No doubt a better one exists. % Ellipses indicate code I haven't repeated. % ... \makeatletter \long\def\settoheight#1#2{\setbox\@tempboxa\vbox{#2}#1\ht\@tempboxa\relax} \makeatother % ... \newlength{\onelineboxheight} % While I may give multiple paragraphs as an argument, \hbox can't deal % with quotations or other list environments which aren't allowed to appear % in RESTRICTED horizontal mode, so check the height first. \long\def\myboxit #1{\settoheight{\onelineboxheight}{#1}% \ifdim\onelineboxheight>\baselineskip \mywideboxit{#1}% \else \settowidth{\onelineboxwidth}{#1}% \ifdim\onelineboxwidth>\halftextwidth \mywideboxit{#1}% \else\fbox{#1}\fi \fi} % ... --------------------------------------------------------------------------- Date: Mon, 23 Apr 90 21:42:28 PDT From: bsd@sumex-aim.stanford.edu (Bruce Duncan) Subject: script macros Keywords: LaTeX, macros Greetings, Is there a LaTeX style format or TeX macros for making scripts and screenplays? Bruce Duncan bsd@sumex-aim.stanford.edu ---------------------------------------------------------------------- Date: Fri, 27 Apr 90 17:57:33 EDT From: clayton@thumper.bellcore.com (R. Clayton) Subject: Latex footnotes raising Keywords: LaTeX, footnotes If a block of material is too big to fit at the end of the current page, latex (tex 2.98, c 2.35, latex 8 Feb 1989) puts it on top of the next page. However, it also covers the gap at the bottom of the current page by jacking up any footnotes so they appear right after the last of the text on the page. Does anyone have a fix for this, either in latex or in my document? What follows is a file showing the problem. \documentstyle{article} % 16 Mar 88 \def \sentence{Blah blah blah blah blah blah blah blah blah blah.\ } \def \graph{\par\sentence\sentence\sentence\sentence\sentence\sentence} \begin{document} \graph\graph\graph\graph \par\sentence\sentence\sentence\footnote{\sentence\sentence\sentence} \sentence\sentence\sentence \graph\graph\graph\graph \vbox to 3 in {\vfill hello.} \end{document} R. Clayton clayton@thumper.bellcore.com {rutgers!}bellcore!thumper!clayton ------------------------------------------------------------------------ Date: Sun, 29 Apr 90 22:12:53 EDT From: "Prof. David F. Rogers" Subject: Plain \big, \Big etc. macros -- problem Keywords: TeX, Plain, macros % It appears that there is an annomoly in the Plain TeX definitions % Plain TeX defines the following macros for obtaining larger brackets etc. % Notice that the sizes are incremented by 3 pts. % \def\big#1{{\hbox{$\left#1\vbox to8.5\p@{}\right.\n@space$}}} % \def\Big#1{{\hbox{$\left#1\vbox to11.5\p@{}\right.\n@space$}}} % \def\bigg#1{{\hbox{$\left#1\vbox to14.5\p@{}\right.\n@space$}}} % \def\Bigg#1{{\hbox{$\left#1\vbox to17.5\p@{}\right.\n@space$}}} % \def\n@space{\nulldelimiterspace\z@ \m@th} % Define an even bigger function % Note Plain defines \big=8.5pt \Big=11.5pt \bigg=14.5pt \Bigg=17.5pt % \bBig=10pt \Bbigg=13pt \bBigg=16pt \Bbiggg=19pt % \biggg=20.5pt \Biggg=23.5pt \bigggg=26.5pt \Bigggg=29.5pt % \biggggg=32.5pt \Biggggg=35.5pt % Note that increments of 1.5 pt are now `filled in' and the sizes are % extended by simply changing the size number in the Plain macros. \parindent = 0pt \def\nospace{\nulldelimiterspace=0pt \mathsurround=0pt} % no need for catcode \def\bBig#1{{\hbox{$\left#1\vbox to10pt{}\right.\nospace$}}} \def\Bbigg#1{{\hbox{$\left#1\vbox to13pt{}\right.\nospace$}}} \def\bBigg#1{{\hbox{$\left#1\vbox to16pt{}\right.\nospace$}}} \def\Bbiggg#1{{\hbox{$\left#1\vbox to19pt{}\right.\nospace$}}} \def\biggg#1{{\hbox{$\left#1\vbox to 20.5pt{}\right.\nospace$}}} \def\Biggg#1{{\hbox{$\left#1\vbox to 23.5pt{}\right.\nospace$}}} \def\bigggg#1{{\hbox{$\left#1\vbox to 26.5pt{}\right.\nospace$}}} \def\Bigggg#1{{\hbox{$\left#1\vbox to 29.5pt{}\right.\nospace$}}} \def\biggggg#1{{\hbox{$\left#1\vbox to 32.5pt{}\right.\nospace$}}} \def\Biggggg#1{{\hbox{$\left#1\vbox to 35.5pt{}\right.\nospace$}}} \def\xBig#1{{\hbox{$\left#1\vbox to 43pt{}\right.\nospace$}}} % Unfortunately this DOES NOT work. Anyone have any ideas as to why? % Dave Rogers This is a test of the big macros. $$ \big[\bBig[\Big[\Bbigg[\bigg[ $$ The second two square brackets are the same size and the last two brackets are also the same size when they should vary by 1.5 pts. In addition the first bracket is actually 12 pts high when it should be 8.5 points high, the second is 18 pts high and should be 10 pts and the last is 24 pts and should be 14.5 pts! Either I do not understand something or something is wrong. Any ideas as to why? \end ----------------------------------------------------------------------- %%% 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 ************************** -------