[Fonts] Re: After-XTT's extension of the encoding field.

2003-09-04 Thread T.SHIOZAKI
From: Juliusz Chroboczek [EMAIL PROTECTED]
Subject: Re: [Fonts] After-XTT's extension of the encoding field.
Date: 04 Sep 2003 17:17:59 +0200
Message-ID: [EMAIL PROTECTED]

 TTCap was based on the IMHO erroneous assumption that it is better to
 hack extensions to fonts.dir rather than provide an extensible
 database for font-related information.  Today, we do have just such an
 extensible database: fontconfig.

 As far as the implementation goes, TTCap lives in the font backend,
 which implies that somebody got the layering wrong.

You slightly mistake the fact.

I (as the inventor of TTCap) intended TTCap to be just kludge.
I did not get the layering wrong and not assume something erroneous,
but just intentionally ignored the layering.
Actually, I also guess TTCap is not elegant but ugly.
However it has been giving surely powerful and practical solution to
CJK (at least Japanese) people.


 I do not deny that TTCap does work around real problems.  However, I
 do not believe that TTCap is something we want to follow.

It seems for me that not a few users still need TTCap (and X-TT)
and several persons want to continue supporting it, although I do not
know whether it is better TTCap to be retained more or to be expanded
into other backends.  I wonder we are not homogeneous.

# I intend not to say anything more.


--
Takuya SHIOZAKI

___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts


[Fonts] Re: After-XTT's extension of the encoding field.

2003-08-14 Thread Jungshik Shin
On Thu, 7 Aug 2003, Mike FABIAN wrote:

 Jungshik Shin [EMAIL PROTECTED] :

  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

___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts


Re: [Fonts] Re: After-XTT's extension of the encoding field.

2003-08-14 Thread Jungshik Shin
On Fri, 8 Aug 2003, Mike FABIAN wrote:
 Jungshik Shin [EMAIL PROTECTED] :
  On Thu, 7 Aug 2003, Mike FABIAN wrote:

  It can be automatically generated.  The /usr/sbin/fonts-config script
  on SuSE Linux generates such TTCap entries automatically into the
 
  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)

 Yes, it does.

details on how Mike's font-config script works... snipped

  Thanks you for the details. It seems that you gave
a lot of thought to the script and that it meets my need (if I have to
tweak fonts.scale/dir files ever again :-))

 Jungshik
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts


[Fonts] Re: After-XTT's extension of the encoding field.

2003-08-14 Thread Mike FABIAN
Jungshik Shin [EMAIL PROTECTED] $B$5$s$O=q$-$^$7$?(B:
(B
(B On Sat, 2 Aug 2003, Chisato Yamauchi wrote:
(B
(B   Have you seen CJK's *TYPICAL* fonts.dir of TrueType fonts?
(B It is following:
(B
(B  Not many people would be fond of tweaking fonts.dir/scale files
(B these days :-)
(B
(BIt can be automatically generated.  The /usr/sbin/fonts-config script
(Bon SuSE Linux generates such TTCap entries automatically into the
(Bfonts.dir if it detects that xtt is enabled in /etc/X11/XF86Config.
(B
(BCurrently it generates only entries for artifical bold and italic
(Bfor fonts which do not yet have real bold and italic versions.
(B
(BI could extended it to support more features of TTCap, but I'm not
(Bsure whether it is worth the effort.
(B
(BI agree that the old X fonts are broken beyond repair and we should
(Bmove on to use fontconfig/Xft as much as possible.
(B
(BThe old font system must be kept for backwards compatibility of course
(Bbut it is probably just a waste of effort to add more extensions the
(BX11 core font system.
(B
(B-- 
(BMike Fabian   [EMAIL PROTECTED]   http://www.suse.de/~mfabian
$B?gL2ITB-$O;E;v$NE([EMAIL PROTECTED](B
(B___
(BFonts mailing list
(B[EMAIL PROTECTED]
(Bhttp://XFree86.Org/mailman/listinfo/fonts