Updated Message->containsUnicode() to detect the GSM 03.38 Basic Character Set#13
Merged
vood merged 1 commit intoConnectCorp:masterfrom Sep 8, 2015
Merged
Conversation
…ich are outside the GSM default character set. Nexmo claims to be able to support the GSM 03.38 Basic Character Set <http://unicode.org/Public/MAPPINGS/ETSI/GSM0338.TXT> in text (not unicode) messages. Here, I've changed this method to test specifically for these. The old method fails because many of these characters are outside the normal ASCII range, and because the characters cannot be converted safely using ord() and str_split().
vood
added a commit
that referenced
this pull request
Sep 8, 2015
Updated Message->containsUnicode() to detect the GSM 03.38 Basic Character Set
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
2 participants
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.
Nexmo claims to be able to support the GSM 03.38 Basic Character Set http://unicode.org/Public/MAPPINGS/ETSI/GSM0338.TXT in text (not unicode) messages. Here, I've changed this method to test specifically for these. The old method fails because: