Community
Participate
Working Groups
- WindowsXP(English) + MUI + GB18030 patch - locale china(PRC) - WSWB V2 + NLS fragments for WSWB Default text font is NOT GB18030 enabled font, so that editor can't show GB18030 character by default. When I change text font from Workbench->Fonts page, it can show the character. However, it would be better if Eclipse could detect the existance of GB18030 code page support and its font, then choose appropriate fonts. Since WindowsXP support GB18030 code page by default even if it is a English version, but it doesn't have GB18030 font until user install GB18030 support kit.
The default fonts are defined by the jfacefonts.properties file for the locale in which you are using. The java.util.Locale class does not have encoding support so we cannot specify a fonts property file that does. However in the case of simplified Chinese encoding is an interesting determinator of font to use - we should consider this as part of the 2.1 encoding review. Currently you can select a more appropriate font using the fonts preference page. Renaming PR and adding Text component owner to the cc list.
Encoding support is really only required in the properties file for the GB18030 code page on Simplified Chinese. The jfacefonts.properties for Simplified Chinese should use GB18030 fonts - it is not required as a general solution.
GB18030 fonts don't exist on Simplefied Chinese Windows 2000 nor Windows XP by default. User explicitly needs to install GB18030 enablement kit. Does this solution work with Simplefied Chinese system which doesn't have GB18030 fonts?
Please let me know following information: - Which fonts are used in jfacefonts.properties for Simplified Chinese? GB18030 enabled fonts or other? - If the fonts are GB18030 enabled fonts, what happen if the OS (W2K or WinXP) doesn't have the fonts, which is default config of W2K and WinXP?
You can find the font files in the jfacefonts.properties in files in the fragment for org.eclipse.jface. The current (2.1) fragments list the following for Simplified CHinese org.eclipse.jface.bannerfont.0=\u5B8B\u4F53-bold-9 org.eclipse.jface.headerfont.0=\u5B8B\u4F53-bold-12 org.eclipse.jface.textfont.0=\u5B8B\u4F53-regular-10 org.eclipse.jface.textfont.1=Courier-regular-10 org.eclipse.jface.textfont.2=Lucida Console-regular-9 Please note that the Eclipse team does not choose this fonts. If you have some better suggestions please append them to this report and we can see about getting them entered into the fragments.
If you refer to the Simplified Chinese translation, the Jfacefont.properties is set to use the Simplified Chinese OS default font and not the GB18030 font. The reason is because user will only get the GB18030 font when applying the GB18030 support kit. Most users do not have the GB18030 support kit applied to their OS. The ones who do just need to pick up the available GB18030 font. It would be better if the code can pick up the "default font" set in the OS (this font could be either regular Chinese font or GB18030 set previously by the users)but this is not how the code works today.
This would mean that Simplifed Chinese works differently than any other platform and would require special code for this case. This is not an adequate general solution regardless as we have similar issues in other configurations - hence this problem report. The best short term solution is to find a set of fonts that exist on both the out of the box XP/2000 and in GB18030 - the user can always change them if required.
GB18030 char set is a "superset" of the Simplified Chinese char set. It contains new glyphs which are just being introduced laterly to the computer world (similar to the case of the Euro currency). The problem would be resolved if GB18030 font is being used as "Microsoft windows default font". Until then, we need to use the "common" char set of GB18030/regular Simplified Chinese, which is the regular Simplified Chinese char set.
Not for 3.0
Reopening now that 3.0 has shipped
We are moving away from this feature generally due to this an other issues with this solution. This is something that should be considered as part of Theme support.
