Bug 17311

Summary:	Add a FC_LOCALE_LANG element
Product:	fontconfig	Reporter:	Behdad Esfahbod <freedesktop>
Component:	library	Assignee:	fontconfig-bugs
Status:	RESOLVED MOVED	QA Contact:	Behdad Esfahbod <freedesktop>
Severity:	enhancement
Priority:	medium	CC:	akira, fonts-bugs, freedesktop
Version:	2.4
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Behdad Esfahbod 2008-08-26 09:28:29 UTC

This would be quite similar to FC_LANG, except that it holds the default language of the locale, not the language we are looking for fonts for.

The idea is that an application (Pango) looking for a font to render English always passes en as lang.  However, in CJK locales, it may be desirable to select the same font for Latin as well as CJK.  With the proposed element, a conf file can check whether FC_LOCALE_LANG is CJK and in that case, add the CJK font as the single preferred font.  All this without affecting the case of not running under a CJK locale.

Comment 1 Akira TAGOH 2012-04-02 00:25:44 UTC

There are some objections to behave like that:

https://bugzilla.redhat.com/show_bug.cgi?id=485566

That's opposed to this idea. that may be good if it's configurable with some option but not doing something with the huge rules.

FYI anyway.

Comment 2 Behdad Esfahbod 2012-04-02 13:48:45 UTC

Well, what I'm suggesting by itself doesn't change anything.  It just makes it possible for configurations to achieve effects that are currently not possible.

Comment 3 Akira TAGOH 2012-04-02 20:15:56 UTC

Thanks. maybe current FC_LANG object may causes the confusion. it could be replaced with "script" or something like that. it shouldn't be puzzled by the sets of the language and the territory. though we have to have the mapping table to the language for fonts then. or we could guess the language from the aggregation of the scripts and give a lower score than picking up from the mapping table for fallback.

This is an idea I'm pondering in fontconfig-ng with BCP47 support since it might breaks the backward compatibility.

Comment 4 GitLab Migration User 2018-08-20 21:46:20 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/47.

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.