Bug 3200 - Chromium browser do not display foreigner character correct.
Summary: Chromium browser do not display foreigner character correct.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: D Morgan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3198
  Show dependency tree / graph
 
Reported: 2011-10-27 06:58 CEST by Luan Pham
Modified: 2012-07-07 05:50 CEST (History)
2 users (show)

See Also:
Source RPM: chromium-browser-15.0.874.102-0.1.mga1.i586
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Luan Pham 2011-10-27 06:58:40 CEST 
Description of problem: When display web page in either Chinese or Arabic I got display with a square instead of correct character.


Version-Release number of selected component (if applicable):
chromium-browser-15.0.874.102-0.1.mga1.i586
Comment 1 Manuel Hiebel 2011-10-27 13:13:22 CEST 
That is the version in testing. 
Bug assigned to the package maintainer.

Assignee: bugsquad => dmorganec

Comment 2 Kamil Rytarowski 2011-10-29 04:02:44 CEST 
Are the fonts installed?

CC: (none) => krytarowski

Comment 3 Luan Pham 2011-10-29 06:58:05 CEST 
Yes this only happen for Chromium-browser and I open the same page it look ok on Firefox.
Manuel Hiebel 2011-10-29 14:43:05 CEST

Depends on: (none) => 3198

Manuel Hiebel 2011-10-29 14:43:19 CEST

Blocks: (none) => 3198
Depends on: 3198 => (none)

Comment 4 Marja Van Waes 2012-02-01 07:56:22 CET 
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

@ D Morgan

Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Don't change anything if you want to be pinged by me in this report again ;)

CC: (none) => marja11

Comment 5 Marja Van Waes 2012-07-06 15:06:25 CEST 
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 6 Luan Pham 2012-07-07 05:50:15 CEST 
I was report this problem while run on Mageia 1, but the problem already solve in Mageia 3.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.