Hmm. I guess I could use both methods. The reason I did it that way was because people may do something like this:zet.dp.ua wrote:One suggestion: it would be better to minimize the additional info in the xml file. <entry id="My string">My string</entry>, <s id="My string">My string</s> could be enough.
Integrating string table with irrlicht's text node can really save a lot of time.
Don't write any possibly localizable text in the code!!!
Code: Select all
core::ustring info = st::_T("<Information>");
Of course, because they used < and >, it breaks XML. Which is why I support CDATA:
Code: Select all
<entry>
<id><![CDATA[<Information>]]></id>
<translation>sdfsdfgjkdfhg</translation>
</entry>
---
I've uploaded new changes:
ustring:
- Fixed operator= that I broke with the previous upload.
- Fixed an error in UTF-8 and UTF-32 parsing that I introduced in the previous upload.
- Support for a more condensed XML style.