[libGD] #42 [Comment added] GD can't display characters with unicode references over 7 digits (Attachment added)
| From: | gd-bugs at lists dot php dot net | Date: | Thu, 04 Nov 2010 16:23:05 +0000 |
| Subject: | [libGD] #42 [Comment added] GD can't display characters with unicode references over 7 digits (Attachment added) | ||
| Groups: | php.gd.bugs | ||
| Request: | Send a blank email to php-gd-bugs+get-796@lists.php.net to get a copy of this message | ||
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#42 - GD can't display characters with unicode references over 7 digits
User who did this - Adam Harvey (LawnGnome)
----------
An updated version (no changes other than unbitrotting) of Pierre's patch from 2007 against the
current HEAD is attached as gdft_fix_selectcharmap.patch. It seems to do the right thing for astral
characters, but I suspect it'll fail badly if Big5 or SJIS encodings are requested, since
it's hard-coded at present to try to select a charmap with FT_ENCODING_UNICODE, rather than
using whatever's requested.
I've also hacked up my own, more minimal patch (attached as gdft_astral_minimal.patch), which
(hopefully) maintains the current behaviour when Big5 or SJIS encoding is requested, but hacks up
the existing UTF-8 function to add four byte UTF-8 codepoint support rather than doing it properly.
Since I have neither a Big5 nor SJIS font to test this with, I can't guarantee that it's
right, but I can't see why it wouldn't be.
I suspect the right answer is probably a combination of the two -- that is, using Pierre's
rewritten UTF-8 handling code with my changes to gdImageStringFTEx -- but it's late and
I'm going to bed, so let's just consider the two patches for now and I'll think about
it more next time I have a free evening. :)
----------
There was one or more files attached to this comment.
More information can be found at the following URL:
http://bugs.libgd.org/?do=details&task_id=42#comment656
You are receiving this message because you have requested it from the Flyspray bugtracking system.
If you did not expect this message or don't want to receive mails in future, you can change
your notification settings at the URL shown above.