was starting to look at it again a few days ago.
Thank you for reminding.
On Thu, Apr 30, 2015 at 12:30 AM, Nicolas Mailhot <nicolas.mailhot@xxxxxxxxxxx> wrote:
Le Mer 29 avril 2015 16:43, Raimund Steger a écrit :
>
> On Wed, April 29, 2015 16:21, Raimund Steger wrote:
>>
>> On Wed, April 29, 2015 15:03, Urs Liska wrote:
>>> [...]
>>
>>> Or otherwise I'd like to know about a way to have fontconfig return
>>> some
>>> "failure condition" instead of a replacement if a font isn't matched.
>>
>> The problem with this is that fontconfig has only a fuzzy concept of
>> equality. Most people would think of font equality as "family name
>> equality". If that's what you want, just compare FC_FAMILY and/or
>
> Ah, before I forget to mention that *again*, there are also Microsoft's
> font name normalization rules which are not currently implemented by
> fontconfig but have at times been hinted at by Nicolas ;)
And it is here:
http://blogs.msdn.com/b/text/archive/2007/04/23/wpf-font-selection-model.aspx
There is no value to normalisation rules if everyone invents its own,
please use those since they are already documented and implemented in the
closed software world.
Regards,
--
Nicolas Mailhot
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig
Akira TAGOH
_______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
