TUGboat, Volume 12 (1991), No. 2

Merits and some problems of producing texts of wlshyphenation capabilities for German lan- with diacritical marks and multilingual editions us- guage texts. ing TEX were shown by G. Koch in examples from Hebrew texts and bilingual book projects. o Walter A. Obermiller Philosophical and technical insights into print- Max-Planck Institut fiir Chemie Geochemistry Division ing old German documents with appropriate old Postfach 3060 fonts were presented by Yannis Haralambous. He 6500 Mainz introduced old German Fraktur, Gotisch, Schwaba- FRG cher and Initialen fonts he created with METAFONT. walterlmpch-mainz.mpg.dbp.de and showed old German works of print he has type- set in them. The fonts are fantastic! Yannis will make them available in Heidelberg soon. G. Bienek announced the availability of a new T@ bulletin board. It is accessible under the num- ber +49-8024-8416 and will carry the offerings of the normal DANTE distribution. A new twist to including graphics in TEX doc- uments was introduced by F. Sowa. A preprocessor Philology converts Tag Image File Format (TIFF) graphic files into a .pk font file which is then simply printed by including a . tex file also produced in the process. Russian T&jX The bitmap is distributed over a number of charac- ters. so even old drivers should be able to handle Basil Malyshev, Alexander Samarin and them. His graphic inclusion mechanism hence does Dimitri Vulis not require the use of a \special. The preproces- For processing Russian texts [I] by one should sor is capable of dealing with simple bitmaps and adjust TEX to use: Russian language hyphenation, has dithering capabilities to deal with grayscale and coding of the Russian characters, and fonts with the RGB pictures. cyrillic symbols. From the user interface "department", L.P. T)jX 3.0 can be adjusted without changes! Kurdelski presented a Smallt alk based system to The hyphenation patterns described in [2] are simplify the creation and processing of TEX docu- used for Russian language. Actually is bilin- ments on PCs and their output via printers con- gual- the Russian and English hyphenation pat- nected to a heterogeneous network, so as to relieve terns are loaded by following file: the user from having to deal with DOS or network software. \language=O % English The final day of the meeting had four tutori- \lefthyphenmin=2 als on the agenda. H. Kopka introduced the use \righthyphenmin=3 of PI- macros, while B. Burr gave an introduc- \input ehyphen.tex tory IPW tutorial. A tutorial on how to change \language=l % Russian \lefthyphenmin=2 IPW style files (H. Partl) and one on METAFONT (F. Sowa) were followed by a final discussion. \righthyphenmin=2 \input cyrdef.tex Conclusion \input rhyphen.tex Many different uses of TEX in Germany are reflected \language=O % English as default by the talks outlined above. As more and more peo- In the file cyrdef . tex proper catcode, uccode, ple are using TpX here, many more will be thought lccode and mathcode are set for cyrillic characters. of. As all meetings that I have attended this Switching between Russian and English hy- meeting too was very short. phenation is performing by \language: setting The challenges for the immediate future are \language=O means English, \language= I means clear: introduction of the new 256 character Latin Russian. English words are not hyphenated if the fonts, for which the encoding scheme has been Russian patterns are active and reversely. Another tentatively approved at the Cork meeting. Only possibility is to merge the English and Russian hy- new German hyphenation patterns and a revised phenation patterns as a single language. german. sty will then be needed to make full use TUGboat, Volume 12 (1991), No. 2 213

