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
* There must be an SWT Display created in the current 
 * thread before calling this method.
 * </p>
 */
public FontRegistry() {
	Display display = Display.getCurrent();
	Assert.isNotNull(display);
	hookDisplayDispose(display);
}
/**
 * Creates a font registry and initializes its content from
 * a property file.
 * <p>
 * There must be an SWT Display created in the current 
 * thread before calling this method.
 * </p>
 * <p>
 * The OS name (retrieved using <code>System.getProperty("os.name")</code>)
 * is converted to lowercase, purged of whitespace, and appended 
 * as suffix (separated by an underscore <code>'_'</code>) to the given 
 * location string to yield the base name of a resource bundle
 * acceptable to <code>ResourceBundle.getBundle</code>.
 * The standard Java resource bundle mechanism is then used to locate
 * and open the appropriate properties file, taking into account
 * locale specific variations.
 * </p>
 * <p>
 * For example, on the Windows 2000 operating system the location string
 * <code>"com.example.myapp.Fonts"</code> yields the base name 
 * <code>"com.example.myapp.Fonts_windows2000"</code>. For the US English locale,