You've described the exact issue in 2.2.3 which is already fixed in our code and will be available in 2.2.4.
Your problem is not with the creation part, which creates a perfectly valid JSON string, but rather with the parsing part.
Once you update to 2.2.4, server-side parsing of the string "\u00EB\u00F6\u00E4\u00F3\u00DF" will return "ëöäóß".
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
