serialize() vs print() gotchas with UTF-8

[7Two1]

Rhino (git 5f1ad11) (latest as of 7 July 2013) ...

serialize() munges random UTF-8 chars on both Windows and Centos. (i.e. the […] ellipsis worked, the horizontal [－] failed .. this is not a minus sign. Therefore, for me, serialize() is not trustworthy)

My workaround was to use Centos and redirection in order to save processed data using print()

in my stripped down as an example wrapper.js file...

...
var infile = arguments[0];
serialize(readFile(infile, 'UTF-8'), 'output_filename');
...

java -jar rhinojar ./wrapper.js named_file_containing_utf-8_chars

fails

However,
...
var infile = arguments[0];
print(readFile(infile, 'UTF-8'));
...

java -jar rhinojar ./wrapper.js named_file_containing_utf-8_chars > output_filename

works

... as it turned out, serialize() will also output a BOM which I didn't want. Therefore, print() won out, however, due to Windows cmd limitations, redirection of print() data containing utf-8 will fail without some effort. It was easier to install Java and Ant under Centos instead of chasing after Windows peculiarities.

Hope this report helps.