You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/02 08:55:00 UTC

[jira] [Resolved] (CAMEL-8002) determineAlphabet only considers GSM 3.38 or UCS2

     [ https://issues.apache.org/jira/browse/CAMEL-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-8002.
--------------------------------
    Resolution: Abandoned

> determineAlphabet only considers GSM 3.38 or UCS2
> -------------------------------------------------
>
>                 Key: CAMEL-8002
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8002
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-smpp
>    Affects Versions: 2.12.2
>         Environment: n/a
>            Reporter: Daniel Pocock
>            Priority: Minor
>
> SmppSmCommand.determineAlphabet(Message) tries to work out which SMPP alphabet code is suitable for encoding the message text.
> It checks if GSM 3.38 can represent all the characters in the message and if not it just uses UCS2 (UTF-16).
> This is less than optimal.  Many messages using European languages can not be encoded in GSM 3.38 but they can be coded in Latin1, which is also supported by SMPP (data_coding / alphabet numeric code for Latin1 is 3)
> The jSMPP library (Alphabet.java) does not currently know about the alphabet code 3.
> I proposed a patch for jSMPP and if it is accepted then camel-smpp should be updated to use it.  I already started writing a patch against camel-smpp.  Here is the jSMPP patch:
> https://github.com/uudashr/jsmpp/pull/39



--
This message was sent by Atlassian Jira
(v8.20.10#820010)