| Summary: | Chromium browser do not display foreigner character correct. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Luan Pham <pham182b> |
| Component: | RPM Packages | Assignee: | D Morgan <dmorganec> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, n54 |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | chromium-browser-15.0.874.102-0.1.mga1.i586 | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 3198 | ||
|
Description
Luan Pham
2011-10-27 06:58:40 CEST
That is the version in testing. Bug assigned to the package maintainer. Assignee:
bugsquad =>
dmorganec Are the fonts installed? CC:
(none) =>
krytarowski 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 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 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 I was report this problem while run on Mageia 1, but the problem already solve in Mageia 3. Status:
NEW =>
RESOLVED |