Fix issues if runing in an environment with a Turkish locale #652
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.
Description
When using
LOWER_CASE_WITH_DASHES
orLOWER_CASE_WITH_UNDERSCORES
as FieldNamingPolicy it could happen that certain fields won't get serialized/deserialized.I've seen that behavior on devices with a turkish (
tr-TR
) locale.toLowerCase()
uses the device's locale and converts anI
into anı
. (JavaDoc)Example
A field with the name:
will turn into:
Recreation steps
Check out the first commit (299ee89) and run the test with the following JVM flags:
-Duser.language=tr -Duser.region=TR
References
https://code.google.com/p/google-gson/issues/detail?id=541
http://docs.oracle.com/javase/7/docs/api/java/lang/String.html#toLowerCase()