summaryrefslogtreecommitdiff
path: root/info/digests/texhax/93/texhax.13
diff options
context:
space:
mode:
Diffstat (limited to 'info/digests/texhax/93/texhax.13')
-rw-r--r--info/digests/texhax/93/texhax.13410
1 files changed, 410 insertions, 0 deletions
diff --git a/info/digests/texhax/93/texhax.13 b/info/digests/texhax/93/texhax.13
new file mode 100644
index 0000000000..84e28db7b8
--- /dev/null
+++ b/info/digests/texhax/93/texhax.13
@@ -0,0 +1,410 @@
+TeXhax Digest Friday, 10 Sep 1993 Volume 93 : Issue 013
+
+% The TeXhax Digest is brought to you as a service of the TeX Users Group %
+% and UK TeX Users Group in cooperation with the UK TeX Archive group %
+
+Today's Topics:
+ Re: LaTeX documentation: FTP site?
+ Re: TeXhax Digest V93 #012
+ DVI to (Acrobat) PDF driver
+ Latex on PC
+ re: Why \markboth{}{} used in standard LaTeX report style?
+ latex ISO CD template wanted
+ xdvik 1.1 & PostScript font bitmaps available
+ A raw encoding file for type1 text fonts
+
+
+Administrivia:
+ Moderators: David Osborne and Peter Abbott
+ Contributions: TeXhax@tex.ac.uk
+ Administration, subscription and unsubscription requests:
+ TeXhax-request@tex.ac.uk
+
+----------------------------------------------------------------------
+
+Date: Fri, 27 Aug 1993 11:50:40 -0000
+From: Manuel Carriba <M.Carriba@dcs.sheffield.ac.uk>
+Subject: Re: LaTeX documentation: FTP site?
+
+Any TeX/LaTeX related documentation can be found in the
+CTAN archives, i.e. pip.shsu.edu, ftp.tex.ac.uk, ftp.uni-stuttgart.de.
+
+You'll find them in the directory tex-archive/documents
+Some FAQs and other helpfiles can be found in tex-archive/help
+
+Hope this helps :-D
+
+Manuel Carriba (M.Carriba@dcs.shef.ac.uk)
+
+------------------------------
+
+Date: Fri, 27 Aug 1993 12:13:21 -0400
+From: Lee Wittenberg <leew@pilot.njin.net>
+Subject: Re: TeXhax Digest V93 #012
+
+In reply to the following messages:
+
+ > Date: Thu, 08 Jul 1993 11:40:35 -0400
+ > From: Ali Taalebi <taalebi@gel.ulaval.ca>
+ > Subject: latex for PC
+ >
+ > Where can find a Latex which can be run on a PC?
+ >
+ > ------------------------------
+ >
+ > Date: Sat, 17 Jul 1993 11:53:35 -0500
+ > From: robinson@atax.eng.uab.edu (John M. Robinson)
+ > Subject: ? intro to Tex on DOS
+ >
+ > I would appreciate any suggestions on how to get started using Tex.
+ > Accordingly, I would like to acquire a Tex interpreter for my
+ > 486 at home.
+
+I would recommend the excellent emTeX implementation by Eberhard
+Mattes. It is available via anonymous ftp from ftp.uni-stuttgart.de.
+I believe it is also available from pip.shsu.edu, tex.ac.uk, and other
+sites.
+
+ -- Lee Wittenberg
+
+------------------------------
+
+Date: Fri, 27 Aug 1993 11:22:21 -0500
+From: "Ed.Garay" <Ed.Garay@UIC.EDU>
+Subject: DVI to (Acrobat) PDF driver
+
+Is anyone working on a DVI to PDF driver for DOS, Unix or OS/2?
+
+PDF is the Portable Document Format, the Adobe Acrobat file format,
+based on the PostScript imaging model, that is capable of representing
+any PostScript page.
+
+If we could get our TeX documents in PDF format, then we could use
+one of the Acrobat viewers, like Acrobat Reader or Acrobat Exchange,
+to preview our documents with all the benefits of the Acrobat technology
+(e.g. font metric emulation, zooming, panning, searching, post-it-like
+annotations, etc). With Adobe Exchange, we could print PDF documents
+on PostScript AND EVEN on non-PostScript printers.
+
+This, of course, assumes that Adobe Acrobat is going to take off,
+which I believe it will, and that the Adobe Acrobat products are going
+to be commonplace and not expensive. Today, you can get Acrobat Exchange
+for Windows and the Mac for about $120, in the U.S. Acrobat Reader sells
+for about $50. Acrobat Distiller, which converts PostScript to PDF,
+sells for $600, but this wouldn't be needed if we had a DVI2PDF driver ;-)
+Adobe says these products will run on Windows, Mac, DOS and Unix (and OS/2
+I hope), in that order. Also, last week I saw a thin (%180 page) PDF specs
+book published by Adobe, at a local bookstore.
+
+I would really like to hear your thoughts on the merits of a DVI2PDF driver.
+- --- Ed Garay
+
+------------------------------
+
+Date: Mon, 30 Aug 1993 16:29:23 +0200
+From: Khaled Odeh <Khaled.Odeh@dma.univ-compiegne.fr>
+Subject: Latex on PC
+
+Is Latex on PC exists in public domain. If yes, where can i find it.
+
+ Khaled ODEH (University of Compiegne *France*)
+ Tel : (33) 44.23.44.23 Poste. 47.33
+ E-mail : kodeh@dma.univ-compiegne.fr
+
+------------------------------
+
+Date: Wed, 01 Sep 1993 16:44:12 -0700
+From: "Ethan V. Munson" <munson@acacia.CS.Berkeley.EDU>
+Subject: re: Why \markboth{}{} used in standard LaTeX report style?
+
+In addition to Jerry Leichter's reply in the last issue of TeXhax, I
+received some e-mail responses which suggested alternative
+work-arounds for my problems with headings in the UCTHESIS style.
+
+The most useful came from Mike Piff <M.Piff@sheffield.ac.uk>, who
+recommended that I use either headerfooter.sty or fancyheadings.sty.
+I tried headerfooter.sty and had great success. For this, Mike has my
+eternal gratitude and a standing offer of his choice of libation
+should our paths ever cross.
+
+Jerry replied directly to my technical question. I was sorry to see
+that a documented feature like the \pagestyle{myheadings} should be so
+fragile. Since his answer didn't really solve my problem, he gets
+only temporary gratitude but I'll be happy buy him his choice of
+libation, too.
+
+Ethan Munson
+munson@cs.berkeley.edu
+
+------------------------------
+
+Date: Wed, 08 Sep 1993 15:03:08 +0200
+From: matsu@cso.ricoh.co.jp (Akio Matsubara)
+Subject: latex ISO CD template wanted
+
+Dear everybody,
+ I am looking for a ISO Committe Draft template for LATEX.
+ Please reply if anyone has it.
+
+Thanks
+Akio Matsubara
+Ricoh Japan
+
+------------------------------
+
+Date: Thu, 26 Aug 1993 18:01:35 -0400
+From: karl%edu.umb.cs@uk.ac.nsfnet-relay
+Subject: xdvik 1.1 & PostScript font bitmaps available
+
+I've released new versions of:
+* kpathsea -- my path searching library,
+* xdvik -- my modified xdvi that uses it, and
+* psfonts -- Ghostscript-generated bitmaps for the standard PostScript fonts.
+
+ ftp.cs.umb.edu:pub/tex/{xdvik,psfonts}.tar.gz
+
+Please notice the `.gz' instead of `.z' or `.Z' -- the default gzip
+extension was changed in response to a poll on the GNU newsgroups.
+
+I've stopped making the library available separately, since that was
+causing maintenance hassles. The library is part of the xdvik distribution.
+
+I've established a mailing list, tex-k@cs.umb.edu, for bug reports and
+discussions for the TeX-related stuff I maintain. I hope this will
+provide for sharing of interim fixes, quicker help when I cannot respond
+immediately, and so on. To join, email tex-k-request@cs.umb.edu with a
+message whose body contains a line
+subscribe your-preferred-email-address
+
+I expect to release a new version of dvipsk shortly, perhaps within a week
+or two. web2c will follow as soon as possible.
+
+Here's the NEWS:
+
+kpathsea:
+* Routines to look up TeX font files, default path specifications, etc.
+* Sort-of pattern matching: /foo//bar matches subdirectories
+ /foo/a/bar, /foo/b/bar, /foo/a1/a2/bar, etc.
+* $var and ${var} expansion.
+* Support for MakeTeX... scripts.
+* Support for fallback resolutions and font.
+* Lazy evaluation of path elements.
+* Some runtime debugging support.
+
+xdvik:
+* Rewrite font finding routines to use the new kpathsea facilities.
+* Update for xdvi patchlevel 17.
+
+psfonts:
+* In Adobe StandardEncoding, and named with leading `r', for the new xdvik.
+* TFM widths in the PK files match those in the TFM files.
+* Umlaut character has been corrected (in the GS fonts).
+* Encoding of psyr* (the symbol font) matches Adobe's.
+
+karl@cs.umb.edu
+Help fight the new programming monopolies -- write lpf@uunet.uu.net.
+
+------------------------------
+
+Date: Wed, 01 Sep 1993 14:48:17 -0700
+From: mackay@edu.washington.cs (Pierre MacKay)
+Subject: A raw encoding file for type1 text fonts
+
+Over the course of a rich discussion of virtual fonts, I have
+finally come to understand and appreciate the full usefulness
+of Tom Rokicki's careful distinction between input encoding
+and output encoding in afm2tfm. In a virtual font environment
+it answers several questions that have recently been raised about
+the proper encoding of a {\em raw} tfm file. The raw tfm
+should contain references to every simple (non-composite)
+character in the actual list of glyphs, and it need not contain
+anything else. Dozens of possible output encodings are
+possible, among which DC will of course be a major player,
+but all those reencodings will be easier and more portable
+if there is only one {\em raw} encoding. The raw encoding should
+provide for {\em every} simple character in the font, including
+all the unmapped characters. Fortunately, the list of
+unmapped characters is almost as consistent as Adobe Standard
+Encoding at least in text fonts. I propose therefore
+the following ASEX.enc (Adobe Standard Coding Extended)
+to be used with the -p flag in afm2tfm. What is used for
+the -t flag is wide open, but it can certainly include DC.enc
+
+There remains the question of what to do about the various
+Superfont layouts: Courier in its most prolific version has
+352 simple characters and the Monotype TimesNewRomanSF Superfont
+has 337 simple characters. In the case of TimesNewRoman, the
+excess is the result of combining the regular with the expert
+font, and all that is needed is to code the expert part back
+out into an expert raw TFM file. Then there are only 12 U&lc pairs
+of additional simple characters. A similar approach can be taken
+with Courier; many of the symbol characters, together with the
+borders and dingbats do not belong in a tex encoding anyway.
+
+% -------------------------------------------------------------------------
+%
+% This is ASEX encoding. (file ASEX.enc)
+%
+% Adobe Standard Encoding Extended.
+%
+% Creator: Pierre A. MacKay mackay@cs.washington.edu
+% Creation Date: Thu Aug 31 08:56:22 PDT 1993
+%
+% This is an input coding file for use with Radical Eye Software's
+% afm2tfm. Use with the -p flag. This file should also be
+% used with ps2pk to create a complete set of bitmapped
+% characters.
+%
+% The sole purpose of this file is to ensure that all non-composite
+% characters in the font are made available in the raw TFM. Therefore
+% there are no ligatures or any other refinements. The raw TFM
+% file contains no ligatures or kernings---nothing but character
+% metrics. We retain Adobe Standard encoding for all mapped
+% characters on the AFM file, and extend the list by adding
+% the unmapped simple characters into the empty code positions
+% from O 200 to O 240. It is assumed that the output coding used
+% for the TeX tfm will be different from this ( -t flag in afm2tfm ).
+%
+% The extended part of this encoding is consistent with the general
+% run of text fonts from Adobe, BitStream, DTC, Linotype, Monotype,
+% URW and probably others as well. For SuperFont characters, see below.
+%
+% Jan Michael Rynnings has pointed out that a few very carefully designed
+% fonts, e. g. Adobe Garamond and Adobe Caslon, treat all the accented
+% characters as simple glyphs (must make for a huge pfa file), and that
+% this input encoding would not recognize such refinements. True---but
+% such fonts will be a tiny minority, and can be dealt with by
+% special encoding files.
+%
+% Usage:
+% afm2tfm <FontName>.afm -p ASEX.enc -t <XXX>.enc -v <vplname> <rawname>
+%
+/ASEXEncoding [ % now 256 chars follow
+%
+% The following will replace the characters from 0 to 32 in the raw encoding
+% if you have access to a SuperFont. There is reason to hope that this
+% set will be as stable as the unmapped set in current text fonts
+% If you don't have a SuperFont, and have to create any of these as a
+% composite, precede the name with a dot, as is done here for
+% Scedilla and scedilla. The change in name keeps afm2tfm from thinking
+% that the character already exists when it comes to evaluate the output
+% (-t flag) encoding.
+%
+% 0x00
+ /Aogonek /Eogonek /Iogonek /Kafii9170 /Lafii9170 /Lcaron /Nafii9170 /Rafii9170
+ /Safii9170 /.Scedilla /Tafii9170 /Uogonek /.notdef /.notdef /.notdef /.notdef
+
+% 0x10
+ /aogonek /eogonek /iogonek /kafii9170 /lafii9170 /lcaron /nafii9170 /rafii9170
+ /safii9170 /.scedilla /tafii9170 /uogonek /.notdef /.notdef /.notdef /.notdef
+
+% 0x20 % Keep the space, for use as \boundarychar (Give it zero width in vpl)
+ /space /exclam /quotedb /numbersign
+ /dollar /percent /ampersand /quoteright
+ /parenleft /parenright /asterisk /plus /comma /hyphen /period /slash
+% 0x30
+ /zero /one /two /three /four /five /six /seven
+ /eight /nine /colon /semicolon /less /equal /greater /question
+% 0x40
+ /at /A /B /C /D /E /F /G /H /I /J /K /L /M /N /O
+% 0x50
+ /P /Q /R /S /T /U /V /W
+ /X /Y /Z /bracketleft /backslash /bracketright /asciicircum /underscore
+% 0x60
+ /quoteleft /a /b /c /d /e /f /g /h /i /j /k /l /m /n /o
+% 0x70
+ /p /q /r /s /t /u /v /w
+ /x /y /z /braceleft /bar /braceright /asciitilde /.notdef
+%
+% This is the Extension to Adobe Standard Encoding
+%
+% In as many of the next 32 positions as necessary, include
+% all the unmapped simple (non-composite) characters. The
+% inclusion of Ccedilla and ccedilla is problematic. These are
+% composites in some schemes, simple in others. Best to
+% include them here. Characters are entered in alphabetical order
+% by name. If you need to create your own composite for Ccedilla
+% ccedilla or Eth, precede the name with a dot as indicated above.
+%
+% 0x80
+ /Ccedilla /Eth /Thorn /brokenbar /ccedilla /copyright /degree /divide
+ /eth /logicalnot /minus /mu /multiply /onehalf /onequarter /onesuperior
+% 0x90
+ /plusminus /registered /thorn /threequarters
+ /threesuperior /trademark /twosuperior /.notdef
+ /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
+%
+% From here on the order is again Adobe Standard Encoding
+%
+% 0xA0
+ /.notdef /exclamdown /cent /sterling /fraction /yen /florin /section
+ /currency /quotesingle /quotedblleft /guillemotleft
+ /guilsinglleft /guilsinglright /fi /fl
+% 0xB0
+ /.notdef /endash /dagger /daggerdbl /periodcentered /.notdef /paragraph /bullet
+ /quotesinglbase /quotedblbase /quotedblright /guillemotright
+ /ellipsis /perthousand /.notdef /questiondown
+% 0xC0
+ /.notdef /grave /acute /circumflex /tilde /macron /breve /dotaccent
+ /dieresis /.notdef /ring /cedilla /.notdef /hungarumlaut /ogonek /caron
+% 0xD0
+ /emdash /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
+ /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
+% 0xE0
+ /.notdef /AE /.notdef /ordfeminine /.notdef /.notdef /.notdef /.notdef
+ /Lslash /Oslash /OE /ordmasculine /.notdef /.notdef /.notdef /.notdef
+% 0xF0
+ /.notdef /ae /.notdef /.notdef /.notdef /dotlessi /.notdef /.notdef
+ /lslash /oslash /oe /germandbls /.notdef /.notdef /.notdef /.notdef
+] def
+
+% --------------------END of ASEX.enc-------------------------------------
+
+Email concerned with UnixTeX distribution software should be sent primarily
+to: elisabet@u.washington.edu Elizabeth Tachikawa
+otherwise to: mackay@cs.washington.edu Pierre A. MacKay
+Smail: Northwest Computing Support Center Resident Druid for
+ Thomson Hall, Mail Stop DR-10 Unix-flavored TeX
+ University of Washington
+ Seattle, WA 98195
+ (206) 543-6259
+
+
+------------------------------
+
+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.
+
+Please send contributions to: TeXhax@tex.ac.uk
+
+Administration, subscription and unsubscription requests:
+ On Internet:
+ send a one line mail message to TeXhax-request@tex.ac.uk
+ SUBSCRIBE TEX-L <your real name>
+ UNSUBSCRIBE TEX-L
+ On BITNET:
+ send a similar one-line mail message to LISTSERV@xxx
+ On JANET:
+ send a similar one line mail message to TeXhax-request@uk.ac.tex
+
+For information on the TeX Users Group, please send a message to
+TUG@math.ams.com, or write TeX Users Group, P.O. Box 869, Santa
+Barbara, CA 93102, USA.
+
+Back issues of the digest are available for anonymous ftp from
+the UK TeX Archive, tex.ac.uk (134.151.40.18)
+ in [tex-archive.digests.texhax.YY]texhax.NN
+and ftp.tex.ac.uk (134.151.44.19)
+ in /pub/archive/digests/texhax/YY/texhax.NN
+where YY = last two digits of year, NN = issue number
+
+ftp.tex.ac.uk is also mirrored to pip.shsu.edu (192.92.115.10) and
+ftp.uni-stuttgart.de (129.69.1.12) as part of the Comprehensive TeX
+Archive Network, and may give better response for subscribers in the
+USA and Europe, respectively.
+
+\bye
+
+End of TeXhax Digest [Volume 93 Issue 13]
+*****************************************