Bug 386367 - Font: support of OpenType localization features
Summary: Font: support of OpenType localization features
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.2   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-01 03:21 EDT by Andre Saibel CLA
Modified: 2019-11-28 05:44 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Saibel CLA 2012-08-01 03:21:53 EDT
The acceptance of a UI depends on the culturally respectful representation of characters for the target language area.

OpenType font format specifies some 'features' to improve internationalization and localization abilities of fonts. First of all there's the 'locl' feature that enables glyphs to have different (localized) forms. 

Many fonts are aware of these features and contain variants for latin, cyrillic, greek, arabic/persian/urdu and -most of all- CJK letters/glyphs. 
So it stands to reason to equip an application with a single high-quality font that is sufficient for the whole world.

Microsoft, Linux/FreeType/Pango and Mac OS X support these features natively, too.
(Microsoft: http://www.microsoft.com/typography/otspec/features_ko.htm , Pango: http://www.pango.org/ScriptGallery )
I do not know much about implementation details yet, just know that it's the matter of the application to use these capabilities.

The possibility to "switch" the representation of the texts in an UI would be great for org.eclipse.swt.graphics.Font.
Comment 1 Lars Vogel CLA 2019-11-27 07:48:57 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.