Commit 1b2a4f21 authored by Rogerborg's avatar Rogerborg

Elucidate on the (non) encoding conversions in irrString.

git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@1769 dfc29bdd-3216-0410-991c-e03cc46cb475
parent 8ddbcc67
...@@ -18,10 +18,15 @@ namespace core ...@@ -18,10 +18,15 @@ namespace core
{ {
//! Very simple string class with some useful features. //! Very simple string class with some useful features.
/** string<c8> and string<wchar_t> work both with unicode AND ascii, /** string<c8> and string<wchar_t> both accept Unicode AND ASCII/Latin-1,
so you can assign unicode to string<c8> and ascii to string<wchar_t> so you can assign Unicode to string<c8> and ASCII/Latin-1 to string<wchar_t>
(and the other way round) if your ever would want to. (and the other way round) if you want to.
Note that the conversation between both is not done using an encoding.
However, note that the conversation between both is not done using any encoding.
This means that c8 strings are treated as ASCII/Latin-1, not UTF-8, and
are simply expanded to the equivalent wchar_t, while Unicode/wchar_t
characters are truncated to 8-bit ASCII/Latin-1 characters, discarding all
other information in the wchar_t.
Known bugs: Known bugs:
Special characters like umlauts are ignored in the Special characters like umlauts are ignored in the
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment