Dear Sir,
On Mon, 01 Oct 2007 09:39:06 +0200 (CEST)
Werner LEMBERG [EMAIL PROTECTED] wrote:
Following is a function whose API is similar to FT_Select_Charmap()
but ignores non-Microsoft cmap subtables. Does it serve your
purpose?
I think my quick fixes already serves Dmitry's purposes. Your
Hello,
http://bugs.winehq.org/show_bug.cgi?id=9840 has a ttf font attached
to it which can be perfectly displayed in Windows, but Wine is not able
to actually show any character using this font, only 'c' is displayed.
That's because Freetype selects first unicode cmap table which happens
to be
Hi,
On Sun, 30 Sep 2007 21:13:00 +0900
Dmitry Timoshkov [EMAIL PROTECTED] wrote:
http://bugs.winehq.org/show_bug.cgi?id=9840 has a ttf font attached
to it which can be perfectly displayed in Windows, but Wine is not able
to actually show any character using this font, only 'c' is displayed.
[EMAIL PROTECTED] wrote:
Your patch assumes that Apple Unicode cmap is often
broken but others are more reliable, but I'm afraid
that this is not generic assumption.
That was really a hack to show that other cmap tables actually
work better for that font. Of course other fonts can have cmap
Dear Sir,
On Mon, 1 Oct 2007 11:52:19 +0900
Dmitry Timoshkov [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
So, I think, it's better for Wine to have internal priorities
of prefered cmap subatble and choose the best cmap subatble
by himself. How do you think of?
Wine uses FT_Select_Charmap
On Sun, 2007-09-30 at 20:16, [EMAIL PROTECTED] wrote:
As I've shown in previous post, Apple Unicode cmap in the
sample font is NOT broken from the viewpoint of data
structure, I think. To detect broken cmap as you say,
it's required to investigate cmap, loca, glyf subtables
content
