Bug 25458 [Font] DBCS support: new SWT API
Last Friday we have included a new API in Font: public Font(Device device, FontData[] fds) { In order to have a more appropriate behavior on DBCS platforms Eclipse/UI should start using this API. Anyway, the best police still is never change the default font in the widget if you don't need to. (this new API is going to make difference in Eclipse/Motif only)
bundles/org.eclipse.jface/src/org/eclipse/jface/resource/FontRegistry.java
if(Arrays.equals(existing,fontData))
		return;
		
	Font oldFont = (Font)stringToFont.remove(symbolicName);
	stringToFontData.put(symbolicName, fontData);
	if(update)
		fireFontMappingChanged(symbolicName);
	if (oldFont == defaultFont())
		return;
	if (oldFont != null )
		oldFont.dispose();
}
/**
 * Reads the resource bundle.  This puts FontData[] objects
 * in the mapping table.  These will lazily be turned into
 * real Font objects when requested.
 */
private void readResourceBundle(ResourceBundle bundle,String bundleName) throws MissingResourceException {
	Enumeration keys = bundle.getKeys();
	while (keys.hasMoreElements()) {
		String key = (String) keys.nextElement();
		int pos = key.lastIndexOf('.');
		if (pos == -1) {
			stringToFontData.put(key, new FontData[] {
	            makeFontData(bundle.getString(key))});
		} else {
			String name = key.substring(0, pos);
			int i = 0;
			try {
				i = Integer.parseInt(key.substring(pos + 1));