GNOME Bugzilla – Bug 86591
Combining Jamos support with Xft
Last modified: 2004-12-22 21:47:04 UTC
Now basic-xft rendering module can't shape Combining Hangul Jamos (U+1100 - U+11FF). A new rendering module is needed for this. This patch adds hangul-xft module. Additionally I did some cleanup on hangul-x module because a few same #defines and/or tables were shared between hangul-x and hangul-xft.
Created attachment 9478 [details] [review] pango patch to add hangul-xft module
Ah no one checked whether this patch is good or not... Maybe there's no guy here to understand the hangul module and this patch? Then OK to commit this patch? Many Korean guys have tested this version of the patch and no one complained yet. At least I could integrate this stuff to the HEAD, if I success to build that correctly).
No, I haven't forgotten about your patch, I'm just extremely shortchagned for time recently.
Some problem: When I use "real" (not "sans" or something like) English Truetype font with Korean font associated, the hangul-xft module can't find Korean glyphs from the given font. match any family == "Arial" edit family =+ "Baekmuk Gulim"; I guess some code in pango or Xft assigns different Truetype font according to the unicode range. Is it right? How can I let hangul-xft use Hangul font for the U+1100~U+11FF range?
I'm not quite sure I understand your problem. Is the problem that your font doesn't have glyphs for the U+1100 - U+11FF range, but only the composed characters?
I've applied your patch to the HEAD branch of Pango; I think it might be a little big to go into stable. A) Could you check what I applied? There were some conflicts with the ksc5601.1992-3. B) Could you fix up the ksc5601.1992-3 code to match the way for the other encodings you render the prefix of an uncomposable Hangul syllable as a syllable? Thanks.
> I'm not quite sure I understand your problem. Is the problem > that your font doesn't have glyphs for the U+1100 - U+11FF > range, but only the composed characters? Both. When basic-xft renders Hangul syllables correctly, hangul-xft can't find glyphs on U+AC00~ or U+1100~.
Now ksc5601.1992-3 code fixed in HEAD. 2002-08-01 Changwoo Ryu <cwryu@debian.org> * modules/hangul/hangul-x.c (render_syllable_with_ksx1005): Renders the prefix of uncomposable Hangul syllable in the way of other font encoding code. Well, at least is it possible some "bug fixes" go into stable? There are some leaks and wrong glyph selection fixed in this patch.
Moving bugs to new hangul component
Sorry for not responding earlier; yes bug fixes can go into stable if you think they are safe. (Not likely to make things get worse.) It seems that some bug fixes have gone into stable recently. Can this bug be closed now?
Closing; please reopen if that is incorrect.