I don't think is that simple. The right Unicode support would have wchar* instead of char* in all function calls, and specially in the Lua binding. We don't need to change the current API, but at least we should have to add new functions where there is string as a parameter to correctly support Unicode.
That's why I like UTF-8, so we can keep the same API, and change things only at the system function call. Anyway this is not in our short term task list. But I think that eventually will became necessary. Best, Scuri Em qua, 12 de set de 2018 às 05:19, 云风 Cloud Wu <[email protected]> escreveu: > Antonio Scuri <[email protected]>于2018年9月10日周一 下午7:03写道： > >> Hi 云履, >> >> In IUP, CD and IM we use fopen to read and write files most of the >> time, with a few exceptions when there is a native API that loads or saves >> the file for us. >> >> IUP access files mainly for configuration files in LED, Lua or cfg >> (IupConfig). >> >> CD writes metafiles, for instance. >> >> IM loads and saves image files in several different formats using >> different APIs, but most of the time uses fopen too. >> >> So, actually they all have the same problem. >> >> > Could you consider write a fopen wrapper (and use a macro define for > compatibility) for better unicode support ? > > In windows, we can use _wfopen to solve encoding problems. > > _______________________________________________ > Iup-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/iup-users >
_______________________________________________ Iup-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/iup-users
