Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337287 - Unable to render GB18030 G1 characters (\u1820\u0F00) on StyledText widget
Summary: Unable to render GB18030 G1 characters (\u1820\u0F00) on StyledText widget
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-16 04:43 EST by Gary Tu CLA
Modified: 2019-11-14 03:32 EST (History)
2 users (show)

See Also:


Attachments
Sample Code (1.38 KB, text/plain)
2011-02-16 04:45 EST, Gary Tu CLA
no flags Details
Screenshot (5.68 KB, image/png)
2011-02-16 04:47 EST, Gary Tu CLA
no flags Details
G1 in 4.2 M6 (2.81 KB, image/png)
2012-05-07 03:34 EDT, Julia Zhou CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Tu CLA 2011-02-16 04:43:36 EST
Build Identifier: I20100608-0911

The StyledText widget is unable to render 2 of GB18030 G1 characters as described in https://labweb.torolab.ibm.com/gcoc/documents/gvtguide/testareas/DIH-UUN-010.htm unless we explicitly set the font to SimSun-18030. However it works on Text widget.

Reproducible: Always

Steps to Reproduce:
1. Enable GB18030 support as http://msdn.microsoft.com/en-us/library/aa578128.aspx
2. Besides add SimSum18030 font linking to Tahoma and Arial, also add Courier & Courier New to link to SimSum18030
3. Run the sample program attached and you can find those 2 characters (\u1820\u0F00) are rendered as square but it render successfully on the Text widget.
Comment 1 Gary Tu CLA 2011-02-16 04:45:01 EST
Created attachment 189075 [details]
Sample Code
Comment 2 Gary Tu CLA 2011-02-16 04:47:04 EST
Created attachment 189076 [details]
Screenshot
Comment 3 Felipe Heidrich CLA 2011-02-18 14:50:41 EST
On my machines

Windows 7 - all chars are renderer on both widgets

Xp - Text has 5 missing glyphs, StyledText has 1
Xp using simsun-18030 font - all chars are rendere on both widgets.
Comment 4 wanglei CLA 2011-03-22 09:31:03 EDT
Hi Felipe, I tried this on WinXP platform following the steps below:
Install GB18030 support package
1. Open Control Panel -> Regional and Language Options, on Languages tab, check Install files for East Asian languages.
2. Install the GB18030 support package http://go.microsoft.com/fwlink/?LinkID=26235.
Enable GB18030 font linking
1. Open the windows register
2. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink].
3. Double-click Tahoma.
4. Add "SimSun18030.ttc,SimSun-18030", in a new line, in the edit box.
5. Double-click Arial.
6. Add "SimSun18030.ttc,SimSun-18030", in a new line, in the edit box.
7. Restart the computer.
So we didn't specify the font to use SimSum-18030 explicitly in the code, and it's easy to reproduce with the sample code above on both WinXP and Win2003 platform, please try again. Thanks a lot.
Comment 5 Felipe Heidrich CLA 2011-03-29 10:23:45 EDT
My XP is really old I have already installed those packages before.
Wanglei, after you followed the steps in your previous message, you got the text showing correctly in Text (all glyphs) but not in StyledText (missing glyphs) ?
Comment 6 wanglei CLA 2011-03-29 10:35:39 EDT
(In reply to comment #5)
> My XP is really old I have already installed those packages before.
> Wanglei, after you followed the steps in your previous message, you got the
> text showing correctly in Text (all glyphs) but not in StyledText (missing
> glyphs) ?

Yes, it works on Text widget, but not work for StyledText.
Comment 7 Julia Zhou CLA 2012-05-07 03:34:57 EDT
Created attachment 215164 [details]
G1 in 4.2 M6

Mongolian/Tibetan characters are displayed as square marks
Tested on WinXP platform, build 4.2 M6.
Comment 8 Lars Vogel CLA 2019-11-14 03:32:06 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.