#662931 ttf-freefont: Reports variant in Bulgarian language

Package:
fontconfig
Source:
fontconfig
Description:
generic font configuration library - support binaries
Submitter:
Date:
2015-05-18 11:27:46 UTC
Severity:
minor
#662931#5
Date:
2012-03-07 11:39:48 UTC
From:
To:
Hi,

currently, the fonts in ttf-freefont report their variant (i.e. bold, italic,
etc.) in Bulgarian language, e.g.
$ fc-match FreeMono
FreeMono.ttf: "FreeMono" "нормален"
$ fc-match FreeMono:bold
FreeMonoBold.ttf: "FreeMono" "получерен"

Please note that this is independent of the locale set on the system.
Curiously, there is also a German translation of these strings present in the
sfd source file, but for whatever reason, the Bulgarian ones is prefered.

 - Fabian
#662931#10
Date:
2012-05-04 08:34:39 UTC
From:
To:
Hi Fabian,

I happened to be looking over the Debian bugs, and noticed this new report.

I can confirm that fc-match returns the Bulgarian string, but this strikes me
as an fc-match bug.

This comes from a standard table of strings in the font, indexed by language.
There is no further logic in the font, and I just double-checked: the
strings all
seem to be indexed correctly.

This works properly for FreeMono with most software (e.g. on systems set
up for German, the face names appear in German)

My only clue is, fc-list FreeMono lists the Bulgarian string first
*after* the main
"en" string.  (That's odd -- wouldn't Basque come first?  Aha. It's sorting by
ISO 639-3 language code, for which Basque is 'eus', and Bulgarian is 'bul'.)
This is an fc-cache bug.

(Please report further FreeFont related issues to
https://savannah.gnu.org/bugs/?group=freefont)
#662931#15
Date:
2012-06-08 08:08:08 UTC
From:
To:
reassign 662931 fontconfig 2.9.0-5
forwarded 662931 https://bugs.freedesktop.org/show_bug.cgi?id=27765
thanks

Am 04.05.2012 10:34, schrieb Steve White:

Indeed it is. It has been filed two years ago in the fontconfig bug
tracker and got recently fixed by the following commit:
http://cgit.freedesktop.org/fontconfig/commit/?id=7587d1c99d9476b6dd4dbe523c0204da700fed8d

  - Fabian
#662931#30
Date:
2012-07-25 15:40:15 UTC
From:
To:
Fabian Greffrath <fabian@greffrath.com> writes:

Can I get someone to confirm that this is fixed in 2.9.0-5?
#662931#35
Date:
2012-07-26 09:06:12 UTC
From:
To:
Am 25.07.2012 17:40, schrieb Keith Packard:

The bug has been reassigned to fontconfig 2.9.0-5, i.e. it has been
marked found in this specific version - not fixed. However, I can
confirm that the bug is still present in the fontconfig package
currently in unstable.

  - Fabian