Bug 1787 - RFE: Port the XLC_LOCALE locales from Solaris to Xorg
Summary: RFE: Port the XLC_LOCALE locales from Solaris to Xorg
Status: CLOSED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: * Other (show other bugs)
Version: git
Hardware: All All
: high enhancement
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-04 22:58 UTC by Roland Mainz
Modified: 2011-10-15 16:23 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Roland Mainz 2004-11-04 22:58:56 UTC
RFE: Port the XLC_LOCALE locales from Solaris to Xorg. It seems that Solaris has
much more fontset/encoding mappings (just compare
/usr/openwin/lib/locale/en_US.UTF-8/XLC_LOCALE vs. xc/nls/XLC_LOCALE/en_US.UTF-8
) in XLC_LOCALE than the current Xorg versions of those files.
It would be nice if this could be ported to Xorg 

Notes:
1. I added support for Sun-specific font encodings like suneu-greek or
sun.unicode.india-0 so they can be included in the mappings, too

2. I added an "ascii-0" font encoding with bug 1703 (`Lots of "FreeType:
couldn't find encoding 'ascii-0'" warnings`) - it may be nice to put that in
front of the 16bit font encodings which have ASCII as their base (=positions
0-127) - this may save some time when only ASCII glyphs are needed as only the
ASCII parts need to be loaded as 8bit font (instead of loading a fully-qualified
16bit font).

3. xc/nls/XLC_LOCALE/zh_CN.gb18030 misses the GBK1988.1989-0 entry present in
the Solaris version (/usr/openwin/lib/locale/zh_CN.GB18030/XLC_LOCALE)

4. Solaris has a special tag called "load_option delay_nocheck" - what exactly
is that ? Is this worth being ported to Xorg ?
Comment 1 Roland Mainz 2005-01-10 04:04:16 UTC
Steve/Ienup:
Any idea who can work on that for X11R6.9.0, please ?
Comment 2 Daniel Stone 2006-04-04 23:46:11 UTC
the x.org bz is not a place to track requests to sun


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.