Re: TrueType fonts, Type1 fonts, X, and the FHS
>>>>> In <[🔎] 20011101095434.A25755@deadbeast.net>
>>>>> Branden Robinson <branden@debian.org> wrote:
>> [1 <text/plain; us-ascii (quoted-printable)>]
>> On Thu, Nov 01, 2001 at 11:05:38PM +0900, Yasuhiro Take wrote:
>> > Please tell me your idea to solve the problem that two types of fonts.scale
>> > file are needed for one TrueType font: one for freetype backend and the other
>> > for xtt backend.
On my understanding, both freetype and xtt do not refer fonts.scale
on runtime. They refers fonts.dir only.
>> Yikes, I was unaware of this.
>>
>> You mean the two backends use the same name for two different file
>> formats? Need I point out how dumb that is?
>>
>> Anyway, please post examples of each style of font.scale.
>>
>> I imagine the ones for the freetype backend are in the traditional
>> format:
>>
>> 44
>> a010013l.pfb -urw-urw gothic l-book-r-normal--0-0-0-0-p-0-iso8859-1
>> a010015l.pfb -urw-urw gothic l-demibold-r-normal--0-0-0-0-p-0-iso8859-1
>> [...]
Both freetype and xtt backends can handle the traditional format
of cause. For example:
Arial.ttf -monotype-arial-regular-r-normal--0-0-0-0-p-0-iso8859-1
Freetype backend can handle an extended format. The format likes
bellow:
:2:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0
This entry means '2nd Face in mincho.ttc is this XLFD'. The syntax
is described in "5.1 The FreeType TrueType backend" of
/usr/share/doc/xfree86-commo/README.fonts.gz
Xtt backend can handle this freetype's syntax.
And furthermore, xtt can also handle extended syntax called `TTCap.'
For example:
fn=1:ai=0.3:dfhsmw3.ttc -dynalab-pmincho-medium-i-normal--0-0-0-0-p-0-iso8859-1
fn= means "Face number", ai= means "Automatic Italic: specifies how
the glyph is slanted.
This type of syntax is descrbed in "5.2 The X-TrueType TrueType
backend" of /usr/share/doc/xfree86-commo/README.fonts.gz.
And more detail can be found in /usr/share/doc/xfs-xtt/X-TT/INSTALL.eng.gz
Freetype can not handle TTCap. So, when freetype backend is used
and some fonts.dir in fontpaths contain TTCap syntax, Freetype backend
can not interpret fonts.dirs. These fontpaths are ignored with error.
So, There are 3 types of fonts.dir formats:
Traditional format
Freetype extended format
TTcap extended format
Xtt can handle all of 3 formats.
Freetype can handle Traditinal and Freetype extended formats.
Other engine (bitmap, type1 and so on) can handle only Traditional format.
>> Anyway, the idea that springs to mind is perhaps to have two files
>> generated by update-fonts-scale:
>>
>> fonts.scale.xc (for "X Consortium", the traditional format)
>> fonts.scale.xtt (for "X-TrueType")
>>
>> And then have fonts.scale in each directory symlink to one of those
>> files. I'm still thinking about how the decision about which one to
>> symlink to should be made. Maybe a debconf template.
I think this solution is suitable.
--
ISHIKAWA Mutsumi
<ishikawa@linux.or.jp>, <ishikawa@debian.org>, <ishikawa@redhat.com>
Reply to: