Conversation
added 9 commits
December 26, 2020 10:31
…nd make the testLanguageTag make the switch only in Pharo9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Possibility to switch to Zinc UTF8 encoder/decoder in Pharo 9.
We keep the old TextConverter encoder/decoder as the default for now (and for those who need it in any case). The problem is that the old encoder (
UTF8TextConverter) uses a stream on aStringcollection whileZnUtf8Encoderrequires aByteArraycollection in the stream. Code changes are therefore often required. Seaside is not yet ready either but will switch at the some point.Users can switch between the used encoders by using:
GRPlatform current setutf8CodectoDeprecatedTextConverterandGRPlatform current setutf8CodectoZinc