Bug 26604 - lang=xx and lang=xx-yy behave inconsistently
Summary: lang=xx and lang=xx-yy behave inconsistently
Status: RESOLVED DUPLICATE of bug 35118
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.8
Hardware: Other All
: medium normal
Assignee: Keith Packard
QA Contact: Behdad Esfahbod
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-17 02:38 UTC by Jens Petersen
Modified: 2011-06-17 03:24 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Jens Petersen 2010-02-17 02:38:19 UTC 
Current fontconfig seems to behalf consistently for testing lang=xx
compared to lang=xx-yy.

There are some examples and discussion in
https://bugzilla.redhat.com/show_bug.cgi?id=546490

and also some discussion here:
http://lists.freedesktop.org/archives/fontconfig/2009-November/thread.html#3275
Comment 1 Akira TAGOH 2010-07-07 22:50:12 UTC 
Though I attached a patch recently to modify the langset and the charset at Bug#23758, that may be possible to get this resolved by adding some rules to update the lang in the query pattern like:

<match>
  <test name="lang">
    <string>ja</string>
  </test>
  <edit name="lang" mode="append" binding="same">
    <langset>ja-jp</langset>
  </edit>
</match>
<match>
  <test name="lang">
    <string>ja-jp</string>
  </test>
  <edit name="lang" mode="append" binding="same">
    <langset>ja</langset>
  </edit>
</match>

That could be possible to be generated at the build time and give a higher priority to that config perhaps.

How does it look?
Comment 2 Behdad Esfahbod 2011-03-14 15:43:55 UTC 
Is this a dupe of bug 35118?
Comment 3 Akira TAGOH 2011-03-14 18:00:45 UTC 
(In reply to comment #2)
> Is this a dupe of bug 35118?

I think so
Comment 4 Akira TAGOH 2011-06-17 03:24:37 UTC 

*** This bug has been marked as a duplicate of bug 35118 ***

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.