Irrlicht Engine

Of course, I know that it's impossible to solve all problems immediately as people reports it... it is not the time about I'm complain about... but the lacks of discussions and informations on how to contribute.
I'm not familiar with sourceforge tools provided and I don't know how, where and which ...

Please write your bug reports more precisely next time so one can understand what really the bug is.

First of all, english is not my first language... so, I always make mistake in writing ... but anyway... you can't take only a piece of my long topic as a proof that I not explained well where is ...

Any whitespaces introduced are also no real problem because XML should be able to discard them on the fly

It's false !! Because withspaces indise tags are part of the contents of tag !!
I mean:

<TAG>Content ciao </TAG>

The withspaces between Content and ciao mustn't be replaced by any ...

I really don't understand ... I reported in this topic:

http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?t=17313

that the CXMLWriter has many bugs ... but the irrlicht 1.2 is out and nothing is changed !!
Some of the bugs arises only on Linux machines... and maybe I'm the only person that use ...

In my topic, I already notice that:

Sometimes, (I didn't understand this strange behaviour), when gcc encodes an L"String" declaration it prepends the "String" with the Byte Order Mark (BOM).

I've just see that this makes trouble also in operator== of string template.
And for patch this, again ...

Fixing to some byte size is definitely not a solution due to porting issues.

Excatly what I mean... but actually the SVN version of irrlicht has CXMLWriter that works only if wchar_t is 2-bytes and encoded in UTF16.

The main issue is that wchar_t doesn't imply a particular encoding, e.g. UCS or ...

It's a long topic, so I tried to organize it in part enclosed by "Problem section" and "Solution section" that, respectly, describes the bug and the solution proposed by me.
At the end there are some conclusion.

--- Problem:
The following seguence of calls produces an erroneuos xml content if the ...