Graeme Geldenhuys schrieb:
If FPC has true unicode support, then all functions should work correct with just the UnicodeString type. That type's encoding is based on the native encoding of each platform. NO performance hit required.
Can you specify, *which* strings ever *require* platform specific encoding? Beyond filenames and environment strings?
UI strings (GUI, console) are more thightly bound to user code and component/widgetset libraries, than to a platform API (see my other comment)
DoDi _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel