[Bug 34978] Add international encodings to C.I.Cellular

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=34978

Marco Barisione <marco.barisione at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://git.collabora.co.uk/
                   |                            |?p=user/bari/telepathy-spec
                   |                            |.git;a=shortlog;h=refs/head
                   |                            |s/international-charsets
           Keywords|                            |patch
                 CC|                            |lassi.syrjala at nokia.com

--- Comment #1 from Marco Barisione <marco.barisione at collabora.co.uk> 2011-03-03 10:56:30 PST ---
http://git.collabora.co.uk/?p=user/bari/telepathy-spec.git;a=shortlog;h=refs/heads/international-charsets
add a C.I.Cellular.MessageNationalCharacterSet property.

The reason for having a string property is that new charsets are been added
with every standard release and we should avoid requiring a spec update every
time.
I'm calling this property MessageNationalCharset as the word national is used
in the standard (even if multiple nations share the same language...).

The behaviour I expect from a CM is:
* If MessageNationalCharset is 'gsm':
  * We can fit the text in the 7-bit GSM encoding:
    * Send it unchanged in GSM encoding
  * We cannot:
    * MessageReducedCharacterSet is true:
      * Force the conversion to 7-bit GSM
    * MessageReducedCharacterSet is false:
      * Use UCS-2
* If MessageNationalCharset is another encoding we understand:
  * We can fit the text in the encoding:
    * Send it encoded in the national charset (single or fixed? probably
      the CM should choose the best one)
  * We cannot:
    * MessageReducedCharacterSet is true:
      * Force the conversion to the national encoding
    * MessageReducedCharacterSet is false:
      * Use UCS-2
* If MessageNationalCharset is an encoding we don't know:
  * Just behave as if the encoding was GSM. (Or better, the CM should not
    accept setting the value to something it doesn't understand)

In case anybody wants to know more about GSM encodings look at
http://www.3gpp.org/ftp/specs/archive/23_series/23.038/

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.