Bug 92776 - [patch] Allow fontconfig to use 3 components in locales
Summary: [patch] Allow fontconfig to use 3 components in locales
Status: RESOLVED MOVED
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.11
Hardware: Other FreeBSD
: medium normal
Assignee: fontconfig-bugs
QA Contact: Behdad Esfahbod
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-02 14:08 UTC by Koop Mast
Modified: 2018-08-20 21:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Support 3 component locales (2.13 KB, patch)
2015-11-02 14:08 UTC, Koop Mast
Details | Splinter Review

Description Koop Mast 2015-11-02 14:08:03 UTC
Created attachment 119343 [details] [review]
Support 3 component locales

Linux only supports locales with 2 components while POSIX supports
locales with 3 components.

DragonFly and FreeBSD both follow POSIX, which causes fontconfig to
give the following warning:

% env LC_CTYPE=sr_Cyrl_RS.UTF-8 leafpad
Fontconfig warning: ignoring sr_Cyrl_RS.UTF-8: not a valid region tag

For more information about the POSIX documentation:
http://tools.ietf.org/html/bcp47
Chapter 2.1.1 goes over formatting and Appendix-A has more examples.
Comment 1 Akira TAGOH 2015-11-04 02:58:23 UTC
Do you have any pointers that explains POSIX supports BCP47 as a locale representation?
The URL you pointed out is to explan what BCP47 is. it isn't same to what I want to know. AFAIK the POSIX locale system follows similar to BCP47 but has different definition for modifiers say. usually script representation goes into a modifier prefixed by @.
Comment 2 Koop Mast 2015-11-19 12:23:33 UTC
cldr is the authority and that's how they refer to locales and repeat examples of 3-group locales

2 component isn't good enough: serbia has latin and cyrillic based languages, you can't represent both with only 2 components.

The cldr website has a BCP47 section.

http://cldr.unicode.org/ (Unicode Common Locale Data Repository)
http://unicode.org/Public/cldr/2.0.1/ (cldr files)
Comment 3 Akira TAGOH 2015-11-20 02:10:36 UTC
Those two could be represented to sr_RS@latin and sr_RS@cyrilic in glibc say. it isn't entirely true. anyway, just wonder if there are any pointers as a reference that POSIX really supports that style.
Comment 4 GitLab Migration User 2018-08-20 21:46:27 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/49.


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.