Irrlicht Engine

Also if Filename in io::SAttributeReadWriteOptions will stay char*, then next small patch also necessary (but I don't like it) in \source\Irrlicht\CSceneManager.cpp at line 2237: options.Filename=core::stringc(currentPath).c_str(); You really want to avoid doing things like that. It would break the...

greenya wrote:P.S.: I believe this is because of enabled _IRR_WCHAR_FILESYSTEM.

You have to use the patch I supplied to the tracker.
http://sourceforge.net/tracker/?func=de ... tid=540676

Let me know if I need to updated it for the latest trunk.

could I do square roots huge brackets greek alphabet and such things with this ? No, you can't do square roots and huge brackets with this. This will just render whatever glyphs are in a font. This is the best you can do for square root: http://www.fileformat.info/info/unicode/char/221a/index.htm I...

New version of ustring: Renamed USTRING_NO_STL_COMPATIBLE_ITERATOR to USTRING_NO_STL. Added a constructor for constructing from a std::basic_string. Added a constructor for constructing from an iterator. Added operator+ methods for appending a ustring with an Irrlicht string. Added operator+ methods...

The 64bit types are not correctly defined. This would only work correctly under msvc or 64bit systems. We need a way to properly define the 64bit types under 32bit non-msvc systems, though. The type long long int is a 64-bit data type added to C99. Some compilers support it in C++ as an extension (...

New version of ustring: STL compatible iterator. It can be disabled with a #define. Fixed a corruption issue that afflicted UTF-8 and UTF-32 parsing. I also updated CGUITTFont to work with the latest trunk. As an example of the new iterator: core::ustring test("This is a test \xEF\xBF\xBD okay?...

The _IRR_WCHAR_FILESYSTEM define is broken again. It results in a failed compile. I started to try to fix it using fschar_t* instead of c8*, but I quickly ran into another issue: SAttributeReadWriteOptions::filename is a c8*. Will changing that to be an fschar_t break a bunch of stuff? It compiles f...

Could you try with my re-written CGUITTFont class? You can find it here:
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=37296

Thanks for reporting the issue. I've added a warning note to the OP. I also updated the patches to apply to 1.7.2 and to the latest trunk.

If you really, really want to allow unicode XML files, you pretty much will be forced to use my modifications: http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?t=37296 Irrlicht does not understand unicode. At all. Irrlicht's XML reader can read ASCII, UCS-2, and UTF-32/UCS-4. It, by default, rea...

New version of irrUString:

• Fixed a regression introduced with the GCC 4.5+ fixes in the last release.

If you really need UTF-8 XML files, here are my Irrlicht patches that CuteAlien alluded to: http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?t=37296 All you will need is the ustring class and the XML reading/writing files and patches. You will need to modify your Irrlicht project file / makefile...

The problem rises when I'm retrieving data from a UTF-8 encoded SQLite3 database. Let's say, for example, that i'm receiving the string for the french translation of the word "scenario", which is : "sc é nario". When looking in the debugger, the string I'm receiving ( of type co...

The value for © is 0xA9. Add it to your code like so: Keep in mind that the font you use has to include the symbol.

don't call erase() inside the loop but call clear() after the loop. With every iteration the array becomes smaller so after you erased enough elements from the array you are trying to access elements that are no longer there. This is the correct idea. If you are deleting the entire array, delete al...