Re: [Fonts]FreeType bug report
On Tuesday 20 August 2002 9:57 pm, Juliusz Chroboczek wrote: | OT I'm pretty sure Microsoft ships a number of .ttf files with only | OT bitmaps and no outlines with Windows... | | Interesting. Which ones? GulimChe.ttf (Korean lang.font) has enermous amount of bitmaps, I think, for all point sizes up to 22pt. Original TTF is about 6MB in size, imported into PfaEdit it became .. 25MB in size! But GulimChe still has outlines (it's just small part of the font, though)... | | Juliusz | ___ | Fonts mailing list | [EMAIL PROTECTED] | http://XFree86.Org/mailman/listinfo/fonts -- Vadim Plessky http://kde2.newmail.ru (English) 33 Window Decorations and 6 Widget Styles for KDE http://kde2.newmail.ru/kde_themes.html KDE mini-Themes http://kde2.newmail.ru/themes/ ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]FreeType bug report
On Tuesday 20 August 2002 1:21 am, Pablo Saratxaga wrote: | Kaixo! | | On Mon, Aug 19, 2002 at 07:35:33PM +0200, Juliusz Chroboczek wrote: | I'm currently exploring the possibility of moving XFree86 from the PCF | format to the sfnt format for bitmap fonts. I've encountered a number | | You should also decide on an extenson name other than .ttf, to avoid | that those bitmap only ttf files get confused wwith real scalable | fonts by people out there, otherwise there would be a lot of bad | consequences. It seems to me that .ttf extension is o.k. for such fonts. But indeed Qt3/KDE3 and GNOME2/GTK2 should be patched/tested against such fonts. BTW: I can tell that KDE3 can't print using OpenType fonts (exported from PfaEdit), which is *not good*. -- Vadim Plessky http://kde2.newmail.ru (English) 33 Window Decorations and 6 Widget Styles for KDE http://kde2.newmail.ru/kde_themes.html KDE mini-Themes http://kde2.newmail.ru/themes/ ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]FreeType bug report
Kaixo! On Tue, Aug 20, 2002 at 05:44:13PM +0400, Vadim Plessky wrote: | You should also decide on an extenson name other than .ttf, to avoid | that those bitmap only ttf files get confused wwith real scalable | fonts by people out there, otherwise there would be a lot of bad | consequences. It seems to me that .ttf extension is o.k. for such fonts. I disagree. Or have you tested with all programs that use TTF fonts directly, and tested also in other operating systems (Windows, MacOS, BeOS,...) and other graphical environments (like Berlin) that those fonts will work and won't break anything ? I'm afraid that a vast majority of programs and OS currently using TTF simple expect them to always have scalable glyphs; what will happen if one of such programs tries to use a bitmap only font for displaying at a size for xhich there are no bitmaps embedded ? But indeed Qt3/KDE3 and GNOME2/GTK2 should be patched/tested against such fonts. There are a lot of utilities out there that use directly TTFs; from little utilities creating images for web counters, to programs doing 3D rendering of text,... and don't forget also other non-X11 environments; very bad press will happen if fonts are disseminated that cause problems (and they probably will be disseminated if people think they are just normal TTF fonts). So, using a different extension name will solve a lot of trouble. -- Ki ça vos våye bén, Pablo Saratxaga http://chanae.stben.be/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese] msg01080/pgp0.pgp Description: PGP signature
Re: [Fonts]FreeType bug report
Pablo Saratxaga [EMAIL PROTECTED] writes: Kaixo! On Tue, Aug 20, 2002 at 05:44:13PM +0400, Vadim Plessky wrote: | You should also decide on an extenson name other than .ttf, to avoid | that those bitmap only ttf files get confused wwith real scalable | fonts by people out there, otherwise there would be a lot of bad | consequences. It seems to me that .ttf extension is o.k. for such fonts. I disagree. Or have you tested with all programs that use TTF fonts directly, and tested also in other operating systems (Windows, MacOS, BeOS,...) and other graphical environments (like Berlin) that those fonts will work and won't break anything ? I'm afraid that a vast majority of programs and OS currently using TTF simple expect them to always have scalable glyphs; what will happen if one of such programs tries to use a bitmap only font for displaying at a size for xhich there are no bitmaps embedded ? I'm pretty sure Microsoft ships a number of .ttf files with only bitmaps and no outlines with Windows... it's nothing revolutionary and nothing robust software doesn't have to handle already. And to the extent that most font handling for open-source handling goes through FreeType and (increasingly) through fontconfig, there is really very little difference between a .ttf file with only bitmaps, a .ttf file with only bitmaps called something else, and a .pcf file ... the software can encounter such fonts in any of the cases. Regards, Owen ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]FreeType bug report
PS what will happen if one of such programs tries to use a bitmap PS only font for displaying at a size for xhich there are no bitmaps PS embedded ? It will get sixty-odd thousand blank glyphs. Juliusz ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]FreeType bug report
OT I'm pretty sure Microsoft ships a number of .ttf files with only OT bitmaps and no outlines with Windows... Interesting. Which ones? Juliusz ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
[Fonts]FreeType bug report
Hello, Thanks a lot for the previous fix, I'll try it out tonight. I'm currently exploring the possibility of moving XFree86 from the PCF format to the sfnt format for bitmap fonts. I've encountered a number of minor bugs in FreeType 2.1.2 that prevent me from using such bitmap-only sfnts. 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. 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. For me, point 1 is not important (I've decided to generate a single htmx entry), but I think that any crash of FreeType is a severe bug. Point 2 is important, as it won't do to generate loca entries for all glyphs: such a font is too difficult to distinguish from a bona fide scalable font, and I want to generate a single loca entry (for .notdef). As to point 3, I don't care much about it; still, it might be handy to generate fonts with no loca/glyf tables in order to prevent legacy software from mistaking them for scalable fonts. No rush, but do tell me what you've decided to do about the above. Thanks, Juliusz ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
