#8 Wrong unicode strings handling

[Oleksandr Dodatko]

Try to read the JSON file, containing the unicode symbols (for example, the google chrome "Preferences" file). Write it using the StyledWriter.
The unicode strings will be no omore valid as they will contain binary symbols. (Hence, the new settings file won't be recognized by the google chrome).

I have added some new configurations (VS8 projecs only) and build conditions for the unicode handling.In these configurations unicode symbols are not decoded and are handled as usual text instead.

[Oleksandr Dodatko]

Added new VS8 configurations. In these configurations unicode symbols are not decoded and are handled as usual text instead. Fixed unicode shadowing

[Baptiste Lepilleur]

I think the right way to integrate this in the library is to optionally escape unicode string in the writer (by enhancing the Features structure).

[Christopher Dunn]

Pretty sure blep's idea is done: https://github.com/open-source-parsers/jsoncpp/