-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
with recent NeoJSON work, should probably take a different approach to handling Unicode String encoding #6
Comments
needs to be done pre-3.3 release and use encodeAsUTF8intoString instead of |
Looks like the method STONReaderTests>>testJsonString was changed for GemStone ... so this one is likely to be the canary in the gold mine ... Also this test is familiar from NeoJSON where I added additional tests to cover the Unicode16 and Unicode32 examples .... needed for STON tests as well ... and critical for getting unicode handling right. |
…is issue so that the changes can be cherry-picked into the common branch
As I have evolved the STON object serialization for tODE, I am now interested in refactoring the STON work into three segments:
|
…on options: - classic (utf8 challenged) - utf8-friendly - GemStone/tODE v0.5.1 - GemStone/tODE v0.9.* Consolidating the Pharo/GemStone packages in the gemstone branch.
…anch/tag for Ston ...
…ode strings (Unicode16 and Unicode32 examples) and a bit of cross materialization (051 serializer -> 091 marterializer)
Implementation covering the 4 different serialization schemes .. now need to revisit STON api to access the different schemes ... (don't break tODE:) .... convert object serializers first) |
get test results: https://travis-ci.org/GsDevKit/ston/builds/68563919 |
get test results (again) https://travis-ci.org/GsDevKit/ston/builds/68845525 |
…l implementation ... GemStone-specific mods are now present in STON051*, STON091*, and STONutf8* classes ... Modify tests to accomodate svenvc#11
NeoJSON work ...
The text was updated successfully, but these errors were encountered: