HDTenEightyP/NetNews huggingface dataset:
From: hank@ducvax.auburn.edu
Subject: Re: DUAL HANDOUTS/PERSONAL NOTES MACRO IDEA
Organization: Auburn University, AL
Date: Thu, 3 Sep 1992 02:58:20 GMT

In article <1992Sep2.154831.22839@athena.mit.edu>, lasmith@athena.mit.edu (Lones A Smith) writes:
> for editing purposes.   Here's what I want: I want to prefix the additional
> comments for my expanded version of the notes by a symbol --- call it ** ---
> so that lines preceeded by ** are only printed out when a particular control sequence in the preamble is present.  That is,
> 
> privatenotes.tex
> 
> Control sequence present
> ** personal extra remarks
> Class notes
> 
> classhandout.tex
> 
> Control sequence NOT present
> ** personal extra remarks
> Class notes
> 
> Then when I LaTeX the first file, the ** should be ignored entirely, whereas when I LaTeX the second file ** should be read as %.  Brute force methods
> have failed me.  Any ideas, (La)TeXperts??????

It is a different solution, but you might get DM Jones' tex-index from 
niord.shsu.edu and look up version.sty by  Piet van Oostrum.

If you really want to use a beginning-of-every-line-flag, you might consider
something as simple as '%**' and use tr (a GNU utility) to translate, then
feed to TeX. tr for os/2 can be found on ftp-os2.nmsu.edu in pub/os2/all/gnu
(for OS/2 1.x) or pub/os2/2.0/gnu (for OS/2 2.0).

--darrel hankerson hank@ducvax.auburn.edu
From: "Daniel H. Luecking" <DL24794@UAFSYSB.UARK.EDU>
Newsgroups: comp.text.tex
Subject: Re: \outer
Date: Fri, 04 Sep 92 12:13:47 CDT
Organization: Info-Tex<==>Comp.Text.Tex Gateway
X-Gateway-Source-Info: Mailing List


On 3 Sep 92, eijkhout@cupid.cs.utk.edu (Victor Eijkhout) said (among other
things):

>
>The outer-ness implies that such macros cannot appear as macro
>arguments or in macro bodies,
>something that makes sense for things such as \theorem.
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Wrong. I write mathematical papers and am mostly content with plain TeX's
\proclaim macro. But sometimes I have to add material in front of or after
every theorem. The easiest way to do this is (or would be if not for
\outer-ness)

\def\Proclaim#1#2\par{%
<preliminary stuff>\proclaim#1. #2\par<closing stuff>}

Another possibility denied me: \def\lemma#1\par{\proclaim Lemma. #1\par}

According to the TeXbook ``...a user shouldn't be stating a theorem as part
of a definition...''
I can't think of any sentence in the Texbook more absurd than this one!
I don't want to state a theorem, just modify the definition of \proclaim
without having to rewrite the whole thing.

The stated reason (in the TeXbook) for \outer-ness is as an error catching
tool. However, the error messages generated are singularly unhelpful. Moreover
\outer macros are forbidden ``where tokens are being absorbed at high spead''.
What has the speed of absorption got to do with error trapping? I wonder what
Knuth was thinking. One of these days I will delete all instances of \outer
from plain.tex (renaming it of course) and complile a format without it.

>However, for the \newxyz macros I (and others with me) feel htat
>this decision was wrong.

I agree.

>
>Victor.
>

Dan Luecking
Newsgroups: comp.text.tex
From: hm342st@unidui.uni-duisburg.de (Michael Staats)
Subject: Re: After effects of using DEMACS
Date:  4 Sep 92 09:15:27 GMT
Distribution: comp
Organization: Rechenzentrum Uni-Duisburg

In <ARA.92Sep3210741@camelot.ai.mit.edu> ara@zurich.ai.mit.edu (Allan Adler) writes:



>In an earlier message, I said I had the following problem:
>(1) I use DVIVGA and have no difficulty using the arrow keys and page up,
>    page down, home, end keys with it.
>(2) I use DEMACS and then exit DEMACS
>(3) I use DVIVGA and the arrow keys, home,end,pageup,pagedown don't work any 
>    more.


>One possibility is that DEMACS has some kind of Terminate and Stay REsident
>feature, but I doubt that. So the other possibility that occurs to me
>is:
>(a) when DEMACS starts up, it somehow redefines the keyboard, using termcap
>    information and stuff in some file in the directory TERM.
>(b) when it exits, DEMACS does not clean up after itself and restore the
>    original settings.

That sounds correct. At startup, demacs redefines the keyboard using
ANSI conrol sequences. Usually this is cleaned up after exit. This
is all done in ibmpc.el. Maybe your version is messed up for some
reasons. First you should check that ibmpc is loaded at startup.
In your _emacs you should have:
(setq dos-machine-type 'ibmpc)
and you should have "unqouted" the lines following 
;; IBMPC initialization
;;   function keys, cursor keys, meta key (by ALT)

If this is correct, delete ../term/ibmpc.elc and byte-compile ibmpc.el
again.
If this doesn't help, get a new ibmpc.el and byte-compile it.
If this doesn't help, ask again (not me :-).

So long, Michael

-- 
Michael Staats, Student of Theoretical Physics, Uni-GH Duisburg 
Wenn dieser Artikel in Deutsch ist: Bitte entschuldigt meine Fehler.
If this article is in english: Please excuse me for my mistakes. 
if (written_in_C(&article)) mistake_msg_to("michael@hal6000.uni-duisburg.de");
From: aix3!wjg@netcom.com (Joey Gibson)
Newsgroups: comp.text.tex
Subject: JTeX comments?
Date: 1 Sep 92 18:02:40 GMT
Organization: Info-Tex<==>Comp.Text.Tex Gateway
X-Gateway-Source-Info: Mailing List

I was just out at akiu.gw.tohoku.ac.jp, and I found JTeX in the Macintosh TeX
directory. There was a file mentioning MPW in the name. Does anyone use JTeX?
If someone could tell me about it, maybe compare it to OzTeX (since that is
what I am currently using), I would greatly appreciate it.
Thanks.


Joey Gibson

=> "In the country of the blind, the one-eyed man is king." H.G. Wells <=
   ===> The views expressed here are not necessarily those of EMA. <==
From: strat@cutlass.ksu.ksu.edu (Steve Davis)
Newsgroups: comp.text.tex
Subject: Literal display of files.
Date: 31 Aug 1992 22:29:56 -0500
Organization: Kansas State University
NNTP-Posting-Host: cutlass.ksu.ksu.edu

This is probably a very frequently asked question, but ...

How do I do a literal display of files?  I'd like to do something like

\literaldisplayoffile filename.txt

... which would read in the text file and display each character
literally, rather than interpreting them a la \input.

Stratocaster

-- 
  Steve Davis  |    Contact me at ...            | The Boarding House BBS!
               | Internet:  strat@cis.ksu.edu    | 9600 baud (v.32/v.42)
               | FidoNet:    Steve @ 1:295/3     | America: 913-827-0744
Drug Violence exists not because of drugs, but because they are illegal!
Newsgroups: comp.text.tex
From: wijk@fys.ruu.nl (Rob van Wijk)
Subject: dvi2pcl3 or ps2pcl3 convertor
Summary: I'm looking for a dvi2pcl3 convertor for a HP-deskjet 500
Keywords: pcl3,dvi,tex
Organization: Physics Department, University of Utrecht, The Netherlands
Date: Wed, 2 Sep 1992 08:30:01 GMT

I'm looking for a dvi2pcl3 convertor or a ps2pcl3 convertor so I can print
my DVI-files on a HP-deskjet 500. Does anybody have this program, or a
program that is capable of doing such a thing?

Maybe somebody can help me.

Rob van Wijk
Surface Science Division
Debije Institute
Utrecht State University 
The Netherlands
From: eijkhout@cupid.cs.utk.edu (Victor Eijkhout)
Newsgroups: comp.text.tex
Subject: Re: moving DVI files from ASCII to EBCDIC
Date: 28 Aug 92 03:37:04 GMT
Organization: University of Tennessee, Knoxville - Department of Computer Science
Distribution: world
Reply-To: eijkhout@cupid.cs.utk.edu (Victor Eijkhout)
NNTP-Posting-Host: cupid.cs.utk.edu

In article <1992Aug28.010819.1940@umr.edu>, mcastle@mcs213d.cs.umr.edu (Michael R Castle) writes:
|> Our local IBM mainframe has a 3820 laster printer on it that can handle 
|> duplex printing.  The mainframe has TeX and dvi support for the 3820, but
|> I'd rather use the TeX system on our unix system.  My problem is moving the
|> dvi files from the ascii based unix system to the ebcdic based ibm mainframe.
|> 
|> I've done a little of of looking and asking around, but can't seem to find
|> anything that looks like it would be useful for making an easy transition
|> between the systems.

You don't say that you have tried to simply transport the dvi files and
that you've failed. Have you tried simply binary transporting them?

(Dvi files are completely byte-based, so it should work. In the past I've
moved dvi files from an Atari-st to a Unix system, and they printed
perfectly.)

|> Mike Castle

Victor.
From: "Daniel H. Luecking" <DL24794@UAFSYSB.UARK.EDU>
Newsgroups: comp.text.tex
Subject: Re: \font command
Date: Mon, 31 Aug 92 11:04:29 CDT
Organization: Info-Tex<==>Comp.Text.Tex Gateway
X-Gateway-Source-Info: Mailing List


On Friday, Aug. 28, 1992, I posted a query about a posting that appeared
on netnews. I referred to the following line in that posting:

>  > \font\opt12=optima at 12 pt

and I opined that the syntax was wrong and queried as to the nature of the
error.  I recieved two replies:

From "Raymond Chen" <rjc@math.Princeton.EDU>

 > Remember that <equals> can be the null string.  So this defines \opt to
 > refer to the font "12=optima".

I probably  should have included more of the original posting. The only error
message produced was a ``font not found loadable'' message saying optima.tfm
was unavailable. Because of this I assumed that TeX correctly read optima as
the font name and I did not check into the definition of <equals> (which is
<optional spaces> | <optional spaces>=_12 and is a non-intuitive way of saying
the more intuitive: <optional spaces><optional =_12>).  So Raymond seems to be
right, but it doesn't explain why the message did not refer to font
``12=optima''.

-------------------

From: Peter Galko <galko@trix.genie.uottawa.ca>

 > You are attempting to define a font name (like opt10) which is illegal
   ^^^
    | Actually the original poster was attempting this.

 > since font names have names which must conform to the rules for control
 > sequence names (see p. 277 in the TeXbook).  The Texbook explains on p. 7
 > that control sequences can only include letters (numbers are explicitly
 > ruled out), which really means characters currently set to have category
 > 11.

Again, I should have explained more. I was trying to understand the nature of
error message recieved, and jumped to the conclusion that \font would take
a control sequence with a delimiter (which is what happens after \def if a
non-category 11 character follows a control sequence being \def'ed).

I still don't understand the reason for the error messages reported in the
original post (which I neglected to keep).

Dan Luecking.
From: hm308ba@unidui.uni-duisburg.de (Mathias Bartsch)
Newsgroups: comp.text.tex
Subject: How to change "lineskip" in stables ?
Date: 3 Sep 92 13:00:30 GMT
Organization: Rechenzentrum Uni-Duisburg

Hi, TeX-Folks

Would someone please tell me how to change the "lineskip"
in a table produced with the "stables" macros?

I want to typeset a table in \scriptsize and want the lineskip 
to shrink in the same ratio.

Is there a way to switch these parameters inside a table 
(... again and again)?

Thanks in advance!
	
 +----------------------------+-----------------------------------------+
 |       Mathias Bartsch      |  Laboratorium f. Festkoerperphysik      |
 |   Uni -GH- Duisburg (FB10) |  phone : +49 203 379 3476               |
 |       Lotharstr. 1-21      |  Email : hm308ba@unidui.uni-duisburg.de |
 |      W-4100 DUISBURG 1     |  FAX   : +49 203 379 3163               |
 +----------------------------+-----------------------------------------+
From: smith@michael.harvard.edu (Steven Smith)
Newsgroups: comp.text.tex
Subject: Re: Help with "degree" symbol
Date: 4 Sep 92 19:54:43 GMT
Article-I.D.: michael.SMITH.92Sep4145443
Organization: Harvard Robotics Lab, Harvard University
Cc: finvers@enel.ucalgary.ca

finvers@enel.ucalgary.ca (Ivars Finvers) writes:

> I'm stuck. I'm writing a paper where I need to state temperatures
> in degrees C. I can't for figure out how to get LaTeX to generate
> "degree symbol"C.

Paper burns at $451\,^\circ$F (or at $451\,^\circ\rm F$).

Even if you plan to use only LaTeX, get a copy of the TeXbook if only
for chapters 16-19, which describe how to typeset mathematics properly
using TeX.

Steven Smith
From: nelson@hepxvt.ps.uci.edu (Matt Nelson)
Subject: EmTeX installation confusion...
Summary: where are fonts for dviscr?
Newsgroups: comp.text.tex
Keywords: EmTeX, dviscr, fonts
Date: 27 Aug 92 14:59:40 GMT


I recently downloaded EmTeX from ymir.claremot.edu, installed all of the
packages that they had at that site, and proceded to check it out...
LaTeX works fine (at least so far), TeX works (I think), but dviscr
cant find its fonts.  The installation docs mention "copy the fonts to
disk".  Where are these fonts?  I couldnt find them at ymir; am I supposed
to use METAFONT to create them?  If so, how?  If the net could save me
a day of experiments, I would be happy.

If it matters, this is being installed on a notebook, and I dont have a 
printer.  All I want is to be able to write/preview.

thanks much in advance,
matt (nelson@master.ps.uci.edu)
Newsgroups: comp.text.tex
From: todd@vanilla.princeton.edu (Todd J. Mitty)
Subject: BOLDFACE GREEK IN LaTeX
Originator: news@nimaster
Organization: Princeton University
Date: Tue, 1 Sep 1992 15:02:53 GMT


Please see page 53 in the LaTeX manual!!
           -------

I use the following macro:

           \def\boldsymbol#1{\mbox{\boldmath$#1$}}


So, if you want a bold kappa for example, just use $\boldsymbol{\kappa}$  .


Todd
Newsgroups: comp.text.tex
From: piet@cs.ruu.nl (Piet van Oostrum)
Subject: Re: How to write a tricky macro \rcs{} (TeXinfo).
Date: Thu, 27 Aug 1992 10:11:03 GMT
Reply-To: piet@cs.ruu.nl (Piet van Oostrum)
Organization: Dept of Computer Science, Utrecht University, The Netherlands

You can use the package (rcs.sty) with texinfo if you add the following:

\catcode`\$=12\catcode`\@=11

at the beginning and

\catcode`\@=12

at the end, and dot the \input rcs before the \input texinfo.

For the use of the macros you must use @RCS rather than \RCS.
-- 
Piet* van Oostrum, Dept of Computer Science, Utrecht University,
Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands.
Telephone: +31 30 531806   Uucp:   uunet!mcsun!ruuinf!piet
Telefax:   +31 30 513791   Internet:  piet@cs.ruu.nl   (*`Pete')
Newsgroups: comp.text.tex
From: James Petts <pettsj@visigoth.demon.co.uk>
Subject: Egyptian Language Fonts
Organization: No Affiliation
Date: Thu, 3 Sep 1992 07:15:20 GMT
X-Useragent: Nuntius v1.1

Before I go ahead and start coding up between 800 and 3000 glyhps in 
METAFONT I thought I'd ask out here. Does anybody know of any 
hierogyphic, demotic or hieratic fonts available for typesetting Middle 
Egyptian?

James Petts
********************************************************************
* "We use the classical theory on Mondays, Wednesdays and Fridays, *   
*  and the quantum theory on Tuesdays, Thursdays and Saturdays."   *
************************************** Wm. Bragg *******************
From: iwsbarke@acs.ucalgary.ca (Scott Barker)
Newsgroups: comp.text.tex
Subject: need help with a LaTeX macro
Date: 28 Aug 1992 16:45:44 -0500
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

Sorry if this shows up more than once - it didn't seem to work the first time
------------------------------------------------------------------------------

Hi, I'm having problems with a macro, and I was wondering if anyone could
help. I started with a command:

\verb"some text"\\

Which I wanted to change into a macro:

\type{some text}

So I defined the macro as:

\newcommand{\type}[1]{\verb"#1"\\}

Which works fine, except when {some text} contains special characters such as
#$_ etc. Now, when I do:

\verb"# comment line for some programming language"\\

There is no problem, but when I use my macro:

\type{# comment line for some programming language}

LaTeX complains (actually, I think it is TeX complaining) about improper use
of the # character.

Any ideas why the command works, but the macro doesn't?

Thanks for any help you can give.

--
Scott Barker
barker@enel.ucalgary.ca

"Logic is the beginning of wisdom, not the end."
   - Spock, Star Trek VI: The Undiscovered Country
Newsgroups: comp.text.tex
From: gtoal@pizzabox.demon.co.uk (Graham Toal)
Subject: PS CM Fonts? 
Distribution: world
Organization: Cuddlehogs Anonymous
Date: Thu, 27 Aug 1992 17:05:25 +0000


In article <1992Aug25.091026.20378@ccsun.strath.ac.uk> clcp16@ccsun.strath.ac.uk writes:
>A long time away from Usenet, and a very unreliable
>news reader lost me the original article. Could
>someone please point me in the direction of the
>original poster, or the site on which these fonts
>may be found? Thanks.
>
>(I'm not confusing these with Blue Sky's commercial
>efforts --- this was a totally independent project.)

If it was that long ago, it was probably my effort.  They were just an
experiment and weren't very good quality tracings of large bitmaps.  I'm
fairly sure someone else has done it better since then.  Don't know
where mine were kept - I didn't keep them.  Try an 'archie' search
for cmr10.ps perhaps?

G
Newsgroups: comp.text.tex
From: phfrom@nyx.uni-konstanz.de (Hartmut Frommert)
Subject: BibTeX (was Re: SliTeX) Logo?
Organization: Dept. of Physics, University of Constance
Date: Thu, 27 Aug 1992 15:43:55 GMT

Is it defined somewhere in latex.tex or so and not only in some btxdoc or so
files  ? (-: ok, I can take it from there also :-)
--
 Hartmut Frommert, Physics, Univ of Constance, | + Whale killing is murder. +
 P.O.Box 55 60, D-W-7750 Konstanz, Germany | + Eat whale killers, not whales.
 E-Mail: <phfrom@dknkurz1.bitnet> or <phfrom@nyx.uni-konstanz.de>
+    "Windows NoT" expands in German to "Windows Noch Teurer"
+                                                ^even   ^more expensive
From: orloff@surya4.cern.ch (Jean Orloff)
Subject: Re: Rokicki's EPSF macros
Organization: CERN, European Research Center for Particle Physics
Date: Thu, 3 Sep 1992 15:14:12 GMT

>>>>> On 2 Sep 92 16:12:14 GMT, skyvington@republique.ilog.fr (William Skyvington) said:
Wil> I save my Illustrator documents with the PICT option (in the
Wil> dialog box) set to "Macintosh black and white". As for my MacDraw
Wil> Pro stuff, I've got into the habit of always saving it as EPSF.
Wil> Consequently, when I'm working with Textures, I actually see all
Wil> this artwork on the screen in my typeset window. So, all this is
Wil> marvelous!

Wil> BUT... there's a hitch. When I boot up A/UX and drag all this
Wil> stuff across into the Unix file system, and try to run it with
Wil> our network LaTeX system (using exactly the same style macros as
Wil> in Textures), the Rokicki EPSF macros don't seem to be able to
Wil> handle the MacDraw Pro EPSF files and the Illustrator files saved
Wil> with the PICT option set to "Macintosh black and white". The
Wil> LaTeX document appears to get typeset, but the results are
Wil> garbage wherever an illustration is meant to appear. And the
Wil> resulting .dvi file hangs up the laser printer.

Wil> If I save my Illustrator documents with the PICT option set to
Wil> "none (with EPSF header)", everything works perfectly with the
Wil> Rokicki EPSF macros on the Unix Latex system. On the other hand,
Wil> I don't seem to be able to do anything at all with the MacDraw
Wil> Pro artwork.

Wil> Can anybody tell me whether the Rokicki EPSF macros can be
Wil> modified so that they'll work in a Unix LaTeX environment with
Wil> both MacDraw Pro EPSF files and Illustrator files with the PICT
Wil> option set to "Macintosh black and white"?

epsf.sty has nothing to do with this: your problem should be that
there is a mismatch between your graphics file and your
previewer/printer. In Adobe Illustrator, a normal file won't print on Unix
because A.Ill uses special macros whose definition are in the
LaserWriter Prep file. If you include EPSF header-no preview, you do
get the definitions along, so it prints.

Now, I always thought that including the B&W-Mac preview only added a
resource fork containing the bitmap for previewing, which TeXtures was
able to reproduce. The text (or data fork) which gets transferred (via
ftp or whatever) to your Unix workstation should be exactly the same as
with EPSF header-no preview. Could you check this, please?
Otherwise, my faith in EPS will shade away...

Sincerely,
Jean.
--
*************************************************************************
*	Jean Orloff		*	e-mail: ORLOFF@dxcern.cern.ch	*
*	TH-Division, CERN	*	phone:	(41-22) 767-3204	*
*	CH-1211 Geneva 23	*	fax:	(41-22) 782-3914	*
*************************************************************************
From: eijkhout@cupid.cs.utk.edu (Victor Eijkhout)
Newsgroups: comp.text.tex
Subject: Re: Paper and fonts (was Re: TeX In Practice)
Date: 27 Aug 92 02:31:15 GMT
Organization: University of Tennessee, Knoxville - Department of Computer Science
Distribution: world
Reply-To: eijkhout@cupid.cs.utk.edu (Victor Eijkhout)
NNTP-Posting-Host: cupid.cs.utk.edu

In article <1992Aug26.151652.1@lucy.claremont.edu>, dhosek@lucy.claremont.edu writes:

|> > Bull, Don. Have you ever seen a page printed by Bodoni himself?

|> But how does that page look? 

That page looked better than any other page I've ever seen in
my life. It was the first time that a modern really looked brilliant
to me. (Which must also be due to the fact that this was done
with lead technology, not photo-chemically.)

|> But whatever historical arguments you make, the point cannot be
|> denied that the appearance of your book has suffered because of
|> the typeface/paper combination.

Nope. Just the inking.

(And let's now close this rather private discussion on a public forum.)

|> -dh

Victor.
Newsgroups: comp.text.tex
From: dhosek@cbrown.claremont.edu
Subject: Re: moving DVI files from ASCII to EBCDIC
Organization: Harvey Mudd College
Date: 31 Aug 92 23:46:04 PDT

In article <715264965snx@n5ial.chi.il.us>, jim@n5ial.chi.il.us (Jim Graham) writes:
> NOTE:  I am not exactly an expert on ibm mainframe things, spending
> most of my time on UN*X or dos, so I may be way off on this...but.....
 
> In article <1992Aug28.144526.27967@news.th-darmstadt.de>
> schrod@iti.informatik.th-darmstadt.de writes:
> 
>> That has nothing to do with ASCII or EBCDIC. Most DVI drivers assume
>> that IBM mainframes (I assume that they run either MVS or VM/CMS, not
>> AIX/370 ;-) store the files in fixed record files.
 
> I'm assuming that by ``record'' you mean a line of text in a plain old
> ASCII (errr, EBCDIC) text file.  well, the obvious solution is not to
> use fixed-length lines in the file (but then, ibm won't let you, will
> they?).  ok, so we're looking at a file where every last line of text
> will be precisely the same length, no shorter, no longer.  and we want
> to move a DVI file into this format....  shouldn't really be a
> problem....

Actually IBM will let you have a variable record format file no
problem. Catch is that you can't do random access reads on such a
file. This is important for dealing with DVI files.

Furthermore, without some clever hacking at the assembly level,
the program must know at *compile time* the record format of the
file that it's reading. Thus the facile solution of setting
record length to 1 (well actually, you could set it to 4 and get
correct results) will not work with most DVI translation
software--in fact, the only program I know that'll handle
Fixed-anything files is TeXrox which the original poster was
obviously not using.

As for why it's done this way, the answer is efficiency. It's
really actually done this way in DOS and Unix (among others) too,
but the operating systems hide that fact from you.

-dh

(Some days I actually _miss_ VM/CMS.)