diff options
Diffstat (limited to 'info/digests/texhax/93/texhax.16')
-rw-r--r-- | info/digests/texhax/93/texhax.16 | 879 |
1 files changed, 879 insertions, 0 deletions
diff --git a/info/digests/texhax/93/texhax.16 b/info/digests/texhax/93/texhax.16 new file mode 100644 index 0000000000..b319bddc74 --- /dev/null +++ b/info/digests/texhax/93/texhax.16 @@ -0,0 +1,879 @@ +TeXhax Digest Friday, 10 Dec 1993 Volume 93 : Issue 016 + +% 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: How do you single-space captions in a double-spaced document? + Re: Metafont settings in DECUS distribution? + Abbreviation marks for feet and inches + Making large circles in LaTeX or PicTeX + Re: Inserting graphics in LaTeX documents + DVIJEP -j option for VAX/VMS systems + Searching for items in UK CTAN + Re: Searching for items in UK CTAN + TeX + Solaris 2.X TeX etc. + TeX converters to Braille? + Invisible printing! + Report on the inaugural meeting of the NTS group, September 1993 + modes.mf 1.1 available + [comp.text.tex] announcing the French Style Files distribution V3,25 + [comp.text.tex] German dictionary available for ftp + announcement Donald E. Knuth Scholarship + + +Administrivia: + Moderators: David Osborne and Peter Abbott + Contributions: TeXhax@tex.ac.uk + Administration, subscription and unsubscription requests: + TeXhax-request@tex.ac.uk + +---------------------------------------------------------------------- + +Date: Thu, 04 Nov 1993 13:05:35 -0800 +From: "Ethan V. Munson" <munson@acacia.CS.Berkeley.EDU> +Subject: Re: How do you single-space captions in a double-spaced document? + +Mike Piff came to my rescue for the second time with the following +observation: + +> I suspect that the answer is a simple one. +> +> Try {\ssp#1: #2\par} instead. (Set paragraph before forgetting single +> spacing.) + +The original line of code was: + + {\ssp#1: #2}\par + +Mike's suggestion solved the problem. + +Ethan Munson +munson@cs.berkeley.edu + +------------------------------ + +Date: Thu, 04 Nov 1993 17:39:41 -0500 +From: Bill Denning <DENNING@DECUS.Org> +Subject: Re: Metafont settings in DECUS distribution? + +David Rhead writes: + +>>A colleague got TeX-and-friends for VAX/VMS via DECUS. + +>>The DECUS suite includes .pk files. I guess that these were generated with +>>some Metafont settings intended for DEC's LN03. + +>>Does anyone know what Metafont settings were actually used to generate the +>>.pk files in the DECUS distribution? + +Try contacting the DECUS TeX Collection editor, Ted Nieland. If Ted can't help + +himself, he can probably refer you to the folks who did the port. + +ted@nieland.dayton.oh.us +nieland@decus.org + +------------------------------ + +Date: Thu, 04 Nov 1993 18:01:01 -0500 +From: Bill Denning <DENNING@DECUS.Org> +Subject: Abbreviation marks for feet and inches + +From time to time I need to write LaTeX documents that include measurements in +feet and inches. What I'm looking for is a method of using the ' and " marks +to abbreviate feet and inches. + +I've tried several simple macros, but with limited success. + +\newcommand{\inch}{{\tt "}} + +This does exactly what I want for inches, but I can't seem to get a similar +vertical mark for feet -- what I really would like is half of the " mark in the + +\tt font. {\tt '} and {\tt `} give "curled" marks, and \verb doesn't seem to +help either. + +As an alternative, I've also tried: + +\newcommand{\feet}{$^{^{\small\prime}}$} + +\newcommand{\inch}{\feet\feet} + +At least the marks are consistent with each other, but I'm not really satisfied +with the results. (Most of the time I use \large for the type size of my text. +) + +Can anyone make any other suggestions? + +Thanks for your help, Bill + +------------------------------ + +Date: Thu, 04 Nov 1993 18:50:58 -0500 +From: Bill Denning <DENNING@DECUS.Org> +Subject: Making large circles in LaTeX or PicTeX + +Does anyone have any experience in creating large circles in either PicTeX or +the LaTeX picture environment? As documented in Leslie Lamport's book, the +largest circle that can normally be made is approxmately 1/2 inch in diameter. + +On my system I can generate a circle of about 14 mm in diameter, but that's the + +upper limit. Any suggestions would be appreciated. + +Thanks, Bill + +------------------------------ + +Date: Thu, 04 Nov 1993 23:38:49 +0000 +From: Manuel Carriba <M.Carriba@dcs.sheffield.ac.uk> +Subject: Re: Inserting graphics in LaTeX documents + +Heitor S. Lopes (heitor@gpeb.ufsc.br) writes: + +> Does anybody have some hint on how to insert in Latex documents, +> graphic files in any well-known graphic format (e.g. .PCX, .GIF, etc...), +> or from spreadsheet charts? I'm using PcTeX, running under DOS, and I noticed +> that \special{... doesn't work at all. + +Switch to emTeX :-) It supports your desired graphic formats. + +Your nearest site is pip.shsu.edu:tex-archive/systems/msdos/emtex + +Manuel Carriba (M.Carriba@dcs.shef.ac.uk) + +------------------------------ + +Date: Thu, 04 Nov 1993 18:21:49 -0500 +From: Bill Denning <DENNING@DECUS.Org> +Subject: DVIJEP -j option for VAX/VMS systems + +I'm doing some work in LaTeX using the picture environment, and I want to do it +in landscape mode. PORTLAND.STY does the trick, and XDVI handles the output +nicely for screen display. However, when I convert it to print on my HP +LaserJet IIP using DVIJEP, all text wider than 7.50in gets truncated. + +I'm using the February, 1991 distribution of the DECUS TeX Collection for +VAX/VMS systems. I looked around in [TEX_SOURCE.DVI], and found that Nelson +Beebe mentions an update for DVIJEP in his message dated 26-May-1988, which is +contained in the file 00MAIL.16. + +There is also a file called DVIJEP.LANDSCAPEMODS, which is a mail message from +Julian Perry containing the source code modifications needed to implement the +- -j option for DVIJEP. The -j option is used to convert .DVI files that are +generated in landscape mode. + +Does anyone have an updated version of DVIJEP on a VAX/VMS system that allows +the use of the -j option? I need either object or executable code, as I don't +have a C compiler. An .EXE would need to be linked under VMS 5.4-2 or earlier. + +I do not have access to ftp. I believe that the VMSmail command SEND/FOREIGN +would work if the sender is using a MIME compliant mailer. + +Several sources in DECUS have been unable to help with this request. + +Thanks in advance, Bill + +------------------------------ + +Date: Thu, 04 Nov 1993 23:54:59 +0000 +From: Manuel Carriba <M.A.Carriba@sheffield.ac.uk> +Subject: Searching for items in UK CTAN + +Dear all, + +I guess the UK node of the CTAN provides the facility to search for +the location of some specific files, directories or both if you don't +know exactly wehre they're placed in directory tree. + +Can someone tell me the commands or give a short explanation how +I can do this? It should work similar to archie's query. + +Cheers, + +Manuel Carriba (M.Carriba@dcs.shef.ac.uk) + + +------------------------------ + +Date: Fri, 05 Nov 1993 10:53:13 +0000 +From: Sebastian Rahtz <spqr@ftp.tex.ac.uk> +Subject: Re: Searching for items in UK CTAN + + > I guess the UK node of the CTAN provides the facility to search for + > the location of some specific files, directories or both if you don't + > know exactly wehre they're placed in directory tree. + > + > Can someone tell me the commands or give a short explanation how + +if you use ftp, the command + quote site index foo +searches the file list for the word "foo". is that what you mean + + > I can do this? It should work similar to archie's query. +"should" is a strong word. + +sebastian + +------------------------------ + +Date: Wed, 10 Nov 1993 13:36:00 -0500 +From: wwetmore@amweld.org (William Wetmore, amweld sysop) +Subject: TeX + +I need to find out where to get TeX, which platforms it is +available for, etc... Now that we are on the Internet it seems +that our technical writers would like to use this system. +Thanks in advance for any info you can share with me. + +- ---- William Wetmore + American Welding Society, Miami, Florida + amweld.org + +------------------------------ + +Date: Wed, 10 Nov 1993 17:25:01 -0500 +From: Steven "M." Christensen <stevec@yoda.physics.unc.edu> +Subject: Solaris 2.X TeX etc. + + +Do you know if TeX and its related programs have been ported +to Sun Solaris 2.2 or better? + +Steve Christensen + +------------------------------ + +Date: Fri, 03 Dec 1993 10:34:42 +0000 +From: James Renshaw <jhr@mathematics.southampton.ac.uk> +Subject: TeX converters to Braille? + +We have a blind student in our department who currently converts all his +notes into Braille (including a lot of the mathematics). A number of my +collegues use TeX/LaTeX and we would like to save him some time and effort +by converting out lecture notes/tutorial sheets from TeX to Braille. I +have come a cross a LaTeX file called braille.sty together with the +relevant fonts which can output Braille as a sequence of dots but (1) it +can't cope with mathematics and (2) we need some hardware to convert the +dots to actual Braille. + +Does anybody have any suggestions as to how we might achieve this? + +Dr JH Renshaw | Tel : (0703) 593673 +Faculty of Mathematical Studies | Fax : (0703) 593939 +University of Southampton | E-mail : jhr@soton.ac.uk +Southampton SO9 5NH, ENGLAND | or : jhr@maths.soton.ac.uk + +------------------------------ + +Date: Thu, 09 Dec 1993 14:14:00 +0000 +From: AMG0199@vax2.queens-belfast.ac.uk +Subject: Invisible printing! + +I would like to set up an environment in LaTeX say + +\begin{invisible} ..... \end{invisible} + +such that all material contained within it is processed in the normal way +in terms of spacing and paging but at the print out stage blank characters +(invisible ink) are used. Presumably this will involve providing dummy +pixel files. Any advice will be welcome. + +(This may seem like a strange specification -- it has to do with lecture +notes being prepared with parts blanked out, later to be filled in by +students!) + +Tom Patterson +Department of Applied Mathematics & Theoretical Physics +Queen's University of Belfast +uk.ac.qub.v2 + +------------------------------ + +Date: Fri, 12 Nov 1993 12:34:06 +0000 +From: P.Taylor@rhbnc.ac.uk +Subject: Report on the inaugural meeting of the NTS group, September 1993 + + +Report on the Inaugural Meeting of the NTS Core Group: September, 1993. +========================================================================= + +This is a report on the inaugural meeting of the NTS (`New Typesetting System') +project group, held during the autumn DANTE meeting at Kaiserslautern (Germany) + +on 23rd and 25th September, 1993. + +Present: Joachim Lammarsch (DANTE President, and instigator of the NTS project) +; + Philip Taylor (Technical co-ordinator, NTS project); + Marion Neubauer (minutes secretary); + Prof. Dr. Peter Breitenlohner, + Mariusz Olko, + Bernd Raichle, + Joachim Schrod, + Friedhelm Sowa. + +Background: Although the NTS project has been in existence for approximately +eighteen months, there has not previously been a face-to-face meeting of +members of the core group; at the Spring meeting of DANTE Rainer Sch\"opf +announced his resignation as technical co-ordinator, and Philip Taylor was +invited by Rainer and Joachim to take over as co-ordinator, which he agreed to +do. + +Joachim Lammarsch opened the Autumn meeting by reviewing the history of the +project and the rationale which lay behind its creation; each member of the +group then briefly reviewed his or her particular area of interest in the +project, after which the group received an extended presentation from Joachim +Schrod on one possible approach to the realisation of NTS. The members of the +group were broadly in support of the approach outlined by Joachim Schrod, and +it was \stress {agreed} that this should form the basis for discussions at the +meeting. + +The approach proposed by Joachim may be summarised as follows: {\TeX} in its +present form is not amenable to modification; the code, although highly +structured in some ways, is also painfully monolithic in others, and any +attempt to modify the present code in anything other than trivial ways is +almost certainly doomed to failure. Accordingly, before attempting to modify +{\TeX} in any way it is first necessary to re-implement it, the idea +behind such re-implementation being to eliminate the interdependencies of +the present version and to replace these with a truly modular structure, +allowing various elements of the typesetting process to be easily modified or +replaced. This re-implementation should be undertaken in a language suitable +for rapid prototyping, such as the Common Lisp Object System (`CLOS'). The +primary reason for the re-implementation is to provide modularisation with +specified internal interfaces and therby provide a test bed, firstly to ensure +that {\TeX} has been properly re-implemented and subsequently to allow the +investigation of new typesetting paradigms. + +Once a working test bed has been created, and compatibility with existing +{\TeX} demonstrated, a second re-implementation will be undertaken; this +re-implementation will have the same modular structure as the test bed but will +be implemented with efficiency rather than extensibility in mind, and will be +undertaken using a combination of literate programming and a widespread +language with a more traditional approach, such as `C++'. When this second +version has also been demonstrated to be compatible with {\TeX}, it will be +made available to implementors around the world, the idea being to encourage +people to migrate to NTS by demonstrating its complete compatibility with +{\TeX} (the test bed will also be made available if there is interest shewn +in its use). Thereafter new ideas and proposals will be investigated using the +test bed, and if found to be successful these will be re-implemented in the +distribution version. + +The main problem which the group identified with the approach outlined by +Joachim was simply one of resources: in order to accomplish two +re-implementations within a reasonable time-scale, it would be essential to use +paid labour, it being estimated that each re-implementation requires a +minimum of four man-months work to produce a prototype, and eight man-months to +reach the production stage. As this is far beyond the ability of members of the +group to contribute in the short term, it is clearly necessary to employ a +small team (of between two and four members) to carry out the re-implementations +under the guidance and supervision of one or more members of the core group. +Initial costings suggested that this could not be accomplished within the +present financial resources of the group, and accordingly it was \stress +{agreed} that Joachim Lammarsch should seek further financial support. +Subsequent investigations shewed that a quite significant reduction in costs +could be achieved if the programming team were sited in a central or eastern +European country, particularly if the members of the team were also residents +of the country; this approach is being investigated. + +As it was obvious that no immediate progress could be made with Joachim +Schrod's proposal, even though the group agreed that it represented an +excellent philosophical approach, it was also \stress {agreed} that the group +needed to identify some fallback approaches, which could (a)~be commenced +immediately, and (b)~would be of significant benefit to the {\TeX} community at +large. The group identified two such projects, these being (1)~the +specification of a canonical {\TeX} kit, and (2)~the implementation of an +extended {\TeX} (to be known as e-{\TeX}) based on the present WEB +implementation. It was also \stress {agreed} that Marek Ry\'cko \& Bogus{\l}aw +Jackowski would be asked if they were willing to co-ordinate the first of these +activities, and that Peter Breitenlohner would co-ordinate the second. + +The ideas behind the two proposals are as follows. + +(1)~The canonical {\TeX} kit: at the moment, the most that can be assumed of + any site offering {\TeX} is (a)~ini{\TeX}; (b)~plain {\TeX}; (c)~{\LaTeX}; + and (d)~at least sixteen Computer Modern fonts. Whilst these are adequate + for a restricted range of purposes, it is highly desirable when transferring + documents from another site to be able to assume the existence of a far + wider range of utilities. For example, it may be necessary to rely on + BibTeX, or on MakeIndex; it may be useful to be able to assume the existence + of BM2FONT; and so on. Rather than simply say ``all of these can be found + on the nearest CTAN archive'', it would be better if all implementations + contained a standard subset of the available tools. It is therefore the aim + of this project to identify what the elements of this subset should be, and + + then to liaise with developers and implementors to ensure that this subset + is available for, and distributed with, each {\TeX} implementation. + +(2)~Extended {\TeX} (e-{\TeX}): whilst the test bed and production system + approach is philosophically very sound, the reality at the moment is + that the group lacks the resources to bring it to fruition. None the + less, there are many areas in which a large group of existing {\TeX} + users believe that improvements could be made within the philosophical + constraints of the existing {\TeX} implementation. E-{\TeX} is an + attempt to satisfy their needs which could be accomplished without a + major investment of resources, and which can pursued without the need + for additional paid labour. + +Finally the group agreed to individually undertake particular responsibilities; +these are to be: + +Peter Breitenlohner: Remove any existing incompatibilities between +{\TeX}--{\XeT} and {\TeX}, with the idea of basing further e-{\TeX} +developments on {\TeX}--{\XeT}; liaise with Chris Thompson concerning +portability of the code; produce a catalogue of proposed extensions to +e-{\TeX}. + +Joachim Lammarsch: liaise with vendors and publishers in an attempt to raise +money for the implementation of NTS proper; arrange a further meeting of +interested parties; liaise with Eberhard Mattes concerning the present +constraints on the unbundling of em{\TeX}; negotiate with leading academics +concerning possible academic involvement in the project. + +Mariusz Olko: take responsibility for the multi-lingual aspects of e-{\TeX} and +NTS; discuss the possibility of siting the NTS programming team in Poland; +discuss the possibility of academic involvement with leading Polish academics. + +Bernd Raichle: endeavour to get {\TeX}--{\XeT} integrated into the standard +UNIX distribution; prepare a list of proposed extensions to e-{\TeX}; lead +discussions on NTS-L. + +Friedhelm Sowa: primary responsibility for finance; prepare proposals for a +unified user interface and for unification of the integration of graphics; +liaise with the Czech/Slovak groups concerning possible siting of the NTS +programming team in the Czech Republic or Slovakia; discuss possible academic +involvement with leading academics. + +Philip Taylor: Overall technical responsibility for all aspects of the project; +liaise with other potential NTS core group members; prepare and circulate a +summary of the decisions of this and future meetings. + + + Philip Taylor, + 09-NOV-1993 14:02:03 + +------------------------------ + +Date: Wed, 24 Nov 1993 11:08:52 -0500 +From: kb@cs.umb.edu +Subject: modes.mf 1.1 available + +I have released version 1.1 of modes.mf. You can get it by anonymous ftp from + + ftp.cs.umb.edu:pub/tex/modes.mf + +You can also get it by email from George Greenwade's (thanks, George!) +file server if you cannot ftp: email fileserv@shsu.edu with a body of +`sendme modes'. + +This file is a collection of Metafont mode_def's. It also makes common +definitions for write/white printers, `special' information, and +landscape mode. + +The mode for the HP LaserJet 4 has completely new values, from +mbr@research.nj.nec.com; his seemed better tested than previous. + +The IBM 4019 is now a separate mode from the IBM 4216. + +This version again runs through TeX. + +As always, thanks to the contributors. + +If you have mode_def's which are not listed below, or corrections to the +existing ones, please send them to me. Improvements to the exposition, +particularly in how to create a new mode_def, are also welcome. + +karl@cs.umb.edu + +mode_def AgfaFourZeroZero = % AGFA 400PS +mode_def amiga = % Commodore Amiga +mode_def AtariNineFive = % Atari 95dpi previewer +mode_def AtariNineSix = % Atari 96x96 previewer +mode_def AtariSLMEightZeroFour = % Atari ST SLM 804 printer +mode_def AtariSMOneTwoFour = % Atari ST SM 124 screen +mode_def aps = % Autologic APS-Micro5 +mode_def ApsSixHi = % Autologic APS-Micro6 +mode_def bitgraph = % BBN Bitgraph at 118dpi +mode_def boise = % HP 2680A +mode_def CanonCX = % Canon CX, SX, LBP-LX +mode_def CanonEX = % CanonEX in LaserWriter Pro 630 +mode_def CanonLBPTen = % e.g., Symbolics LGP-10 +mode_def ChelgraphIBX = % Chelgraph IBX +mode_def CItohThreeOneZero = % CItoh 310 +mode_def CItohEightFiveOneZero = % CItoh 8510A +mode_def CompugraphicEightSixZeroZero = % Compugraphic 8600 +mode_def CompugraphicNineSixZeroZero = % Compugraphic 9600 +mode_def crs = % Alphatype CRS +mode_def DataDisc = % DataDisc +mode_def DataDiscNew = % DataDisc with special aspect ratio +mode_def DECsmall = % DEC 17-inch, 1024 x 768 +mode_def DEClarge = % DEC 19-inch, 1280 x 1024 +mode_def dover = % Xerox Dover +mode_def epsdraft = % Epson at 120x72dpi +mode_def epsfast = % Epson at 60x72dpi +mode_def epsonlo = % Epson at 120x216dpi +mode_def EpsonLQFiveZeroZeroMed = % Epson LQ-500, 360x180dpi +mode_def EpsonLQFiveZeroZeroLo = % Epson LQ-500, 180x180dpi +mode_def EpsonMXFX = % 9-pin Epson MX/FX family +mode_def GThreefax = % 200 x 100dpi G3fax +mode_def HPDeskJet = % HP DeskJet 500 +mode_def HPLaserJetIIISi = % HP Laser Jet IIISi +mode_def HPrugged = % HP RuggedWriter 480 +mode_def ibm_a = % IBM 38xx (\#1) +mode_def IBMD = % IBM 38xx (\#2) +mode_def IBMFourZeroTwoNine = % IBM 4029-30, 4250 +mode_def IBMFourTwoOneSix = % IBM 4216 +mode_def IBMFourZeroOneNine = % IBM 4019 +mode_def IBMProPrinter = % IBM ProPrinter +mode_def IBMSixOneFiveFour = % IBM 6154 display +mode_def IBMSixSixSevenZero = % IBM 6670 (Sherpa) +mode_def IBMThreeOneSevenNine = % IBM 3179 screen +mode_def IBMThreeOneNineThree = % IBM 3193 screen +mode_def IBMThreeEightOneTwo = % IBM 3812 +mode_def IBMThreeEightTwoZero = % IBM 3820 +mode_def IBMEGA = % IBM EGA monitor +mode_def IBMVGA = % IBM VGA monitor +mode_def imagewriter = % Apple ImageWriter +mode_def laserjetfour = % 600dpi HP LaserJet 4 +mode_def laserjetlo = % HP LaserJet at 150dpi +mode_def lasermaster = % 1000dpi LaserMaster +mode_def LASevenFive = % DEC LA75 +mode_def LinotypeOneZeroZeroLo = % Linotype Linotronic [13]00 at 635dpi +mode_def LinotypeOneZeroZero = % Linotype Linotronic [13]00 at 1270dpi +mode_def LinotypeThreeZeroZeroHi = % Linotype Linotronic 300 at 2540dpi +mode_def LNZeroOne = % DEC LN01 +mode_def LPSTwoZero = % DEC lps20 +mode_def LPSFourZero = % DEC LPS40 +mode_def lview = % Sigma L-View monitor +mode_def MacMagnified = % Mac screens at magstep 1 +mode_def MacTrueSize = % Mac screens at 72dpi +mode_def NCD = % NCD 19-inch +mode_def NEC = % NEC +mode_def NEChi = % NEC-P6 at 360x360dpi +mode_def Newgen = % Newgen 400dpi +mode_def NeXTprinter = % NeXT 400dpi +mode_def NeXTscreen = % 100dpi NeXT monitor +mode_def nullmode = % TFM files only +mode_def OCESixSevenFiveZeroPS = % OCE 6750-PS +mode_def okidata = % Okidata +mode_def OneTwoZero = % e.g., high-resolution Suns +mode_def phaser = % Tektronix Phaser PXi +mode_def PrintwareSevenTwoZeroIQ = % Printware 720IQ +mode_def qms = % QMS (Xerox engine) +mode_def QMSOneSevenTwoFive = % QMS 1725 +mode_def QMSOneSevenZeroZero = % QMS 1700 +mode_def RicohFourZeroEightZero = % e.g., TI Omnilaser +mode_def RicohLP = % e.g., DEC LN03 +mode_def SparcPrinter = % Sun SPARCprinter +mode_def StarNLOneZero = % Star NL-10 +mode_def sun = % Sun and BBN Bitgraph at 85dpi +mode_def supre = % Ultre*setter at 2400dpi +mode_def toshiba = % Toshiba 13XX, EpsonLQ +mode_def ultre = % Ultre*setter at 1200dpi +mode_def VarityperFiveZeroSixZeroW = % Varitype 5060W +mode_def VarityperFourThreeZeroZeroLo = % Varityper 4300P at 1200dpi +mode_def VarityperFourThreeZeroZeroHi = % Varityper 4300P at 2400dpi +mode_def VarityperFourTwoZeroZero = % Varityper 4200 B-P +mode_def VarityperSixZeroZero = % Varityper Laser 600 +mode_def VAXstation = % VAXstation monitor +mode_def XeroxDocutech = % Xerox 8790 or 4045 +mode_def XeroxEightSevenNineZero = % Xerox 8790 or 4045 +mode_def XeroxFourZeroFiveZero = % Xerox 4050/4075/4090 +mode_def XeroxNineSevenZeroZero = % Xerox 9700 +mode_def XeroxThreeSevenZeroZero = % Xerox 3700 + + +------------------------------ + +Date: 26 Nov 1993 16:31:59 +0100 +From: gaulle@frors65.circe.fr (Bernard Gaulle) +Subject: [comp.text.tex] announcing the French Style Files distribution V3,25 + + I'm pleased to announce the availability of the so called +"French Style Files" distribution V3,25 on the French archives server of +GUTenberg at ftp.univ-rennes1.fr in directory pub/GUTenberg/french + + I recall that this package is intended for people willing to deal with +French documents or multi-lingual documents with TeX, LaTeX, etc... + + Below is the file giving the major changes since the last distributed +version V3,20 in may, 1993. + +Enjoy, + + --bg + + +% fichier Changements de la distribution << style french >> +=============================================================================== +Voici les principaux changements intervenus dans la distribution du +style french V3,25 du 25 novembre 1993 par rapport a la V3.20 du 11 mai 1993 : + +A NOTER que presque tous les fichiers ont ete modifies. + + Il s'agit d'une version consolidee permettant l'utilisation du +dispositif NFSS2 (New Font Selection Scheme version 2) qui sera introduit +a peu pres sous sa forme actuelle dans LaTeX2e. La prochaine distribution +des fichiers de francisation devrait etre relative a cette nouvelle version +de LaTeX. + +Ameliorations apportees : + - au niveau de la francisation : + - un mot suivi d'une \footnote peut desormais etre + divise en fin de ligne ; + - lettrines produites de facon plus rigoureuse ; + possibilite d'imposer le nombre de lignes ; + - mise en page du style letter ; + - ajout de \prefacename comme dans la distribution de Babel ; + - traitement des guillemets modifie (pour laisser la + possibilite a l'utilisateur de redefinir des macros + ayant des noms composes des caracteres < ou >) ; + - \begin{french} et \end{french} sont autorises avec LaTeX ; + - prise en compte de NFSS2 et de son << Encoding Scheme >> ; + - utilisation possible avec le moteur TeX--XeT ; + - la << contribution >> allemande a ete remise a jour par son + auteur, Marc Torzynski. + +Nouveaux outils proposes : + + - possibilite de preciser son clavier personnel (keyboard.dat) + en le chargeant par \documentstyle[keyboard,...]{...} + (ce dispositif est en beta-test) ; + particulierement utile dans le cas d'installation multi-utilisateurs + ou lorsque le << codepage >> est amene a etre change souvent. + + - mise en oeuvre de convertisseurs 7-bits <==> 8-bits a partir + du fichier keyboard.dat personnel (un compilateur C est necessaire + pour la generation de ces convertisseurs realises avec TeX et lex). + Est particulierement utile pour l'envoi de documents ASCII 7-bits + sur les reseaux. + +Corrections de bogues : + + - utilisation depuis plain TeX ; + - < et > dans le mode mathematique d'AmSLaTeX ; + - definition de \vert et de \bibcite etaient incorrectes ; + - \c est corrige comme dans la distribution de MlTeX ; + - elimination de blancs intempestifs a la suite de \endnonfrench + et \endguillemets ; + - \cite[X] n'imprimait pas X a la francaise ; + - \wrongtypedspaces pouvait etre utilise par erreur en francais. + +Contournements : + - de quelques problemes introduits par NFSS2 (\input non standard, + messages contenant des caracteres non proteges) ; + - de la methode utilisee dans seminar.sty (ou xcomment.sty) pour produire + uniquement des transparents (option slidesonly) ; + + La conformite des fichiers de la distribution est maintenant assuree +par la mise en place d'un << checksum >> qui a ete calcule par le programme +(du domaine public) de Robert M. Soloway. Ce code est inscrit dans tous les +fichiers ou cela s'est avere possible et utile. Vous pouvez donc verifier +la validite de vos fichiers en leur appliquant ce programme (avec l'option -v). +Vous devez obtenir le message : + << The checksum verification of the input file was successful. >> +Si vous obtenez le message : + << The checksum verification of the input file did not succeed. >> +alors cela signifie que vos fichiers ne sont pas d'origine. + + Des formulaires << d'installation correcte >> et << d'incidents >> +sont fournis pour etre completes et renvoyes a l'adresse indiquee. + +Mes remerciements vont a tous ceux qui ont signale des problemes ou +suggere des ameliorations. + + --bg + + +------------------------------ + +Date: 02 Dec 1993 17:37:06 +0100 +From: geoff@ficus.cs.ucla.edu (Geoff Kuenning) +Subject: [comp.text.tex] German dictionary available for ftp + +I have made a German dictionary for ispell available for ftp on +ftp.cs.ucla.edu, in the directory pub/ispell/languages/deutsch. The +dictionary was developed some time ago by Martin Schulz, who was +unable to distribute it. He passed it on to me with a request that I +make it available, and somehow I managed to lose track of his request. +I am embarrassed about how long it took me to rediscover it, but +"better late than never", so it's there for the taking. The files are +gzipped except for README/LIESMICH, which I have left uncompressed so +that you can easily view them. I suggest that you read one of these +files before retrieving any others. +- -- + Geoff Kuenning geoff@maui.cs.ucla.edu geoff@ITcorp.com + +------------------------------ + +Date: Tue, 07 Dec 1993 08:42:14 +0100 +From: Nico Poppelier <N.POPPELIER@elsevier.nl> +Subject: announcement Donald E. Knuth Scholarship + +At the 1993 TUG Annual Meeting the Board of Directors of the TeX Users Group +(TUG) has decided that, starting with the 1994 Scholarship, the Donald E. +Knuth Scholarship will be open to non-TUG members as well as to TUG members. +The same rules for the Scholarship competition will apply, and the current +committee will serve again for the 1994 Scholarship. + +Announcement of the next competition +- ------------------------------------ + +One Knuth Scholarship will be available for award next year. The competition +will be open to all TeX users holding support positions that are +secretarial, clerical or editorial in nature. It is therefore not intended +for those with a substantial training in technical, scientific or +mathematical subjects and, in particular, it is not open to anyone holding, +or studying for, a degree with a major or concentration in these areas. + +The award will consist of an expense-paid trip to the 1994 TUG Annual +Meeting at Santa Barbara, USA, and to the Scholar's choice from the short +courses offered in conjunction with that meeting, and TUG membership for +1993, if the Scholar is not a TUG member, or for 1994, if the Scholar is a +TUG member. A cap of $2000 has been set for the award; however, this does +not include the meeting or course registration fee, which will be waived. + +To enter the competition, applicants should submit to the Scholarship +Committee, by the deadline specified below, the input file and final TeX +output of a project that displays originality, knowledge of TeX, and good +TeXnique. + +The project as submitted should be compact in size. If it involves a large +document or a large number of documents then only a representative part +should be submitted, together with a description of the whole project. For +example, from a book just one or two chapters would be appropriate. + +The project may make use of a macro package, either a public one such as +LaTeX or one that has been developed locally; such a macro package should be +identified clearly. Such features as sophisticated use of math mode, of +macros that require more than ``filling in the blanks'', or creation and use +of new macros will be taken as illustrations of the applicant's knowledge. + +All macros created by the candidate should be well documented with clear +descriptions of how they should be used and an indication of how they work +internally. + +All associated style files, macro-package files, etc., should be supplied, +or a clear indication given of any widely available ones used (including +version numbers, dates, etc.); clear information should be provided +concerning the version of TeX used and about any other software (e.g. +particular printer drivers) required. Any nonstandard fonts should be +identified and provided in the form of .tfm and .pk files suitable for use +on a 300dpi laser printer. + +While the quality of the typographic design will not be an important +criterion of the judges, candidates are advised to ensure that their +printed output adheres to sound typographic standards; the reasons for +any unusual typographic features should be clearly explained. + +All files and documents comprising the project must be submitted on +paper; the input files should be provided in electronic form as well. +Suitable electronic media are IBM PC-compatible or Macintosh diskettes, +or a file sent by electronic mail. + +A brochure with additional information is available from the TUG office. To +obtain a copy, or to request instructions on e-mail submission, write to the +address at the end of this announcement, or send a message by e-mail to +TUG@tug.org with the subject ``Knuth Scholarship request''. + +Along with the project, each applicant should submit a letter stating +the following: +1. affirmation that he/she will be available to attend the 1994 TUG + Annual Meeting; +2. affirmation of willingness to participate on the committee to + select the next Scholar. + +Each applicant should also submit a `curriculum vitae' summarizing +relevant personal information, including: +1. statement of job title, with a brief description of duties and + responsibilities; +2. description of general post-secondary school education, TeX + education, identifying courses attended, manuals studied, personal + instruction from experienced TeX users, etc.; +3. description of TeX resources and support used by the + candidate in the preparation of the project. + +Neither the project nor the `curriculum vitae' should contain the +applicant's name or identify the applicant. These materials will be reviewed +by the committee without knowledge of applicants' identities. If, despite +these precautions, a candidate is identifiable to any judge, then that judge +will be required to make this fact known to the others and to the TUG board +members responsible for the conduct of the judging. + +The covering letter, `curriculum vitae', and all macro documentation that is +part of the project input should be in English. (English is not required for +the output of the project.) However, if English is not the applicant's +native language, that will not influence the decision of the committee. + +Selection of the Scholarship recipient will be based on the project +submitted. + +Schedule +- -------- + +The following schedule will apply (all dates are in 1994): + + March 7 Deadline for receipt of submissions + March 21--May 16 Judging period + May 23 Notification of winner + 31 July--4 August 1994 Annual Meeting, Santa Barbara, USA + +The 1994 Scholarship Committee consists of +- - Chris Rowley, Open University, UK (Chair); +- - David Salomon, California State University, Northridge, USA; +- - Jenny Smith, Jon Wiley and Sons, Ltd. Chichester, UK. + +Where to write +- -------------- +All applications should be submitted to the Committee in care of the +TUG office: + TeX Users Group + Attn: Knuth Scholarship Competition + PO Box 869 + Santa Barbara, CA 93102 USA + email: TUG@tug.org + +Nico Poppelier +Liaison to the 1993 Committee + + +------------------------------ + +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@TUG.org, 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.79.28) + in [tex-archive.digests.texhax.YY]texhax.NN +and ftp.tex.ac.uk (134.151.79.32) + 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 16] +***************************************** |