Re: wstring, wofstream, and encodings

Thanks. I'm actually wroking on a Crypto interop project. Is there
anyway to stop it in it's entirety? I guess you can imagine the issues
this is causing on encrypted data.

Last night I read pertinent sections of Stroustrap's C++ Programming
Language [1] (strings, streams, locales) and his Appendix D - Locales
[and Facets] [2]. I also read Schmitt's 'International Programming for
Microsoft Windows' [3]. None seem to address this issue.

Is this specifed in ISO? Unfortunately, I'm not too familiar with the
standard, and I do not have a copy of it. If so, I could understand
the compression (if specified). I can deal with/without the BOM and
The Unicode Consortium's standards and recommendation, and ISO/IEC
10646. But the loss of data on the code point U+9AA8 is absolutely
unacceptable.

Jeff
Jeffrey Walton

[1] B Stroustrup, The C++ Programming Language, Addison Wesley Inc.,
ISBN 0-201-70073-5
[2] B Stroustrup, The C++ Programming Language, Appendix D: Locales,
Addison Wesley Inc., ISBN 0-201-70073-5
[3] International Programming for Microsoft Windows, Microsoft Press,
ISBN 1572319569