Return-Path: Received: from [62.76.169.38] (HELO video) by vsu.ru (CommuniGate Pro SMTP 3.5b3) with ESMTP id 3767061 for CyrTeX-en@vsu.ru; Fri, 31 Aug 2001 22:04:04 +0400 To: (Cyrillic TeX Users Group) Subject: Re: Type 1 Bluesky Fonts for Cyrillic References: From: Vladimir Volovich Date: Fri, 31 Aug 2001 22:04:13 +0400 In-Reply-To: ("Ruprecht von Waldenfels"'s message of "Fri, 31 Aug 2001 19:27:20 +0200") Message-ID: Lines: 64 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.103 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi Ruprecht, "RvW" == Ruprecht von Waldenfels writes: RvW> I have been trying for some time to have better results RvW> converting to PDF by using Type 1 fonts. I've edited the divps RvW> config.ps file and added support for Type 1 cm fonts; included RvW> the {type1cm} package and used dvips and then ghostscript 7.00 RvW> to convert my File to pdf using embedded fonts. Still only the RvW> latin fonts are embedded. As I don't fully understand the RvW> mechanisms behind what I'm doing, I started to look and found RvW> out that - as it seems to me - I should need to somehow activate RvW> the bluesky cyrillic fonts I'm aiming at. What puzzles me is RvW> that these fonts are not specified as to what encoding they RvW> use. (I use T2A as an encoding) But maybe I don't understand the RvW> mechanisms behind using Type 1 Fonts. First of all, the bluesky cyrillic fonts (wncy* fonts) come not in T2A encoding, but in 7-bit OT2 encoding. (it is possible, however, to create virtual fonts which will be T2A-encoded, but will refer to bluesky cyrillic fonts). So, to use bluesky cyrillic fonts, you should use OT2 encoding: \usepackage[OT2,T1]{fontenc} \usepackage{your-input-encoding}{inputenc} Then you have two options to enter cyrillic text: either switch to OT2 encoding and wncyr font family: \fontencoding{OT2}\fontfamily{wncyr}\selectfont, and then enter cyrillic text using latin letters or switch to cyrillic 8-bit input encoding and enter cyrillic text using it (e.g. \fontencoding{OT2}\fontfamily{wncyr}\selectfont\inputencoding{koi8-r}). Then PDF will include type1 bluesky cyrillic fonts. (the default cmr font family uses LH fonts but not bluesky, but you apparently do not have type1 versions of LH fonts, so you get bitmaps in PDF). If you use T2A encoding with cmr font family, you again use LH fonts (which will become bitmaps in your PDF because you do not have type1 version of LH fonts). And make sure to have your psfonts.map and pdftex.map contain a section with wncy* fonts (look e.g. for wncyr10.pfb). You can also find TeX support files for the cyrillic bakoma fonts (they are also CM-like) at ftp://ftp.vsu.ru/pub/tex/font-packs/c1fonts/ after unpacking the tarballs into your texmf tree, do not forget to update your psfonts.map and pdftex.map files. on teTeX, this could be accomplished by adding a reference to cmbkmcyr.map included in the c1fonts package into the script updmap, and running that script. [the paradissa-corr tarball is provided as a replacement for original type1 fonts which contain some incompatibilities with dvips and pdftex embedding algorithms]. Best, v.