This issue was fixed in xenial via <https://bugs.debian.org/787149>. OTOH, we don't use the fonts-droid-fallback package by default in Ubuntu. The replacement conf file in xenial (64-language-selector- prefer.conf) is correct in this respect.
The question is if the issue is important enough to backport the fix to trusty. If you think it is, please feel free to prepare a patch and accomplish a SRU in accordance with <https://wiki.ubuntu.com/StableReleaseUpdates>. ** Bug watch added: Debian Bug tracker #787149 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787149 ** Package changed: fonts-droid (Ubuntu) => fonts-android (Ubuntu) ** Changed in: fonts-android (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to fonts-droid in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1595822 Title: Monospace not Monospace in Japanese Status in fonts-android package in Ubuntu: Fix Released Bug description: I found this problem when testing FF for bug #1595414, on an English installation of 14.04. In short: $ LC_ALL='ja_JP.UTF-8' fc-match 'Monospace' DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1595822/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
