2004-09-14, 16:44
(yuvalt @ sep. 14 2004,07:17 Wrote:most xbox kernel functions are ansi only. i think it is almost impossible to change xbmc to compile with unicode defined. but why don't treat every string as utf-8 string, it is ansi compatible and only need to convert back to unicode before displaying it.(droopy @ sep. 13 2004,22:19 Wrote:i noted that smbdirectory.cpp unconditionally call g_charsetconverter.utf8tostringcharset(dirent->name, strfile), which convert unicode file name to native encoding, the file name then will be converted back from native encoding to unicode before it is displayed, this does not make much sense.droopy,
also xdk suggests using ttf font should be avoided since it degrades performance a lot. anyway bitmap font is for console and ttf font is for office application.
since xbmc does not use wchar_t throughout the code we decided to use this method. if you are willing to volunteer and change all the code, add #define unicode and make it work, i'd be happy.
the xdk does not say that ttf should be avoided but say that it less performant. in tests i did, it consumes less memory than xpr font (since we use many fonts in the skin). i did not see any performance degradation.
any constructive ideas?
-yuval
with newest cvs build, it can not display unicode file name with chinese character in smb share properly. filenames in smb share come with two flavors unicode and native encoding(such as gbk), i think it should be treated differently in the program.
i made a gbk xpr font with 7000 charaters. it includes all level 1 and level 2 chinese chararters and all japanese characters. 3000 chinese characters in level 1 cover 99% of everyday used chars. it uses 2048x2048 texture in font buldler and takes 8m in file size. i'll be glad to submit it.
can you tell me where to submit it?