[Bf-committers] Support displaying of non-ASCII filename

[Yaohua Xiong]

Hi Rob,

> I don't think it will work. As I discovered when developing the patch "[#21836] There are problems running blender using UNC paths" there are more places where blender uses file and path names than just winstuff.c and they are not wide character or even utf-8 compatible.

I expected there will be more work to do too. But I think if we stick
to utf8 as internal encoding it will not cause too many problems,
because utf8 encoding is almost "compatible" with ASCII encoding.

> IMHO A better solution until either windows natively handles utf-8 encoded filenames or blender natively uses wide characters is to use Windows multi-byte character strings in the file and path handling routines - this shouldn't require a great amount of effort. I'm willing to do this but I want to wait until [#21836] There are problems running blender using UNC paths is accepted before I do.

I've considered this route, it's indeed simpler than the utf8 way.
Based on my experience, blender already works well with localized
windows multi-byte character, the only thing we really need to do is
modifying blenfont to do find glyphs based on that. The problem is we
cannot share files in different encoding with almost the same glyphs
like simplified Chinese, traditional Chinese, Japanese, Korean... not
quite satisfying.

Best regards,
Yaohua Xiong

-- 
Yaohua Xiong

Traffic and Transportation Engineering College, Tongji Univ.
Cao An Road 4800#, Jia Ding District, Shanghai,  China