Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 59804

Summary: Default font for text editor cannot display Japanese characters
Product: [Eclipse Project] Platform Reporter: Paul Elder <pelder.eclipse>
Component: UIAssignee: Tod Creasey <Tod_Creasey>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Paul Elder CLA 2004-04-23 13:02:47 EDT 
This was discovered using Japanese Windows, but can be reproduced using English
Windows with Japanse fonts installed.

The default font for editors (as specified in
Window->Preferences->Workbench->Colors and Fonts, with Category set to
"Uncategorized") is "Courier New-regular-10". This font does not display
Japanese characters; instead, block characters are displayed.
Comment 1 Tod Creasey CLA 2004-04-26 10:06:50 EDT 
Which build are you working on? This was an issue in the StyledText in M8 but 
has since been fixed. See Bug 56915
Comment 2 Paul Elder CLA 2004-04-26 11:06:11 EDT 
I am using the WSWB M8 derivative (wswb-30M8-200403311308).

This is definitely a font choice problem. Using preferences to change to a font
that supports Japanese scripts allows the text to display correctly.

In addition, I can cut & paste the block characters to Notepad, and they display
correctly. (So the editor has the correct character codes.)

Finally, if I save & reload the file, cut & paste (or font change) both reveal
the correct characters. (So persisting the character data to a file is correct.)

This appears to be a duplicate of Bug 56915.
Comment 3 Steve Northover CLA 2004-04-28 12:45:17 EDT 
This has nothing to do with SWT.  Eclipse needs to choose a font that is 
capable of displaying these characters.  A good font was chosen in the past.  
Did something change?
Comment 4 Tod Creasey CLA 2004-04-29 12:58:30 EDT 
This font has always been Courier - this was a regression from 3.0.

it is a dup of Bug 56915

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