[Fonts] Re: [ft] Creating an [OT]TF font from BDF font

2006-01-23 Thread Werner LEMBERG
 So I'd like to make the following changes to David's proposal:

All of this looks very promising.  I think the final decision on the
table format can only be done after converting a bunch of BDFs forth
and back.


Werner
___
Fonts mailing list
Fonts@XFree86.Org
http://XFree86.Org/mailman/listinfo/fonts


[Fonts] Re: [ft] Creating an [OT]TF font from BDF font

2006-01-23 Thread Werner LEMBERG
 I also recall discussions which discovered that the .otb extension
 was otherwise unused in most of the world.  It doesn't matter at all
 to me; I ask FreeType to try and open the font, completely ignoring
 the extension has proven a valuable property, although it does
 sometimes challenge the FreeType font file handling code with
 'unusual' file data.

I fully agree, but Windows allows to hide the display of file name
extensions -- the demo program might also try `foo.otb' to find the
real file name if the user just gives `foo'.


Werner
___
Fonts mailing list
Fonts@XFree86.Org
http://XFree86.Org/mailman/listinfo/fonts


[Fonts] Re: [Freetype] Encodings XLFDs within sfnt

2003-07-09 Thread Werner LEMBERG
 In order to preserve bitmap font names as we switch to sfnt for
 XFree86, I need to have fonttosfnt put the original font name in
 some place where mkfontscale can find it.

 The proper way would be to formally define a new sfnt table, for
 example ``XF86''.  However, I think it is simpler and quite as
 reliable to put a non-standard signature in some standard place.

Why do you think it is more complicated to add a new sfnt table?

 I'm currently tempted to use the ``comment'' string in the ``name''
 table.  I could generate it to be

   XFree86 font, original name was -misc-fixed-...

 and then check for this string.

Hmm, an XF86 table would also allow to store unconverted BDF
properties which are lost otherwise.  I vote for an XF86 sfnt table.


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


[Fonts]Re: [Freetype] FreeType bug report

2002-09-27 Thread Werner LEMBERG


 1. FreeType crashes at ttgload.c:103 if hhea-number_Of_HMetrics
is 0.  The problem is with k, which is assumed to be at least 1.

I've just added a guard, thanks.

 2. FreeType refuses to get an sbit that has a glyph index beyond
 maxp-numGlyphs.  Note that the OpenType spec explicitly allows a
 font to have no scalable glyphs, although it warns against legacy
 rasterisers not being able to process such fonts.
 
 3. FreeType refuses to load a font that has no loca or glyph tables.
 See the above note.

Those are valid concerns IMHO.  David, do you have time to handle
that?


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



[Fonts]Re: [Freetype] Buggy metrics with FreeType 2 and BDF or PCF fonts?

2002-08-20 Thread Werner LEMBERG


 I'm attaching a little test program that you should run on 8x13.bdf
 and 8x13.pcf.  Please notice the (x, y) couple printed for every
 glyph, which are, respectively,

   face-glyph-metrics.horiBearingX and
   face-glyph-metrics.horiBearingY.

 The 8x13 font has a bounding box of (0, -2) through (8, 11).  Thus, I
 believe that the correct values should be (0, 704).  However, I'm
 getting

   (0, -128) for the BDF version; and
   (512, 704) for PCF version.

 Can anyone confirm this bug, or tell me what I'm doing wrong?

I can confirm that.

PCF: It is a typo in pcfdriver.c which uses `rightSideBearing' instead
of `leftSideBearing'.

BDF: The bitmap's height was missing in horiBearingY.

I've fixed that in the CVS.  Thanks for the report.


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



Re: [Freetype] Re: [Fonts]New versions of mkfontscale and FreeType2 backend

2002-05-01 Thread Werner LEMBERG


 RG (I tested it with Arphic TTF which be distributed with most
 RG Linux distributions and all *BSD.)

 Hmm, there may be problems with this font; I'm told it has bugs.
 Maybe the FreeType folks can comment?

Yes, Just's ttDump reports a problem with the `glyf' table (and
dies :-) -- all other tables are OK apparently, but I haven't
investigated it in more detail.

 I guess a suitable heuristic would be to decalare all monospaced fonts
 in East-Asian encodings to be charcell.

Indeed, it is rather safe to assume that all CJK glyphs have the same
width.  There do exist fonts with different heights (especially for
typesetting Japanese), but I don't know how this is implemented in the
font since the height is context-dependent.  I believe that vertical
kerning is done by the application and not by the font (please correct
me if this assumption is incorrect).


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