[Documentation-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts
I have this same effect on my Xenial (Unity) desktop. It is especially evident in chrome with URLs that contain numerics. -- You received this bug notification because you are a member of Documentation Packages, which is subscribed to ubuntu-font-family- sources in Ubuntu. https://bugs.launchpad.net/bugs/1520772 Title: New font uses Arabic-sized figures in Latin contexts Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: Confirmed Bug description: Upgrade of ubuntu fonts causes fonts to look as in attachments ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 28 12:34:43 2015 Dependencies: InstallationDate: Installed on 2015-10-29 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+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 1441210] Re: Roboto fonts make printer crash (fonts-android)
Hello Jean-Sebastien, or anyone else affected, Accepted fonts-android into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fonts- android/1:4.3-3ubuntu1.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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: fonts-android (Ubuntu Trusty) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1441210 Title: Roboto fonts make printer crash (fonts-android) Status in fonts-android package in Ubuntu: Fix Released Status in fonts-android source package in Trusty: Fix Committed Status in fonts-android package in Debian: New Bug description: trusty SRU request == [Impact] When using Roboto fonts (the fonts-roboto package), printing fails with some printers. This has been fixed in later versions, so this proposed upload installs Roboto fonts from fonts-android 4.4.4r2 instead of 4.3. Unlike fonts-droid, fonts-roboto is not a seeded package, so while it's an annoying bug for those affected, this fix only affects those who explicitly install and use fonts-roboto. [Test Case] * Package: fonts-roboto 1:4.3-3ubuntu1.1 * Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. * Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. [Regression Potential] Low. [Original Description] As per https://code.google.com/p/android/issues/detail?id=38383, there has been issues with the Roboto font family regarding printing. These issues seem to have been resolved in the new version of the fonts made available by Google in 2014 here http://developer.android.com/design/style/typography.html. My setup: 1) Release: Ubuntu 14.04 LTS 2) Package: fonts-roboto 1:4.3-3ubuntu1.1 3) Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. 4) Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. Steps to reproduce: Install fonts-roboto package from Ubuntu Software Center. Produce a document in Libre Office with Roboto font and send to printer. Printer is crashing, need hard reboot. Workaround: (1) Remove fonts-roboto package from Ubuntu Software Center. (2) Download new version of the fonts made available by Google and save them in the .fonts folder in home directory. (3) Produce a new document with Roboto font and send to printer. (4) Document is printing. Basically, I think this package just need to be updated to use the latest fonts issued by Google. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1441210/+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] Update Released
The verification of the Stable Release Update for language-selector has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in “language-selector” source package in Trusty: Fix Released 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
[Documentation-packages] [Bug 1351092] Update Released
The verification of the Stable Release Update for language-selector has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in “language-selector” source package in Trusty: Fix Released 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
