|
Fonts and font facilities supplied with Ghostscript |
|---|
For other information, see the Ghostscript overview.
Ghostscript is distributed with two kinds of files related to fonts:
Most of the font files supplied with Ghostscript have the extension .pfb, and a few have .pfa or .gsf. Each file defines one ordinary PostScript Type 1 outline font which any PostScript language interpreter can use. Files with .pfa or .pfb extensions are also compatible with Adobe Type Manager (ATM) and with tools that don't include a full PostScript language interpreter; files with .gsf extension are incompatible with ATM and other tools. Ghostscript compiled with the "ttfont" option can also use TrueType fonts with the extension .ttf.
When Ghostscript needs a font, it must have some way to know where to look for it: that's the purpose of the Fontmap file, which associates the names of fonts such as /Times-Roman with the names of font files, such as n021003l.pfb. Fontmap can also create aliases for font names, so that for instance, /NimbusNo9L-Regu means the same font as /Times-Roman.
Two sets of free fonts are supplied for Ghostscript:
Font packages
System File name Contents Types
DOS and
MS Windowsgs###fn1.zip Basic .pfb gs###fn2.zip Miscellaneous Various, for
different fonts
Unix ghostscript-fonts-std-#.##.tar.gz Basic .afm, .pfb,
.pfmghostscript-fonts-other-#.##.tar.gz Miscellaneous .afm, .gsf,
.pfa, .pfm
"#.##" and "###" are the version number with and without punctuation. Fonts can be found at
ftp://ftp.cs.wisc.edu/ghost/aladdin/gs###/ (for a particular version)
ftp://ftp.cs.wisc.edu/ghost/aladdin/fonts/ (for several versions)
Don Knuth's Computer Modern fonts are popular, free, and widely available. A Fontmap appropriate for these fonts is available from:
ftp://tug.ctan.org/tex-archive/fonts/cm/ps-type1/contrib/Fontmap.cmr
or from other CTAN sites.
Adobe has created sample CID-keyed PostScript fonts for Traditional Chinese, Japanese and Korean, from existing free glyph data (thus, manufactured by Adobe but not commercial-quality). They are available from:
ftp://ftp.oreilly.com/pub/examples/nutshell/cjkv/adobe/samples/Also essential CMaps should be installed to use these CID-keyed fonts. For detail of how to use CID-keyed font, refer CJK.htm.
The essential CMap files mapping from character encodings to CID are published
under freely redistributable license with no modification, available from:
ftp://ftp.oreilly.com/pub/examples/nutshell/ujip/adobe/The CMap files mapping from CID to Unicode are available from "PDF Core Font Information" at
http://partners.adobe.com/asn/developer/technotes/fonts.htmlThe CMap files mapping from CID to vendor specific encodings (Big5, PRC, ShiftJIS, Wangsung) are available from Asian font packages for Adobe Acrobat Reader. The license for included CMap files are same as above, but the included fonts are "solely for Acrobat". Do not use them with Ghostscript.
A free PostScript font for Traditional Chinese "KaiSu" in OCF format, originally provided courtesy of Jackson Technology, Ltd., Taiwan under the GPL and now distributed by the Taiwan NeXT User Group, is available from:
ftp://ftp.cs.wisc.edu/ghost/hanzi/
Prof. Wu of the Department of Economics of National Taiwan University has created several free Type 1 Chinese fonts designed to be used with TeX. His e-mail is ntut019@ccms.ntu.edu.tw. The fonts are available from
ftp://cle.linux.org.tw/pub/fonts/cwfont/
Arphic Technology Co., Ltd., has created 4 free TrueType Chinese fonts (2 for Traditional Chinese and 2 for Simplified Chinese) available under the Arphic Public License, a license very similar to the GPL. These fonts can be used as CID-keyed font via on-the-fly CIDFontType2 conversion. Refer CJK.htm The fonts and license are available from various GNU mirrors, or
ftp://cle.linux.org.tw/pub/fonts/arphic/
Mr. Tetsurou Tanaka of the Department of Engineering, University of Tokyo, has created a set of free Kanji Type1 fonts available from
ftp://ftp.ipl.t.u-tokyo.ac.jp/Font/
along with documentation in Japanese and English describing their conditions of use and how to use them. An older copy of these fonts, under somewhat different names, is available at the Ghostscript site:
ftp://ftp.cs.wisc.edu/ghost/kanji/
Mr. Norio Katayama has done some work to make Ghostscript work well with Kanji fonts. An easy-to-install Kanji font for Ghostscript, with installation instructions, is at
http://www.cit.ics.saitama-u.ac.jp/~far/howto/gs-ttf.html
The same site has patches to make Ghostscript work with Japanese outline fonts via VFlib, with documentation in both English and Japanese:
http://www.cit.ics.saitama-u.ac.jp/~far/howto/gs-vflib.html
Here are some other resources in Japanese relating to VFlib and using Ghostscript with Japanese fonts:
- http://www.ldl.jaist.ac.jp/~akr/nonresearch/free-software/ghostscript/index.ja.html
- Author <akr@jaist.ac.jp>
- http://kakugawa.aial.hiroshima-u.ac.jp/~kakugawa/Hacks/
- http://itohws03.ee.noda.sut.ac.jp/~matsuda/VFlib-FT/
- Author <matsuda@itohws01.ee.noda.sut.ac.jp>
Hwan Design Inc. created Hangul TrueType fonts (including Hanja) and released under license similar to BSD. These fonts can be used as CID-keyed font via on-the-fly CIDFontType2 conversion. Refer CJK.htm
ftp://ftp.mizi.com/pub/baekmuk/
N. Glonty and A. Samarin created in 1989 a Cyrillic extension of TeX's "Computer Modern" fonts, now freely available through the Comprehensive TeX Archive Network (CTAN), for instance at
ftp://ctan.tug.org/tex-archive/fonts/cyrillic/cmcyr/
CTAN's entire collection of Cyrillic fonts is, for instance, at
ftp://ctan.tug.org/tex-archive/fonts/cyrillic/
Basil K. Malyshev created the "Paradissa Fonts Collection" in 1993. It contains 165 fonts, including the Glonty and Samarin font above plus other Computer Modern, Euler, and LaTeX fonts, all in PostScript Type 1 format with .AFM and .PFM files, compatible with ATM. The collection could once be found through CTAN, for instance at
ftp://ctan.tug.org/tex-archive/fonts/postscript/cm/
but the CTAN archive has been reorganized and it is not clear where to find the fonts. These fonts are covered by this license:
Paradissa fonts collection.
Copyright © 1993, Basil K. Malyshev. All Rights Reserved.Licensing agreement
The author of this fonts grants to any individual or non-commercial organization the right to use and to make an unlimited number of copies of full collection or selected fonts when this is done WITHOUT CHARGE and has attached this licence agreement.
This fonts cannot be sold or distributed with any commercial product without written authorization from the author. If you want to charge a small fee for distribute fonts as is or with any software, you should contact the author.
This restriction is not intended to apply to connect time charges, or flat rate connection/download fees for electronic bulletin board services.
Basil K. Malyshev <malyshev@mx.ihep.su> 22 December 1993, Protvino, Russia.
George W. Wilson is distributing some free partial Unicode fonts he created. These fonts currently lack Arabic and CJK characters, but they include a very large subset of the remaining Unicode set. They are available in both Type 1 and TrueType formats. See
http://bibliofile.mc.duke.edu/gww/fonts/Unicode.html
Fonts occupy about 50KB each, so Ghostscript doesn't load them all automatically when it runs. Instead, as part of normal initialization Ghostscript runs a file gs_fonts.ps, which arranges to load fonts on demand using information from the font map. To preload all of the known fonts, invoke the procedure
loadallfonts
The file prfont.ps contains code to print a sample page of a font. Load this program by including it in the gs command line or by invoking
(prfont.ps) run
Then to produce a sampler of a particular font XYZ, invoke
/XYZ DoFont
For example,
/Times-Roman DoFont
For more information about how Ghostscript loads fonts during execution, see here.
Ghostscript displays text on screen using whatever font technology is provided by the system on which it runs, by calling the system's API to display text. On platforms with X Windows, this is X Windows; on MS Windows it may be TrueType or ATM; Ghostscript neither knows nor cares.
The PostScript language specifies that fonts are data structures with particular contents (for instance, they include a bounding box for the font, an Encoding vector to specify the character set, etc.), and it is common for PostScript files to use this fact; also, characters can be used as clipping regions, and can be arbitrarily algorithmically rotated, skewed, expanded or condensed, etc. Most of this information is available in some form from the underlying graphics system, but one crucial piece is not: the actual scalable outlines of the characters, which Ghostscript needs in order to implement both clipping with character shapes and arbitrarily transformed characters. Consequently
Ghostscript needs the scalable outlines of any font mentioned in a document, and loads them from the disk (.pfa, .pfb, or .gsf file) in the usual way, even if it uses the platform's font machinery to display the characters. In other words, Ghostscript must still be able to find its font files.
To make matters worse, platforms use different names for their standard fonts. For example, the Times Roman font, for which PostScript files use the name "Times-Roman", may be known as "Times-Roman", "Times Roman", "Tms Rmn", "Times New Roman", or "TimesNewRoman". The name may even be completely different: the usual Helvetica-equivalent TrueType font is called "Arial". It is possible to deal with this situation by introducing aliases in Fontmap, but there are two reasons why Ghostscript does not currently do this:
If you don't seem to be getting nice characters on the screen under MS Windows, you can try adding aliases to Fontmap, according to the documentation you'll find in there.
Ghostscript can use any Type 0, 1, 3, 4, or 42 font acceptable to other PostScript language interpreters or to ATM, including MultiMaster fonts. Beginning with release 4.0, Ghostscript can also use TrueType fonts if it was compiled with the "ttfont" option.
To add fonts of your own, you must edit Fontmap to include at the end an entry for your new font; the format for entries is documented in Fontmap itself. Since later entries in Fontmap override earlier entries, a font you add at the end supersedes any corresponding fonts supplied with Ghostscript and defined earlier in the file.
In the PC world, Type 1 fonts are customarily given names ending in .PFA or .PFB. Ghostscript can use these directly: you just need to make the entry in Fontmap. If you want to use with Ghostscript a commercial Type 1 font (such as fonts obtained in conjunction with Adobe Type Manager), please read carefully the license that accompanies the font to satisfy yourself that you may do so legally; Aladdin Enterprises takes no responsibility for any possible violations of such licenses. The same applies to TrueType fonts.
Ghostscript provides a way to construct a (low-quality) Type 1 font from a bitmap font in the BDF format popular in the Unix world. The shell script bdftops (Unix) or the command file bdftops.bat (DOS) converts a BDF file to a scalable outline using bdftops.ps . Run the shell command
bdftops BDF_filename [AFM_file1_name ...] gsf_filename fontname
UniqueID [XUID] [encodingname]
The arguments have these meanings:
BDF_filename Input bitmap file in BDF format AFM_file1_name AFM files giving metrics (Optional) gsf_filename Output file fontname Name of the font UniqueID UniqueID (as described below) XUID XUID, in the form n1.n2.n3... (as described below) (Optional) encodingname "StandardEncoding" (the default), "ISOLatin1Encoding",
"SymbolEncoding", "DingbatsEncoding"(Optional)
For instance
bdftops pzdr.bdf ZapfDingbats.afm pzdr.gsf ZapfDingbats 4100000 1000000.1.41
Then make an entry in Fontmap for the .gsf file (pzdr.gsf in the example) as described above.
The rest of this document is very unlikely to be of value to ordinary users.
As noted above, Ghostscript accepts fonts in the same formats as PostScript interpreters. Type 0, 1, and 3 fonts are documented in the PostScript Language Reference Manual (Second Edition); detailed documentation for Type 1 fonts appears in a separate Adobe book. Type 2 (compressed format) fonts are documented in separate Adobe publications. Type 4 fonts are not documented anywhere; they are essentially Type 1 fonts with a BuildChar or BuildGlyph procedure. Types 9, 10, and 11 (CIDFontType 0, 1, and 2) and Type 32 (downloaded bitmap) fonts are documented in Adobe supplements. Type 42 (encapsulated TrueType) fonts are documented in an Adobe supplement; the TrueType format is documented in publications available from Apple and Microsoft. Ghostscript does not support Type 14 (Chameleon) fonts, which use a proprietary Adobe format.
You can precompile -- convert -- any Type 1 font into C, then compile and build it into the Ghostscript executable. (Type 1 fonts include any font whose name ends with .pfa or .pfb, and it also includes all the Ghostscript .gsf fonts except the Hershey fonts.) This has no effect on rendering speed, but it eliminates the time to load the font dynamically, which may make a big improvement in total rendering time, especially for multi-page documents. It also reduces the number of auxiliary files required at run time. Fonts precompiled and built into Ghostscript this way need not appear in Fontmap, although if they do appear there, no harm is done.
The utility for precompiling fonts is named font2c. Note that since font2c uses the PostScript language program font2c.ps, Ghostscript must already be available to run it, and Fontmap must contain entries for the fonts you want to compile. For example, to precompile the Times-Italic font,
font2c Times-Italic ptmri.c
The first argument ("Times-Italic" above) is the font's name and the second ("ptmri.c") is the name of the resulting C file. You can use any file name you want, as long as it ends in ".c". It needn't be limited to eight characters unless your operating system requires this. If "XYZ.gsf" or "XYZ.pfa" is the font file's name in Fontmap, "XYZ.c" is a good choice for the C file.
Under VMS, or other systems whose the C compilers limit the length of identifiers, you must do something slightly more complicated; for that see the section on short identifiers in C. On VMS also, you must quote the font name ("{font name}") to preserve the name's mixed upper and lower case. For VMS environments in general see the VMS directions in the documentation on building Ghostscript, and ignore the rest of this section.
Note that fonts are not supplied with Ghostscript in precompiled form, since those files are quite large and can easily be recreated using font2c. There is a makefile target to run font2c on all the fonts supplied with Ghostscript. Invoke it with
make fonts_standard_c
Besides running font2c, you must compile the fonts and link them in These fonts can be used as CID-keyed font via on-the-fly CIDFontType2 conversion. Refer CJK.htm The fonts and license are available from various GNU mirrors, or
ftp://cle.linux.org.tw/pub/fonts/arphic/
Mr. Tetsurou Tanaka of the Department of Engineering, University of Tokyo, has created a set of free Kanji Type1 fonts available from
ftp://ftp.ipl.t.u-tokyo.ac.jp/Font/
along with documentation in Japanese and English describing their conditions of use and how to use them. An older copy of these fonts, under somewhat different names, is available at the Ghostscript site:
ftp://ftp.cs.wisc.edu/ghost/kanji/
Mr. Norio Katayama has done some work to make Ghostscript work well with Kanji fonts. An easy-to-install Kanji font for Ghostscript, with installation instructions, is at
http://www.cit.ics.saitama-u.ac.jp/~far/howto/gs-ttf.html
The same site has patches to make Ghostscript work with Japanese outline fonts via VFlib, with documentation in both English and Japanese:
http://www.cit.ics.saitama-u.ac.jp/~far/howto/gs-vflib.html
Here are some other resources in Japanese relating to VFlib and using Ghostscript with Japanese fonts:
- http://www.ldl.jaist.ac.jp/~akr/nonresearch/free-software/ghostscript/index.ja.html
- Author <akr@jaist.ac.jp>
- http://kakugawa.aial.hiroshima-u.ac.jp/~kakugawa/Hacks/
- http://itohws03.ee.noda.sut.ac.jp/~matsuda/VFlib-FT/
- Author <matsuda@itohws01.ee.noda.sut.ac.jp>
Hwan Design Inc. created Hangul TrueType fonts (including Hanja) and released under license similar to BSD. These fonts can be used as CID-keyed font via on-the-fly CIDFontType2 conversion. Refer CJK.htm
ftp://ftp.mizi.com/pub/baekmuk/
N. Glonty and A. Samarin created in 1989 a Cyrillic extension of TeX's "Computer Modern" fonts, now freely available through the Comprehensive TeX Archive Network (CTAN), for instance at
ftp://ctan.tug.org/tex-archive/fonts/cyrillic/cmcyr/
CTAN's entire collection of Cyrillic fonts is, for instance, at
ftp://ctan.tug.org/tex-archive/fonts/cyrillic/
Basil K. Malyshev created the "Paradissa Fonts Collection" in 1993. It contains 165 fonts, including the Glonty and Samarin font above plus other Computer Modern, Euler, and LaTeX fonts, all in PostScript Type 1 format with .AFM and .PFM files, compatible with ATM. The collection could once be found through CTAN, for instance at
ftp://ctan.tug.org/tex-archive/fonts/postscript/cm/
but the CTAN archive has been reorganized and it is not clear where to find the fonts. These fonts are covered by this license:
Paradissa fonts collection.
Copyright © 1993, Basil K. Malyshev. All Rights Reserved.Licensing agreement
The author of this fonts grants to any individual or non-commercial organization the right to use and to make an unlimited number of copies of full collection or selected fonts when this is done WITHOUT CHARGE and has attached this licence agreement.
This fonts cannot be sold or distributed with any commercial product without written authorization from the author. If you want to charge a small fee for distribute fonts as is or with any software, you should contact the author.
This restriction is not intended to apply to connect time charges, or flat rate connection/download fees for electronic bulletin board services.
Basil K. Malyshev <malyshev@mx.ihep.su> 22 December 1993, Protvino, Russia.
George W. Wilson is distributing some free partial Unicode fonts he created. These fonts currently lack Arabic and CJK characters, but they include a very large subset of the remaining Unicode set. They are available in both Type 1 and TrueType formats. See
http://bibliofile.mc.duke.edu/gww/fonts/Unicode.html
Fonts occupy about 50KB each, so Ghostscript doesn't load them all automatically when it runs. Instead, as part of normal initialization Ghostscript runs a file gs_fonts.ps, which arranges to load fonts on demand using information from the font map. To preload all of the known fonts, invoke the procedure
loadallfonts
The file prfont.ps contains code to print a sample page of a font. Load this program by including it in the gs command line or by invoking
(prfont.ps) run
Then to produce a sampler of a particular font XYZ, invoke
/XYZ DoFont
For example,
/Times-Roman DoFont
For more information about how Ghostscript loads fonts during execution, see here.
Ghostscript displays text on screen using whatever font technology is provided by the system on which it runs, by calling the system's API to display text. On platforms with X Windows, this is X Windows; on MS Windows it may be TrueType or ATM; Ghostscript neither knows nor cares.
The PostScript language specifies that fonts are data structures with particular contents (for instance, they include a bounding box for the font, an Encoding vector to specify the character set, etc.), and it is common for PostScript files to use this fact; also, characters can be used as clipping regions, and can be arbitrarily algorithmically rotated, skewed, expanded or condensed, etc. Most of this information is available in some form from the underlying graphics system, but one crucial piece is not: the actual scalable outlines of the characters, which Ghostscript needs in order to implement both clipping with character shapes and arbitrarily transformed characters. Consequently
Ghostscript needs the scalable outlines of any font mentioned in a document, and loads them from the disk (.pfa, .pfb, or .gsf file) in the usual way, even if it uses the platform's font machinery to display the characters. In other words, Ghostscript must still be able to find its font files.
To make matters worse, platforms use different names for their standard fonts. For example, the Times Roman font, for which PostScript files use the name "Times-Roman", may be known as "Times-Roman", "Times Roman", "Tms Rmn", "Times New Roman", or "TimesNewRoman". The name may even be completely different: the usual Helvetica-equivalent TrueType font is called "Arial". It is possible to deal with this situation by introducing aliases in Fontmap, but there are two reasons why Ghostscript does not currently do this:
If you don't seem to be getting nice characters on the screen under MS Windows, you can try adding aliases to Fontmap, according to the documentation you'll find in there.
Ghostscript can use any Type 0, 1, 3, 4, or 42 font acceptable to other PostScript language interpreters or to ATM, including MultiMaster fonts. Beginning with release 4.0, Ghostscript can also use TrueType fonts if it was compiled with the "ttfont" option.
To add fonts of your own, you must edit Fontmap to include at the end an entry for your new font; the format for entries is documented in Fontmap itself. Since later entries in Fontmap override earlier entries, a font you add at the end supersedes any corresponding fonts supplied with Ghostscript and defined earlier in the file.
In the PC world, Type 1 fonts are customarily given names ending in .PFA or .PFB. Ghostscript can use these directly: you just need to make the entry in Fontmap. If you want to use with Ghostscript a commercial Type 1 font (such as fonts obtained in conjunction with Adobe Type Manager), please read carefully the license that accompanies the font to satisfy yourself that you may do so legally; Aladdin Enterprises takes no responsibility for any possible violations of such licenses. The same applies to TrueType fonts.
Ghostscript provides a way to construct a (low-quality) Type 1 font from a bitmap font in the BDF format popular in the Unix world. The shell script bdftops (Unix) or the command file bdftops.bat (DOS) converts a BDF file to a scalable outline using bdftops.ps . Run the shell command
bdftops BDF_filename [AFM_file1_name ...] gsf_filename fontname
UniqueID [XUID] [encodingname]
The arguments have these meanings:
BDF_filename Input bitmap file in BDF format AFM_file1_name AFM files giving metrics (Optional) gsf_filename Output file fontname Name of the font UniqueID UniqueID (as described below) XUID XUID, in the form n1.n2.n3... (as described below) (Optional) encodingname "StandardEncoding" (the default), "ISOLatin1Encoding",
"SymbolEncoding", "DingbatsEncoding"(Optional)
For instance
bdftops pzdr.bdf ZapfDingbats.afm pzdr.gsf ZapfDingbats 4100000 1000000.1.41
Then make an entry in Fontmap for the .gsf file (pzdr.gsf in the example) as described above.
The rest of this document is very unlikely to be of value to ordinary users.
As noted above, Ghostscript accepts fonts in the same formats as PostScript interpreters. Type 0, 1, and 3 fonts are documented in the PostScript Language Reference Manual (Second Edition); detailed documentation for Type 1 fonts appears in a separate Adobe book. Type 2 (compressed format) fonts are documented in separate Adobe publications. Type 4 fonts are not documented anywhere; they are essentially Type 1 fonts with a BuildChar or BuildGlyph procedure. Types 9, 10, and 11 (CIDFontType 0, 1, and 2) and Type 32 (downloaded bitmap) fonts are documented in Adobe supplements. Type 42 (encapsulated TrueType) fonts are documented in an Adobe supplement; the TrueType format is documented in publications available from Apple and Microsoft. Ghostscript does not support Type 14 (Chameleon) fonts, which use a proprietary Adobe format.
You can precompile -- convert -- any Type 1 font into C, then compile and build it into the Ghostscript executable. (Type 1 fonts include any font whose name ends with .pfa or .pfb, and it also includes all the Ghostscript .gsf fonts except the Hershey fonts.) This has no effect on rendering speed, but it eliminates the time to load the font dynamically, which may make a big improvement in total rendering time, especially for multi-page documents. It also reduces the number of auxiliary files required at run time. Fonts precompiled and built into Ghostscript this way need not appear in Fontmap, although if they do appear there, no harm is done.
The utility for precompiling fonts is named font2c. Note that since font2c uses the PostScript language program font2c.ps, Ghostscript must already be available to run it, and Fontmap must contain entries for the fonts you want to compile. For example, to precompile the Times-Italic font,
font2c Times-Italic ptmri.c
The first argument ("Times-Italic" above) is the font's name and the second ("ptmri.c") is the name of the resulting C file. You can use any file name you want, as long as it ends in ".c". It needn't be limited to eight characters unless your operating system requires this. If "XYZ.gsf" or "XYZ.pfa" is the font file's name in Fontmap, "XYZ.c" is a good choice for the C file.
Under VMS, or other systems whose the C compilers limit the length of identifiers, you must do something slightly more complicated; for that see the section on short identifiers in C. On VMS also, you must quote the font name ("{font name}") to preserve the name's mixed upper and lower case. For VMS environments in general see the VMS directions in the documentation on building Ghostscript, and ignore the rest of this section.
Note that fonts are not supplied with Ghostscript in precompiled form, since those files are quite large and can easily be recreated using font2c. There is a makefile target to run font2c on all the fonts supplied with Ghostscript. Invoke it with
make fonts_standard_c
Besides running font2c, you must compile the fonts and link them in These fonts can be used as CID-keyed font via on-the-fly CIDFontType2 conversion. Refer CJK.htm The fonts and license are available from various GNU mirrors, or
ftp://cle.linux.org.tw/pub/fonts/arphic/
Mr. Tetsurou Tanaka of the Department of Engineering, University of Tokyo, has created a set of free Kanji Type1 fonts available from
ftp://ftp.ipl.t.u-tokyo.ac.jp/Font/
along with documentation in Japanese and English describing their conditions of use and how to use them. An older copy of these fonts, under somewhat different names, is available at the Ghostscript site:
ftp://ftp.cs.wisc.edu/ghost/kanji/
Mr. Norio Katayama has done some work to make Ghostscript work well with Kanji fonts. An easy-to-install Kanji font for Ghostscript, with installation instructions, is at
http://www.cit.ics.saitama-u.ac.jp/~far/howto/gs-ttf.html
The same site has patches to make Ghostscript work with Japanese outline fonts via VFlib, with documentation in both English and Japanese:
http://www.cit.ics.saitama-u.ac.jp/~far/howto/gs-vflib.html
Here are some other resources in Japanese relating to VFlib and using Ghostscript with Japanese fonts:
- http://www.ldl.jaist.ac.jp/~akr/nonresearch/free-software/ghostscript/index.ja.html
- Author <akr@jaist.ac.jp>
- http://kakugawa.aial.hiroshima-u.ac.jp/~kakugawa/Hacks/
- http://itohws03.ee.noda.sut.ac.jp/~matsuda/VFlib-FT/
- Author <matsuda@itohws01.ee.noda.sut.ac.jp>
Hwan Design Inc. created Hangul TrueType fonts (including Hanja) and released under license similar to BSD. These fonts can be used as CID-keyed font via on-the-fly CIDFontType2 conversion. Refer CJK.htm
ftp://ftp.mizi.com/pub/baekmuk/
N. Glonty and A. Samarin created in 1989 a Cyrillic extension of TeX's "Computer Modern" fonts, now freely available through the Comprehensive TeX Archive Network (CTAN), for instance at
ftp://ctan.tug.org/tex-archive/fonts/cyrillic/cmcyr/
CTAN's entire collection of Cyrillic fonts is, for instance, at
ftp://ctan.tug.org/tex-archive/fonts/cyrillic/
Basil K. Malyshev created the "Paradissa Fonts Collection" in 1993. It contains 165 fonts, including the Glonty and Samarin font above plus other Computer Modern, Euler, and LaTeX fonts, all in PostScript Type 1 format with .AFM and .PFM files, compatible with ATM. The collection could once be found through CTAN, for instance at
ftp://ctan.tug.org/tex-archive/fonts/postscript/cm/
but the CTAN archive has been reorganized and it is not clear where to find the fonts. These fonts are covered by this license:
Paradissa fonts collection.
Copyright © 1993, Basil K. Malyshev. All Rights Reserved.Licensing agreement
The author of this fonts grants to any individual or non-commercial organization the right to use and to make an unlimited number of copies of full collection or selected fonts when this is done WITHOUT CHARGE and has attached this licence agreement.
This fonts cannot be sold or distributed with any commercial product without w