On Tue, 2003-07-29 at 10:09, Egbert Eich wrote:
> Owen Taylor writes:
> > On Tue, 2003-07-29 at 04:44, Egbert Eich wrote:
> > > The After-XTT project which has picked up the long orphaned
> > > xtt truetype font renderer has submitted patches to xtt which
> > > recently were committed to the CVS.
> > > One of the changes prepares for the extention of the font encoding field:
> > >
> > > [From the changelog]
> > > - Preparation for extending the encoding field of XLFD. X-TT permits
> > > the following additional XLFD format:
> > > "-foo-foo-medium-r-normal--0-0-0-0-c-0-foo.2000-0.0"
> > > "-foo-foo-medium-r-normal--0-0-0-0-c-0-foo.2000-0.1"
> > > The last number can be used to indicate the plane number of a huge
> > > character set.
> > >
> > > This will work around an Xlib problem that the XCharStruct
> > > array of huge - but sparsely populated - fonts can get large.
> > >
> > > To get a uniform behavior it would be desirable if the 'plane' field
> > > would be interpreted equally by all renderers.
> > >
> > >
> > > Ideas/comments/opinions on this extensions?
> >
> > Let the poor thing die in peace...
> >
> > Old X fonts are pretty much irretrievably broken, we have a good
> > replacement system. Adding extensions such as the above that are
> > basically API extensions (they do no good unless the app knows about
> > them) doesn't make sense at this point.
> >
>
> Well, in legacy apps you usually specify the fonts using app defaults.
Sure, but you aren't exactly going to say "I want this font, but
everything I'm going to use comes from one plane". Or I see
that as unlikely, anyways.
Regards,
Owen
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
