mirror of
https://github.com/ushahidi/SMSSync.git
synced 2026-04-25 15:55:57 +03:00
[GH-ISSUE #78] International (unicode) characters being mangled #66
Labels
No labels
Bug report
Code improvement
Concern
Feature request
Feature request
Good first issue to work on
In progress
Needs info
Question
Ready
Translation
User Experience
User Experience
Website
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SMSSync#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mitra42 on GitHub (Feb 7, 2013).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/78
We are trying to setup smssync to run in a south american country, and as soon as we started sending spanish strings we ran into problems. It looks like SMSSync is mangling the characters.
I'll attach an image showing what happens when someone sends Español (that's an n with a ~ over it) Smsync has turned it into Espa}ol and sent that to the server.
@eyedol commented on GitHub (Feb 7, 2013):
@mitra42. Encoding issue
@mitra42 commented on GitHub (Feb 7, 2013):
Sorry eyedol - "encoding issue" means what? I know about Unicode encoding, but this looks like an encoding issue within smsync, which doesn't seem to be handling the characters transparantly?
@eyedol commented on GitHub (Feb 7, 2013):
@mitra42. Correct. I meant, it's an encoding issue that
SMSSynccan't handle well. Needs fixing.@eyedol commented on GitHub (Feb 12, 2013):
@mitra42 I think it's an Android issue. Which version of Android are you running?
I have Jelly Bean 4.2.1 and I didn't get that issue. See attached screenshot.
@olliebennett commented on GitHub (Feb 24, 2013):
Can also confirm the symbol works fine on Android 4.0.4 (Ice Cream Sandwich)
@eyedol commented on GitHub (Mar 7, 2013):
Not a bug on SMSSync then. Closing.
@mitra42 commented on GitHub (Mar 7, 2013):
Pity you closed it - it may not technically be a SMSSync bug, but its failure to handle unicode on earlier versions of Android is pretty unique to SMSSYnc (SMS-es etc handle unicode just fine). The big problem is that it prevents the use of older, cheaper, android phones as gateways i.e. our cost of a gateway in any country just went from about $70 for a used one to $200+ for a current one that can run Android 4+. This seems pretty unique to SMSSync we haven't seen problems with unicode characters on any other application.
@eyedol commented on GitHub (Mar 8, 2013):
@mitra42 I clearly understand where you're coming from. I' have been trying to reproduce this from my end and I simply can't get it to show as you posted earlier. I'm happy to fix this if only I could know exactly what is going on. Does this only mess up on the
Senttab? Also which version of the Android OS are you running?@mitra42 commented on GitHub (Mar 8, 2013):
Hi Henry, first I must apologise, the problem wasn't yours it was ours - and I bet other developers hit it as well! We were sending unicode characters back from the server, but the encoding on the JSON was set to utf-8, so smssync was mis-interpreting the unicode characters. Thanks for your attention to this.
@eyedol commented on GitHub (Mar 8, 2013):
@mitra42 Thanks for reporting. I'll note that in the documentation so other developers don't repeat it.