[SMS] Wrong codification of UTF-8 character

RESOLVED FIXED

Status

()

RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: isabelrios, Assigned: pgravel)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Points:
---

Firefox Tracking Flags

(blocking-b2g:leo+)

Details

(Whiteboard: [com_ril][POVB])

Attachments

(4 attachments)

(Reporter)

Description

5 years ago
Created attachment 770774 [details]
à character codification

Unagi device 07/03 build: 
Gecko-38e6b25
Gaia-a890df3
Commercial RIL AU .148

STR
1. Start composing a text message
2. When the character counter appears, type an: Ã

EXPECTED
à character should count as one

ACTUAL
The counter goes from one message to the third one after typing à character.
Please see adb logcat attached in case it is useful. 
Also two screenshots, before and after typing the à are attached.
(Reporter)

Comment 1

5 years ago
Created attachment 770777 [details]
Befor à character
(Reporter)

Comment 2

5 years ago
Created attachment 770779 [details]
After à characther
(Reporter)

Updated

5 years ago
blocking-b2g: --- → leo?
Commercial RIL.
Whiteboard: [com_ril]
Blocking justification : same as in https://bugzilla.mozilla.org/show_bug.cgi?id=887745#c5 

Also adding qawanted to see if this is reproducible on Moz Ril.
blocking-b2g: leo? → leo+
Keywords: qawanted

Comment 5

5 years ago
Phil, could you please have a look?
Assignee: nobody → pgravel
Flags: needinfo?(pgravel)

Comment 6

5 years ago
The issue reproduces on Moz Ril too, 
same behavior - the counter goes from one message to the third one after typing à character

Unagi
Build  20130708070214
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/8c0127cc7be3
Gaia   7c40bdaeaffae708342fc773926dcfac5389348e
Keywords: qawanted
(Assignee)

Comment 7

5 years ago
à is not part of the gsm 7-bit alphabet so the whole message gets promoted to a higher alphabet when à is typed, which lowers the number of characters available per segment and thus increases the total number of segments being sent.

Can add à -> A mapping for both upper and lower case for when strict7BitEncoding is enabled, if that is what is being requested.
Flags: needinfo?(pgravel) → needinfo?(isabelrios)

Comment 8

5 years ago
Isabel, in addition to what Phil mentioned in comment #7, could you please send a complete list of all the characters TEF expects to be treated as strict 7 bit.
(Reporter)

Comment 9

5 years ago
(In reply to Anshul from comment #8)
> Isabel, in addition to what Phil mentioned in comment #7, could you please
> send a complete list of all the characters TEF expects to be treated as
> strict 7 bit.

Anshul, attached a txt file with the utf-8 characters expected to be supported. 

(In reply to pgravel from comment #7)
> 
> Can add à -> A mapping for both upper and lower case for when
> strict7BitEncoding is enabled, if that is what is being requested.

Yes, that character should be added to avoid problems. Thanks
Flags: needinfo?(isabelrios)
(Reporter)

Comment 10

5 years ago
Created attachment 772554 [details]
utf-8 characters and symbols
(Assignee)

Comment 11

5 years ago
Isabel,

Thanks for that character list, had a couple of questions:

` (grave accent): is not part of the gsm 7bit standard alphabet. I was planning mapping it to ' (apostrophe), let me know if there is a better mapping.

¼, ½, ¾: I don't see a way to input those with any of the keyboard layouts available.
Flags: needinfo?(isabelrios)
(Reporter)

Comment 12

5 years ago
Hi Phil, 

> ` (grave accent): is not part of the gsm 7bit standard alphabet. I was
> planning mapping it to ' (apostrophe), let me know if there is a better
> mapping.

That is ok.

> 
> ¼, ½, ¾: I don't see a way to input those with any of the keyboard layouts
> available.
Forget about them as it is not possible to type them.

Thanks
Flags: needinfo?(isabelrios)
(Assignee)

Comment 13

5 years ago
Fixed in AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.160
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Whiteboard: [com_ril] → [com_ril][POVB]
You need to log in before you can comment on or make changes to this bug.