After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 354712 - wrongly rendering the combining character in Japanese
wrongly rendering the combining character in Japanese
Status: RESOLVED DUPLICATE of bug 139950
Product: pango
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2006-09-07 02:08 UTC by LingNing Zhang
Modified: 2006-09-07 12:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description LingNing Zhang 2006-09-07 02:08:55 UTC
Please describe the problem:
Description of problem:
OS X deals with the (semi-)voiced consonant using the combining (semi-)voiced
sound mark(U+3099 and U+309A) in Japanese instead of already combined characters. 
So it may be likely to see such documents on even Linux Desktop so that users
may wants to exchange the files between both environments.
When it appears in text, Pango can deal with it as one character for editing.
but obviously it's too larger and it looks like two characters are there then.

Version-Release number of selected component (if applicable):
pango-1.14.0-2

How reproducible:
always

Steps to Reproduce:
1.open a sample file on gedit say
2.
3.
  
Actual results:
looks like a screenshot

Expected results:
should be rendered similarly with the combined character

Additional info:



Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 LingNing Zhang 2006-09-07 02:09:43 UTC
screenshot:
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=134370
Comment 2 LingNing Zhang 2006-09-07 02:10:28 UTC
testcase
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=134371
Comment 3 Owen Taylor 2006-09-07 12:18:25 UTC
I don't think a special-case-Japanese solution here makes sense; this
is just the general problem with handling decomposed input text.


*** This bug has been marked as a duplicate of 139950 ***