Searched refs:forgiving (Results 1 – 13 of 13) sorted by relevance
114 OPJ_BOOL forgiving, in opj_sparse_array_int32_read_or_write() argument122 return forgiving; in opj_sparse_array_int32_read_or_write()319 OPJ_BOOL forgiving) in opj_sparse_array_int32_read() argument326 forgiving, in opj_sparse_array_int32_read()338 OPJ_BOOL forgiving) in opj_sparse_array_int32_write() argument344 forgiving, in opj_sparse_array_int32_write()
110 OPJ_BOOL forgiving);137 OPJ_BOOL forgiving);
877 email header decoding is now forgiving if an RFC2047 encoded word encoded in
665 The earlier versions of these methods were more forgiving because they used an673 Some of the functions in the :mod:`socket` module are still forgiving in this
1112 - Be "forgiving" when interpreting the maxp table version field:
1529 - Be "forgiving" when interpreting the maxp table version field:
12565 - Issue #3196: email header decoding is now forgiving if an RFC2047 encoded word
9200 $x{forgiving → forgɪvɪŋ ; # fordʒɑɪvɪŋ
61965 forgiving %33456 fɔrgˈɪvɪŋ, fərgˈɪvɪŋ
73425 forgiving %24626 for-, fɔrgˈɪvɪŋ, fərgˈɪvɪŋ