Hello Mohammad, or anyone else affected, Accepted language-selector into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/language- selector/0.188.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: language-selector (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser Status in language-selector package in Ubuntu: Fix Released Status in language-selector source package in Bionic: Fix Committed Bug description: [Impact] The file for configuring Japanese rendering with Noto fonts does not refer to the font family with sufficient precision, so it may affect rendering with other fonts unintentionally. The proposed upload fixes the issue. [Test Case] The real tests have been reported in comment #6 and #7 of this bug report. To verify that the modified file is properly installed: 1. Install language-selector-common and language-selector-gnome from bionic-proposed 2. Run this command: cat /etc/fonts/conf.avail/69-language-selector-ja.conf | grep 'Noto Sans CJK JP' (should output the line "<string>Noto Sans CJK JP</string>") [Regression Potential] That config file was added specifically for rendering Japanese with Noto fonts, and the modified file has been confirmed by the original author. Hence the regression risk should be low. [Original description] Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this <test qual="all" name="family" compare="contains"> which should instead be <test qual="all" name="lang" compare="contains"> since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
