logo       

Re: After-XTT's extension of the encoding field.: msg#00013

xfree86.fonts

Subject: Re: After-XTT's extension of the encoding field.

On Thu, 7 Aug 2003, Mike FABIAN wrote:

> Jungshik Shin <jshin@xxxxxxxxxxx> さんは書きました:
>
> > On Sat, 2 Aug 2003, Chisato Yamauchi wrote:
> >
> >> Have you seen CJK's *TYPICAL* fonts.dir of TrueType fonts?
> >> It is following:
> >
> > Not many people would be fond of tweaking fonts.dir/scale files
> > these days :-)

> It can be automatically generated. The /usr/sbin/fonts-config script
> on SuSE Linux generates such TTCap entries automatically into the
> fonts.dir if it detects that xtt is enabled in /etc/X11/XF86Config.

That sounds nice. It'll certainly make things easier. However, it could
make some people frustrated if it just overwrites the existing fonts.dir
(I don't know whether fonts-config on SuSE Linux does that or not)
that was 'hand-tweaked' to their satisfaction. In the past, I made it
a rule to back up fonts.dir/fonts.scale after losing heavily customized
fonts.dir/fonts.scale to an automated tool a couple of times.

> I agree that the old X fonts are broken beyond repair and we should
> move on to use fontconfig/Xft as much as possible.
>
> The old font system must be kept for backwards compatibility of course
> but it is probably just a waste of effort to add more extensions the
> X11 core font system.

Much better said than mine. This is exactly what I meant but apparently
my choice of words was not that good. If I had thought that support
for X11 core fonts need to be removed _now_, I wouldn't have spent my time
on gb18030.2000-1 issue (Xfree86 bug 441) let alone fixing bugs in CJK
font encoding files for freetype module last year.

Jungshik


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise