The outputted FI stream/file contains whitespaces which were placed between tags in original XML and used to create a "pretty" XML (not single line -> added line breaks and indetion to make it easier to read for a human). Those whitespaces are not removed from the stream and are passed into the FI stream making it unnecesarilly larger.
This issue was discovered while I was comparing multiple Fast Infoset implementations - there is a noticable size difference and the additional whitespaces are clerarly identifiable in the stream while using a HEX editor (PSPad, in my case).
I can provide test data if necessary.
Environment
MS Windows 7 x64 - Oracle Java 7 update 40 (x64)
Fedora 18 x64 - OpenJDK 7 update 45
<_ en="'_'" ru="'_'" ua="'_'" pl="'_'"/>
<_ en="*" ru="*" ua="*" pl="*"/>
<_ en="'_'" ru="'_'" ua="'_'" pl="'_'"/>
<_ en="*" ru="*" ua="*" pl="*"/>
<_ en="'_'" ru="'_'" ua="'_'" pl="'_'"/>
<_ en="*" ru="*" ua="*" pl="*"/>
<Ошибки>
Ошибки>
<Ресурсы>
Ресурсы>
<_UnicodeString_><_Integer__0_ en="SysError Could not convert variant of type (UnicodeString) into type (Integer)(0)" ru="SysError Could not convert variant of type (UnicodeString) into type (Integer)(0)" ua="SysError Could not convert variant of type (UnicodeString) into type (Integer)(0)" pl="SysError Could not convert variant of type (UnicodeString) into type (Integer)(0)"/><_95_ en="DataError Data unsupported !!!(95)" ru="DataError Data unsupported !!!(95)" ua="DataError Data unsupported !!!(95)" pl="DataError Data unsupported !!!(95)"/><_255_ en="DataError Data unsupported !!!(255)" ru="DataError Data unsupported !!!(255)" ua="DataError Data unsupported !!!(255)" pl="DataError Data unsupported !!!(255)"/><_25_ en="DataError Data unsupported !!!(25)" ru="DataError Data unsupported !!!(25)" ua="DataError Data unsupported !!!(25)" pl="DataError Data unsupported !!!(25)"/><_203_ en="DataError Data unsupported !!!(203)" ru="DataError Data unsupported !!!(203)" ua="DataError Data unsupported !!!(203)" pl="DataError Data unsupported !!!(203)"/><_118_ en="DataError Data unsupported !!!(118)" ru="DataError Data unsupported !!!(118)" ua="DataError Data unsupported !!!(118)" pl="DataError Data unsupported !!!(118)"/><_211_ en="DataError Data unsupported !!!(211)" ru="DataError Data unsupported !!!(211)" ua="DataError Data unsupported !!!(211)" pl="DataError Data unsupported !!!(211)"/><_38_ en="DataError Data unsupported !!!(38)" ru="DataError Data unsupported !!!(38)" ua="DataError Data unsupported !!!(38)" pl="DataError Data unsupported !!!(38)"/>
The outputted FI stream/file contains whitespaces which were placed between tags in original XML and used to create a "pretty" XML (not single line -> added line breaks and indetion to make it easier to read for a human). Those whitespaces are not removed from the stream and are passed into the FI stream making it unnecesarilly larger. This issue was discovered while I was comparing multiple Fast Infoset implementations - there is a noticable size difference and the additional whitespaces are clerarly identifiable in the stream while using a HEX editor (PSPad, in my case). I can provide test data if necessary.
Environment
MS Windows 7 x64 - Oracle Java 7 update 40 (x64) Fedora 18 x64 - OpenJDK 7 update 45
Affected Versions
[1.2.9]