[Bf-committers] why our own UTF functions?

[joe]

To clarify, there can be implementation differences with utf8
converter functions, especially in the assumptions they make about the
encoding of multibyte strings.

On Sun, Jul 5, 2009 at 9:13 PM, joe<joeedh at gmail.com> wrote:
> These may not work well on all platforms.
>
> Joe
>
> On Sat, Jul 4, 2009 at 11:04 PM, Campbell Barton<ideasman42 at gmail.com> wrote:
>> Since python3 uses unicode strings in some places I looked into
>> conversion and found that we have our own functions to deal with this,
>> but there are also system functions for it.
>>
>> Heres some functions that could be removed in font.c, using system
>> functions instead.
>> - utf8towchar with mbstowcs
>> - wcs2utf8s with wcstombs
>> - utf8slen with mblen
>> - chtoutf8 with mbtowc
>>
>> any reason blender includes its own?
>> --
>> - Campbell
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
>