> > 1. use platform specific unicode version of file operation API in the
> > implementation of BLI_fileops and encode the (probably) wchar
> > filename into utf8.
>
> For Windows file operations we need to change “winstuff” to use
> FindFirstFileW
> and FindNextFileW instead of the ansi versions.
On Thu, Apr 22, 2010 at 3:37 AM, Yaohua Xiong wrote:
> > In general, the user set the locale or the program get it from some
> > environment variable.
> >
> > Blender already support this, so maybe what we need to do is change the
> > locale and convert the string to utf8 and see what happen then
Le 22 avr. 2010 à 08:52, Ignacio Fernandez Moreno a écrit :
> Hi all,
>
> I've been researching too. My aproach was trying to get input in utf/unicode
> and this is what i've found:
>
> - Ghost gets every input as an ascci char, you can see this in
> GHOST_TEventKeyData, and GHOST_EventKey. It
Hi,
I just added a patch in the tracker (#22116) that adds support for the Lab
color space in blender's compositor.
Husam
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Matt,
Glad this is fixed too. Just to let you know that the bug definitely happened
on builds without fastmath too.
loopduplicate
--
Comment By: Matt Ebb (broken)
Date: 2010-04-23 11:42
Message:
Thanks a bunch for finding that, Charlie! Maybe it's some impr
Hi Damien,
Those are good news, Can you add that to the patch i put before?
The two character issue has to do with the so called "dead keys" (keys that
act as modifiers to the next key pressed).
For windows i made a one line patch to prevent filling the key event with
ascii data in those cases.
