hi，Wim
So what are my recommendations wrt string literals with non-ascii
> characters in C++ files...
> 1. Don't do it. Use Wt's tr() mechanism to avoid the encoding mess
> completely. Use a pure ASCII key within the tr() (note that I wrote
> tr("Frankfurt") without umlaut on the u, that was not a typo). Use
> WApplication::messageResourceBundle() and store all encoded strings in
> a properly formatted external XML file. XML files do specify their
> encoding, a C file does not.
> 2. If you can't resist, use L"íntèrnätïñonal Ç++ string". But then you
> have to ensure that the source file encoding assumed by your C
> compiler (could be UTF-8, ISO 8859-1, ...) corresponds to the actual
> encoding of the C file.
>
>
Thanks
Just update my app from wt-3.0.0 to wt-3.1.2, it is a challenge and a chance
at the same time, the challenge is that I need more time to create every
relative item string in the external xml, and the chance is that my app will
be internationalized :-)
Regards
Zhimin
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
