https://bugzilla.redhat.com/show_bug.cgi?id=1070506
Bug ID: 1070506 Summary: Google Chrome does not render Chinese/Japanese kanji characters in tab title after google-droid-sans-fonts is installed Product: Fedora Version: 20 Component: google-droid-fonts Severity: low Assignee: nicolas.mailhot@laposte.net Reporter: shichao.an.nyu@gmail.com QA Contact: extras-qa@fedoraproject.org CC: fonts-bugs@lists.fedoraproject.org, hobbes1069@gmail.com, nicolas.mailhot@laposte.net, paul@frixxon.co.uk, tremble@tremble.org.uk
Created attachment 868274 --> https://bugzilla.redhat.com/attachment.cgi?id=868274&action=edit Google Chrome tab title field does not display Chinese character
Description of problem: After google-droid-sans-fonts is installed, the Chrome Web Browser's tab title does not show Chinese/Japanese kanji characters (hiragana and katakana).
Version-Release number of selected component (if applicable): google-droid-sans-fonts.noarch-20120715-6.fc20
How reproducible: Always
Steps to Reproduce: 1. yum install google-chrome-stable 2. yum install google-droid-sans-fonts 3. In GNOME session, open Chrome with a new tab, open a web page that has Chinese/Japanese kanji characters in title field.
Actual results: In the Chrome tab title area, the Chinese/Japanese kanji characters simply do not display, while others are normal (e.g. Latin alphabet)
Expected results: In the Chrome tab title area, the Chinese/Japanese kanji characters should display.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1070506
Paul Flo Williams paul@frixxon.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shichao.an.nyu@gmail.com Flags| |needinfo?(shichao.an.nyu@gm | |ail.com)
--- Comment #1 from Paul Flo Williams paul@frixxon.co.uk --- Is it possible to reproduce this with packages that Fedora ships? There is no package "google-chrome-stable" in Fedora.
https://bugzilla.redhat.com/show_bug.cgi?id=1070506
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tagoh@redhat.com
--- Comment #2 from Akira TAGOH tagoh@redhat.com --- not sure but it looks like a Chrome bug. it works for me on version 35.0.1862.2 dev aura with google-droid-sans-fonts btw.
https://bugzilla.redhat.com/show_bug.cgi?id=1070506
--- Comment #3 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1070506
Fedora End Of Life endoflife@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2015-06-29 15:07:55
--- Comment #4 from Fedora End Of Life endoflife@fedoraproject.org --- Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
fonts-bugs@lists.fedoraproject.org