923418 - [messaging] Include UTF-8 encoding support in SMS composer

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[Beatriz Rodríguez [:brg]]

As a requirement in some countries, the sms composer must use utf-8 encoding by default when writing a new sms.

We think this encoding is ready in the plaform for MMS composer but we had not seen it for sms (if we are wrong, please resolve this bug as Worksforme).

Comment 1

[Julien Wajsberg [:julienw]]

Hey Beatriz, I believe it's wrong :)


but maybe I don't understand what you're asking.

Currently, for SMS, we allow the user to enter any character. If the character is not included in the SMS 7bit encoding, we automatically switch to Unicode (which is not UTF-8 in the case of SMS, but it's UCS-2 IIRC). As a result, the length of a sms section is also reduced: from 153 char to 67 chars per section.

Is this what you had in mine ?

Comment 2

[Beatriz Rodríguez [:brg]]

(In reply to Julien Wajsberg [:julienw] (PTO today) from comment #1)
> Hey Beatriz, I believe it's wrong :)
> 
> 
> but maybe I don't understand what you're asking.
> 
> Currently, for SMS, we allow the user to enter any character. If the
> character is not included in the SMS 7bit encoding, we automatically switch
> to Unicode (which is not UTF-8 in the case of SMS, but it's UCS-2 IIRC). As
> a result, the length of a sms section is also reduced: from 153 char to 67
> chars per section.
> 
> Is this what you had in mine ?
let me double check the requirement with the country to see if we can cover it with UCS2, I will came back soon.

Comment 3

[Beatriz Rodríguez [:brg]]

The target country will be OK when using strict7bit encoding so no neeed to develop any new thing here just only to include this parameter in the operator variant logic. I will open a different new bug to track it.
Thanks for your help here Julien!