[Bug 671131] New: Hangul Jamo render as U+00xx boxes and produce valgrind errors
bugzilla at redhat.com
bugzilla at redhat.com
Thu Jan 20 14:01:22 UTC 2011
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Hangul Jamo render as U+00xx boxes and produce valgrind errors
https://bugzilla.redhat.com/show_bug.cgi?id=671131
Summary: Hangul Jamo render as U+00xx boxes and produce
valgrind errors
Product: Fedora
Version: 14
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: pango
AssignedTo: behdad at fedoraproject.org
ReportedBy: matt at mattmccutchen.net
QAContact: extras-qa at fedoraproject.org
CC: behdad at fedoraproject.org,
fonts-bugs at lists.fedoraproject.org
Classification: Fedora
Created attachment 474463
--> https://bugzilla.redhat.com/attachment.cgi?id=474463
Valgrind log from gucharmap
Description of problem:
When I look at the Hangul Jamo (U+1100 through U+11FF) in gucharmap, many of
them render as boxes containing numbers between 0000 and 00FF. Dragging across
them with the right mouse button sometimes causes the specific numbers to
change. I re-ran gucharmap under valgrind and got lots of errors. I get
similar behavior by entering a few jamo in gedit with Ctrl-Shift-U, so I don't
think the bug is with gucharmap. I may be missing a font, but in that case
pango should just show boxes with the 11xx numbers instead of behaving in this
bizarre way.
Version-Release number of selected component (if applicable):
pango-1.28.1-4.fc14
How reproducible:
Always
Steps to Reproduce:
1. valgrind gucharmap
2. Choose View -> By Unicode Block.
3. Choose the Hangul Jamo block.
4. Right-drag across the characters.
Actual results:
Some boxes containing 00xx which change unpredictably, and valgrind errors.
Expected results:
Correct rendering or correct numerical boxes, with no valgrind errors.
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the fonts-bugs
mailing list