[Fontconfig] fontconfig crash for special bdf font
Akira TAGOH
akira at tagoh.org
Wed Jan 29 23:07:55 PST 2014
On Wed, Jan 29, 2014 at 4:09 PM, Werner LEMBERG <wl at gnu.org> wrote:
> I see two possibilities on the FreeType side:
>
> 1. Document that NULL is a valid return value for `atom',
> corresponding to a property present in the font with a zero
> string as an argument – the return value
> `FT_Err_Invalid_Argument' of function `FT_Get_BDF_Property'
> indicates that the searched property isn't present in the font.
So FT_Get_BDF_Property will returns FT_Err_INvalid_Argument in this
case? or returning NULL means it's there but it was just an empty
string?
Anyway mentioning more details for the above thing in the doc sounds good to me.
>
> 2. Change the code back to return an empty string.
>
> I tend to solution 1, but I'm open to other suggestions.
>
>
> Werner
--
Akira TAGOH
More information about the Fontconfig
mailing list