| Summary: | ks_IN and sd_IN devanagari locale names are spelled incorrectly, different from glibc, therefore they don’t work | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Mike FABIAN <mike.fabian> | ||||
| Component: | Lib/Xlib (data) | Assignee: | Xorg Project Team <xorg-team> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | cloos | ||||
| Version: | git | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Mike FABIAN
2014-02-19 18:06:28 UTC
This problem still exists in current git master: mfabian@ari:/local/mfabian/src/xorg/libX11/nls (master) $ grep sd_IN *.pre compose.dir.pre:en_US.UTF-8/Compose: sd_IN.UTF-8 compose.dir.pre:en_US.UTF-8/Compose: sd_IN@devanagari.UTF-8 locale.alias.pre:sd: sd_IN.UTF-8 locale.alias.pre:sd_IN.utf8: sd_IN.UTF-8 locale.alias.pre:sd@devanagari: sd_IN@devanagari.UTF-8 locale.alias.pre:sd_IN@devanagari: sd_IN@devanagari.UTF-8 locale.alias.pre:sd_IN@devanagari.utf8: sd_IN@devanagari.UTF-8 locale.dir.pre:en_US.UTF-8/XLC_LOCALE: sd_IN.UTF-8 locale.dir.pre:en_US.UTF-8/XLC_LOCALE: sd_IN@devanagari.UTF-8 mfabian@ari:/local/mfabian/src/xorg/libX11/nls (master) $ grep ks_IN *.pre compose.dir.pre:en_US.UTF-8/Compose: ks_IN.UTF-8 compose.dir.pre:en_US.UTF-8/Compose: ks_IN@devanagari.UTF-8 locale.alias.pre:ks: ks_IN.UTF-8 locale.alias.pre:ks_IN: ks_IN.UTF-8 locale.alias.pre:ks_IN.utf8: ks_IN.UTF-8 locale.alias.pre:ks_IN@devanagari: ks_IN@devanagari.UTF-8 locale.alias.pre:ks_IN@devanagari.utf8: ks_IN@devanagari.UTF-8 locale.dir.pre:en_US.UTF-8/XLC_LOCALE: ks_IN.UTF-8 locale.dir.pre:en_US.UTF-8/XLC_LOCALE: ks_IN@devanagari.UTF-8 mfabian@ari:/local/mfabian/src/xorg/libX11/nls (master) $ Thanks. Pushed as 748d47e69f5c12d8557d56a8a8ec166588da7b93. |
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.