901843 - [zffos1.1][MMS]Spanish characters are garbled in received MMS.

Status: RESOLVED WORKSFORME

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

Description

[RuiLi]

Attachment: sent_received.JPG

User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36

Steps to reproduce:

1. Send a MMS containing some special spanish characters(english letter + symbol above)
2. Download this MMS and open it.


Actual results:

Those special spanish characters are garbled(see the attachments).


Expected results:

All words should be display correctly.

Comment 1

[Preeti Raghunath(:Preeti)]

per the attachement this looks ugly.

:jcheng, please help assign the bug.

Comment 2

[Steve Chung [:steveck]]

(In reply to RuiLi from comment #0)
> Created attachment 786158 [details]
> sent_received.JPG
> 
> User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like
> Gecko) Chrome/27.0.1453.116 Safari/537.36
> 
> Steps to reproduce:
> 
> 1. Send a MMS containing some special spanish characters(english letter +
> symbol above)
> 2. Download this MMS and open it.
> 
> 
> Actual results:
> 
> Those special spanish characters are garbled(see the attachments).
> 
> 
> Expected results:
> 
> All words should be display correctly.

Hi RuiLi, could you please provide your build id? I think we already fixed encoding issue before, thanks.

Comment 3

[Gene Lian (I already quit Mozilla)]

I used FFOS to send MMS carrying exactly the same string shown in the attachment to another FFOS. The received string looks correct. I cannot reproduce this bug.

Comment 4

[Gene Lian (I already quit Mozilla)]

Bug 880648 and Bug 883017 should have already fixed this bug.

Comment 5

[RuiLi]

How to get build id?

Comment 6

[RuiLi]

We update gecko and gaia this week. I check the newer version has involved the codes for bug880648 and 883017. We'll test it again next week.

Comment 7

[RuiLi]

The bug is clear in latest version. It can be closed.

Comment 8

[Ivan Tsay (:ITsay)]

Close bug since it works in the new build.