rn can use any 8-bit coding scheme for Rus- where cmrl0 and cmcyrlo are source Latin and sian characters- "alternative" l, K01-8~,IS0 8859- cyrillic fonts, xcmrl0 is the virtual font, which will 53, etc. The hyphenation patterns and .tfm files consist of two files: xcmri0. tfm and xcmrl0 .vf. should correspond to the coding scheme being used. They are accepted by the standard program Russian QX works with virtual fonts; each of them vf t 0~1.~ consists of an original Computer Modern font (be- Note that such merging is correct because the low the 128~~code) and a font with cyrillic char- cyrillic fonts are created by METAFONT on the base acters (above the 128~~code). For m the cyril- of the same setup files, like cmrl0.mf. The font lic characters are completely equal in "rights" with parameters are identical for Latin and cyrillic fonts. Latin characters. One could define new commands The files are merged by the following couples: as Russian words! The simultaneous usage of cyrillic cmbx* cmcbx* xcmbx* and Latin characters does not require any additional cmbxsll0 cmcbxsll0 xcmbxsll0 commands for switching or separating them. cmbxtilO cmcbxtilo xcmbxt ilO For creating the . tfm file of a virtual font the cmbxsll0 cmcbxsll0 xcmbxsllO program tfmerge was designed. It merges the . tfm cmbxt i 10 cmcbxtilo xcmbxtilo for a Computer Modern font and . tfm for a cyrillic cmmi5 cmcyr5 xcmmi5 xcmmi6 font into a virtual font tfrn and .vf in accordance cmmi6 cmcyr6 . cmmi* cmct i* xcmmi* with the coding scheme of the Russian characters. cmmiblO cmcbxlO xcmmibl0 The managing of the program tfmerge is per- cmr* cmcyr* xcmr* formed by a file which contains the table of corre- cmsl* cmcsl* xcmsl* spondence between the position of a character in a cmslttlO cmcslttlo xcmsltt 10 virtual font and the position of the same character cms s* cmcss* xcmss* in a cyrillic font. E.g., the correspondence between cmssbxlO cmcssbxlo xcmssbxlo alternative coding into virtual fonts and "phonetic"- cmssdclO cmcssdcl0 xcmssdcl0 like coding (with swapped lower/upper case) into cmssi* cmcssi* xcmssi* cyrillic fonts [3] is expressed by the following pairs: cmt i* cmcti* xcmti* cmtt * cmctt* xcmtt* \200 :a \201:b Mathematical Italic fonts crnrni* are merged \202 : w with Cyrillic Text Italic fonts and proper mathcode's ..... have been set. One can use Russian letters in math. \36O :Q To use another realization of the cyrillic fonts one should create the table of correspondences for The left part of a pair (up to delimiter character tfmerge and select other couples for merging. ":") is the position in virtual fonts and the right part Files plain. t ex for TJ# and If onts .tex for is the position in cyrillic fonts. The position can be MTJ# should be changed to substitute the references specified by a symbol or by an octal number. When to the Latin font being merged by references to the sorted by left parts the file becomes simpler: proper virtual font. \200:abwgdevzijklmnoprstufhc~()\177yx~'q For a VAX/VMS realization. creating . fmt files \240:ABWGDEVZIJKLMNOP requires only setting the parameter trie-size to \NO: RSTUFHC" [I -YX\\@q 16000. For SB30TEX (on MS-DOS) some .tfm files The correspondence between IS0 8859-5 coding are not preloaded, because the size of the . tfm files in virtual fonts and the "phonetic1'-like coding in is increased. For EmQX C3al the options -i -0 -8 cyrillic fonts is expressed by: -mt : 12700 have been set. \260:abwgdevzijklmnoprstufhc~~)\177yxl'q The main problem with virtual fonts is that not \320:ABWGDEVZIJKLMNOPRSTUFHC-[I-YX\\@Q all .dvi drivers can handle the virtual fonts. To avoid that problem the program PosTeX has been The calling sequence of tfmerge program is: designed. It reads a .dvi file, expands the virtual TFMERGE [-dl cmrlO cmcyr1O xcmrl0 fonts and writes a new .dvi file which is accepted Used mainly on the IBM PC, alphabetically or- by any .dvi driver. dered, almost identical to Microsoft's codepage 866. There are some . dvi drivers which already ac- Used on some UNIX-like systems. based on cept the virtual fonts, e.g. from the fine collection "phonetic" correspondence between Latin and cyril- Really more comprehensive utilities are needed lic characters. to create virtual fonts. Used on VAX/VMS, alphabetically ordered. 214 TUGboat, Volume 12 (1991), No. 2 by Eberhard Mattes. One can use such . dvi drivers without PosTeX. But extensive usage of virtual fonts with a previewer will require more memory and in- crease the time before showing the first page. For a . dvi file which consists of a single cyrillic character. three files xcmrl0. vf, cmrl0. pk and cmcyr 10.pk are opened instead of one file cmcyrlO.pk, and to- tal required memory is increased by one-third. This example only shows that extensive usage of virtual fonts will require more economic realization. Another reason to use the program PosTeX is the portability of .dvi files. Our virtual fonts refer to local coding of Russian characters and immedi- The macros \Alph and \alph are redefined too. ately after wing a . dvi file is not portable. After being transforming by PosTeX a .dvi file becomes References portable - it refers only to ordinary fonts. [l] Barbara Beeton, Mathematical symbols and It's also possible to enter Russian text using cyrillzc fonts ready for distribution (revised). pure ASCII. for people who don't do much Russian TUGboat 6 (1985), no. 3, pp. 124-128. wing, but need to set an occasional citation. In [2] Dimitri Vulis. Notes on Russian m. TUGboat this case. control sequences can be used, and it is 10 (1989), no. 3, pp. 332-336. necessary to specify the boundary between Russian H.J. and non-Russian text to switch the hyphenation pat- [3] ~~OHTHH ~p. Memanpoexm xupunnoe- cxozo an$aeuma dnx neuamawqux ycmpoCcme terns. E.g.. for printing this article in TUGboat c the WNcyr realization of the cyrillic characters by ealcoxua pa3peue?tuea: npenp~~~HQB3. Thomas Ridgeway has been used. 90-66, IIPOTBMHO.1990. An integration of Russian into "International I4Wnby Joachim Schrod is done by the following o Basil Malyshev Institute for High Energy Physics Russian. sty file: 142284, Protvino, USSR \def \cont entsnameCCo~epxa~ae) [email protected] \def \listf igurename(Cnmco~prncy~xo~) o Alexander Samarin \def \listtablename(Cnmox T~~~HII) Institute for High Energy Physics \def \abstractname