[Documentation-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
** Changed in: fonts-android (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Documentation Packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Status in “fonts-android” package in Debian: Fix Released Bug description: [Impact] fontconfig configuration settings, aimed at making the Droid Sans Fallback font be used to render Chinese, fails sometimes in an unpredictable way. This seems to be caused by the file 65-droid-sans- fonts.conf, which is currently installed by fonts-droid. Consequently that file is proposed to be dropped from fonts-droid. Some fontconfig files in language-selector are proposed to be changed accordingly. Example problems: * One of the AR PL UMing fonts is sometimes used instead of Droid Sans Fallback in case of a Chinese locale. * Buggy rendering of Chinese contents in qt apps in case of a non-Chinese locale (bug #1334495). * Droid Sans Fallback can't be used in Ubuntu Touch (see discussion at bug #1346766). [Test Case] Since the behaviour is not always buggy, it's hard to present a proper test case. Instead I have to refer to the discussions in this bug report as well as the above mentioned bugs. [Regression Potential] While the fonts-droid package installs a bunch of fonts for various languages, only the Droid Sans Fallback font is used as part of Ubuntu's default font configuration. The regression risk for Chinese users is reasonably very low. There is a risk, though, that this change leads to surprise changes for individual users who make use of other fonts but Droid Sans Fallback. There is no indication that those other fonts are widely used. [Original description] There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~documentation-packages Post to : documentation-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~documentation-packages More help : https://help.launchpad.net/ListHelp
[Documentation-packages] [Bug 1360657] Re: Incorrect space character at the power-hibernate page
I don't think this should be marked Fix Committed until it is in trusty- proposed. ** Changed in: ubuntu-docs (Ubuntu Trusty) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu. https://bugs.launchpad.net/bugs/1360657 Title: Incorrect space character at the power-hibernate page Status in “ubuntu-docs” package in Ubuntu: Fix Released Status in “ubuntu-docs” source package in Trusty: Confirmed Bug description: The power-hibernate page includes example code to enable hibernation. However, as regards the "Action" key in the logind entry, the semi- colon in the list is followed by a space character which prevents the multiple-sessions identifier from being loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1360657/+subscriptions -- Mailing list: https://launchpad.net/~documentation-packages Post to : documentation-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~documentation-packages More help : https://help.launchpad.net/ListHelp
[Documentation-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
** Branch linked: lp:debian/fonts-android -- You received this bug notification because you are a member of Documentation Packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Status in “fonts-android” package in Debian: New Bug description: [Impact] fontconfig configuration settings, aimed at making the Droid Sans Fallback font be used to render Chinese, fails sometimes in an unpredictable way. This seems to be caused by the file 65-droid-sans- fonts.conf, which is currently installed by fonts-droid. Consequently that file is proposed to be dropped from fonts-droid. Some fontconfig files in language-selector are proposed to be changed accordingly. Example problems: * One of the AR PL UMing fonts is sometimes used instead of Droid Sans Fallback in case of a Chinese locale. * Buggy rendering of Chinese contents in qt apps in case of a non-Chinese locale (bug #1334495). * Droid Sans Fallback can't be used in Ubuntu Touch (see discussion at bug #1346766). [Test Case] Since the behaviour is not always buggy, it's hard to present a proper test case. Instead I have to refer to the discussions in this bug report as well as the above mentioned bugs. [Regression Potential] While the fonts-droid package installs a bunch of fonts for various languages, only the Droid Sans Fallback font is used as part of Ubuntu's default font configuration. The regression risk for Chinese users is reasonably very low. There is a risk, though, that this change leads to surprise changes for individual users who make use of other fonts but Droid Sans Fallback. There is no indication that those other fonts are widely used. [Original description] There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~documentation-packages Post to : documentation-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~documentation-packages More help : https://help.launchpad.net/ListHelp
[Documentation-packages] [Bug 1334495] Re: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts
** Branch linked: lp:debian/fonts-android -- You received this bug notification because you are a member of Documentation Packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Bug description: [Info for the Trusty SRU request] Please see the description at bug #1351092. [Original description] Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a "italic" font, others in a "normal" font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the "normal" characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of "locale" looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. "locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE="de_DE.UTF-8" LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE="de_DE.UTF-8" LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES="de_DE.UTF-8" LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= " fc-match: »DejaVuSans.ttf: "DejaVu Sans" "Book"« This is my first bug filed at launchpad. I filed it for language- selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~documentation-packages Post to : documentation-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~documentation-packages More help : https://help.launchpad.net/ListHelp
