Am 25.07.2012 17:40, schrieb Keith Packard:
reassign 662931 fontconfig 2.9.0-5
[...]
Can I get someone to confirm that this is fixed in 2.9.0-5?
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
Fabian Greffrath writes:
> 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:
>> I can confirm that fc-match returns the Bulgarian string, but this strikes me
>> as an fc-match bug.
>
> In
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:
I can confirm that fc-match returns the Bulgarian string, but this strikes me
as an fc-match bug.
Indeed it is. It has been filed two years ag
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
Package: ttf-freefont
Version: 20100919-1
Severity: minor
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" "получерен"
5 matches
Mail list logo