Closed Bug 880648 Opened 11 years ago Closed 11 years ago

[MMS] Accented characters are not correctly sent/received in a MMS

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla24
blocking-b2g leo+
Tracking Status
firefox22 --- wontfix
firefox23 --- wontfix
firefox24 --- fixed
b2g18 --- fixed
b2g18-v1.0.0 --- wontfix
b2g18-v1.0.1 --- wontfix
b2g-v1.1hd --- fixed

People

(Reporter: isabelrios, Assigned: airpingu)

References

Details

(Whiteboard: MMS_TEF)

Attachments

(4 files, 3 obsolete files)

Attached image MMS sent
Bug seen on Unagi v1-train Gecko-65bbcee Gaia-13c6246 PROCEDURE With the device in Spanish 1.Create a new MMS, attach a file (it does not matter from where) and write for example: Más 2.Send the MMS EXPECTED The MMS is sent correctly, the file is ok and also the text ACTUAL The characters are not shown correctly. See screenshot attached. Maybe is it realated to bug 877141?
Attached image MMS received
This issue is very important and blocking the launching dates. The text included in a MMS should never be changed and should reach the other party in the same way it is written by the sender. Changing the component to something more appropiate.
Component: Gaia::SMS → DOM: Device Interfaces
Product: Boot2Gecko → Core
(In reply to Beatriz Rodríguez [:brg] from comment #2) > This issue is very important and blocking the launching dates. > The text included in a MMS should never be changed and should reach the > other party in the same way it is written by the sender. > Changing the component to something more appropiate. Absolutely
Reproduce by 6/10 build Seem like SMS is also wrong on receiver
Hi Gene! Could you help with this? Thanks!
Flags: needinfo?(gene.lian)
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Pleasure!
Assignee: nobody → gene.lian
Blocks: b2g-mms
Flags: needinfo?(gene.lian)
Blocks: 883017
I can't reproduce here on gaia master as of 5ffca88
Could it be related to strict 7 bits encoding?
Eventually, I found out this bug doesn't relate to bug 883017. That bug addresses the issue of wrong text displaying on other parties. This bug addresses the issue of wrong text displaying on our FFOS. I can still reproduce this issue by sending a text like "Más" as mentioned at comment #0. I'm working out a solution for this issue.
No longer blocks: 883017
Attachment #763500 - Flags: review?(vyang)
Attachment #763500 - Flags: feedback?(ctai)
Attachment #763500 - Attachment description: Part 1, content blob should be encoded by utf-8 → Part 1, content blob should be encoded by utf-8 (Gecko end)
Attachment #763504 - Attachment is obsolete: true
Attachment #763504 - Flags: review?(schung)
Attachment #763505 - Flags: review?(schung)
Hi dietrich, We need you help to mark leo+ for this bug which is definitely a critical issue. Thanks!
Flags: needinfo?(dietrich)
Blocks: 883017
Blocking. However, please add a test to ensure support of these types of characters in the platform layer.
blocking-b2g: leo? → leo+
Flags: needinfo?(dietrich)
Comment on attachment 763500 [details] [diff] [review] Part 1, content blob should be encoded by utf-8 (Gecko end) Review of attachment 763500 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me.
Attachment #763500 - Flags: feedback?(ctai) → feedback+
Comment on attachment 763500 [details] [diff] [review] Part 1, content blob should be encoded by utf-8 (Gecko end) Review of attachment 763500 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/mobilemessage/src/ril/WspPduHelper.jsm @@ +2308,5 @@ > + // If the content is a "text/plain" type, we have to make sure > + // the encoding of the blob content should always be "utf-8". > + let tmpStr = this.decodeStringContent(octetArray, charset); > + let encoder = new TextEncoder("UTF-8"); > + content = new Blob([encoder.encode(tmpStr)], {type : mimeType}); nit: we should also reset charset to "utf-8" here.
Attachment #763500 - Flags: review?(vyang) → review+
Addressing the comment. Thanks Vicamo and Ctai for the feedback.
Attachment #763500 - Attachment is obsolete: true
Attachment #764028 - Flags: review+
Attachment #764028 - Flags: feedback+
Whiteboard: MMS_TEF → MMS_TEF[leave open][fixed-in-birch]
Attachment #763505 - Flags: review?(schung) → review+
Attachment #763505 [details] landed in gaia master: 70e1de2de1722e6ecd131d68a0a403f5e1054166
Whiteboard: MMS_TEF[leave open][fixed-in-birch] → MMS_TEF[fixed-in-birch]
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: MMS_TEF[fixed-in-birch] → MMS_TEF
Target Milestone: --- → mozilla24
https://hg.mozilla.org/releases/mozilla-b2g18/rev/636880c5d3ad Leaving status-b2g18 set to affected for the v1-train and v1.1hd uplifts.
v1-train & 1.1hd: aea6834efc2b291971c3065eca7bdfe74a319be8
Flags: needinfo?(jhford)
Flags: in-moztrap?
Can someone from QA verify this issue please?
Whiteboard: MMS_TEF → MMS_TEF, qawanted
Hi, with today's build: Gecko-2ff3151 Gaia-d8d189b I cannot reproduce the problem with accented chars. Seems to be working fine now. Thanks
Status: RESOLVED → VERIFIED
Whiteboard: MMS_TEF, qawanted → MMS_TEF
Flags: in-moztrap? → in-moztrap+
Flags: in-moztrap+ → in-moztrap?(cschmoeckel)
Created new MMS Suite Test Case #8905 - Send MMS message using accented characters
Flags: in-moztrap?(cschmoeckel) → in-moztrap+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: