Difference between revisions of "Talk:LCL Unicode Support"
| Line 4: | Line 4: | ||
Maybe it is best, if we create a new widgetset win32u, that uses the unicode functions instead of ascii functions. [[User:Vincent|Vincent]] 14:33, 20 May 2006 (CEST) | Maybe it is best, if we create a new widgetset win32u, that uses the unicode functions instead of ascii functions. [[User:Vincent|Vincent]] 14:33, 20 May 2006 (CEST) | ||
| + | |||
| + | No it doesnt,actually with use of *W api calls it doesnt too!Win98 doesnt support *W calls,it is supported with unicode interface layer ie unicows,which it also doesnt do anything special just convert utf16 to ansi and opposite if required. | ||
| + | |||
| + | We can do that new widgetset too,it maybe make the code also more clear and maybe we can have some special optimizations too! | ||
| + | but somebody should make sure other stuff between these 2 interfaces become sync and also as i did almost the very same for wince interface i can tell code conversion is not more than 5% of all codes,so we are doing lots of code duplication which is not good! | ||
| + | |||
| + | Maybe haveing a common interface-also between win32a ,win32u and wince-and move those functions/code which need modification to another place. | ||
| + | [[User:Roozbeh\Roozbeh]] | ||
Revision as of 22:29, 21 May 2006
Some questions / things unclear
I want to undertand more and have the following question:
- Suppose the LCL encodes all its strings using UTF8, could you display for instance cyrilic or Arabic in a Russian or Arabian version of win98, i.e. without using the *W winapi calls? As far as I know both together will be impossible then, because no code page supports both charsets. Please correct me, if wrong.
Maybe it is best, if we create a new widgetset win32u, that uses the unicode functions instead of ascii functions. Vincent 14:33, 20 May 2006 (CEST)
No it doesnt,actually with use of *W api calls it doesnt too!Win98 doesnt support *W calls,it is supported with unicode interface layer ie unicows,which it also doesnt do anything special just convert utf16 to ansi and opposite if required.
We can do that new widgetset too,it maybe make the code also more clear and maybe we can have some special optimizations too! but somebody should make sure other stuff between these 2 interfaces become sync and also as i did almost the very same for wince interface i can tell code conversion is not more than 5% of all codes,so we are doing lots of code duplication which is not good!
Maybe haveing a common interface-also between win32a ,win32u and wince-and move those functions/code which need modification to another place. User:Roozbeh\Roozbeh
