[Touch-packages] [Bug 1595414] Re: Awful system-wise generic selection for CJK

2016-06-24 Thread Mingye Wang
My current suggestion is to construct a test HTML like this: UKai/UMing test /* Change the needle font here */ body { font-family: sans-serif; } 漢字汉字 @ zh 漢字汉字 @ ja 漢字汉字 @ en After removing UKai from my system, it begins to show UMing. * * * > as far as I can retell, should be

[Touch-packages] [Bug 1595414] Re: Awful system-wise generic selection for CJK

2016-06-24 Thread Mingye Wang
Just an uninteresting side note, setting font-family to either 'Monospace' or monospace in the test case above shows a very proportional font for ja. This should be a separate report, but just in case I forget: $ LC_ALL='ja_JP.UTF-8' fc-match 'Monospace' DroidSansFallbackFull.ttf: "Droid Sans

[Touch-packages] [Bug 1595414] Re: Awful system-wise generic selection for CJK

2016-06-23 Thread Mingye Wang
Well, I am using Firefox, Firefox 47.0+build3-0ubuntu0.14.04.1. With UKai installed, as far as I can retell, some of the Chinese content (usernames in Twitter notifications) are still displayed in Droid Sans, while tweet bodies are mostly displayed in UKai. I have just did some extra 'inspect

[Touch-packages] [Bug 1595414] [NEW] Awful system-wise generic selection for CJK

2016-06-23 Thread Mingye Wang
Public bug reported: In https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/fonts- arphic-ukai/wily/revision/6, UMing and UKai are set as generics for fonts. However, this set of generics is completely intolerable -- setting UKai as a generic is like setting Zapfino and/or Comic Sans as a

[Touch-packages] [Bug 1560548] Re: Redundant fontconfig files

2016-06-03 Thread Mingye Wang
Just FYI, a user (GPG D0556253) complained about "installing complete Chinese support in 14.04 causes uming and ukai to be default fonts" in an informal chat that I was just participating in. Unfortunately I don't have the condition to reproduce the bug, and additionally he mentioned that the bug

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-04-07 Thread Mingye Wang
Not sure. Some fontconfig tracing env vars might be useful for the Skia LegacyCreateTypeface part I guess... * * * In addition to the weight matching problem, the screenshot for Chromium in #113 gives the JP variant instead of TW. Perhaps I should try to get someone to reproduce this in other

[Touch-packages] [Bug 1566651] Re: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

2016-04-06 Thread Mingye Wang
Upstream HEAD git log with 'bitmap': https://cgit.freedesktop.org/fontconfig/log/?qt=grep=bitmap=1 The two 2015-05-27 commits, and the 2014-08-20 one look interesting. I'm not sure if it's worth to try some extra cherry-picking though. Backporting is hard it seems. By the way, upstream tagged

[Touch-packages] [Bug 1566651] Re: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

2016-04-06 Thread Mingye Wang
Does force-regenerating font cache using `fc-cache -f` help? The commit message in 3cd573f says: > This may breaks the cache but not bumping in this change sets at this moment. > please be aware if you want to try it and run fc-cache before/after to avoid > the weird thing against it. I didn't

[Touch-packages] [Bug 1556457] Re: [FFe] Demilight (OS/2 weight=350) confuses fontconfig

2016-04-05 Thread Mingye Wang
** No longer affects: fontconfig (Arch Linux) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1556457 Title: [FFe] Demilight (OS/2 weight=350) confuses fontconfig

[Touch-packages] [Bug 1556457] Re: [Resolved Upstream] Demilight (OS/2 weight=350) confuses fontconfig

2016-03-12 Thread Mingye Wang
** Also affects: fontconfig (Arch Linux) Importance: Undecided Status: New ** Description changed: See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug 1468027. Fontconfig lacks support for many OpenType/TrueType OS/2 font weight values. This causes a bunch of

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-12 Thread Mingye Wang
** No longer affects: fontconfig (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1468027 Title: change default CJK fonts to Noto CJK Status in Fontconfig:

[Touch-packages] [Bug 1556457] [NEW] [Resolved Upstream] Demilight (OS/2 weight=350) confuses fontconfig

2016-03-12 Thread Mingye Wang
Public bug reported: See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug 1468027. Fontconfig lacks support for many OpenType/TrueType OS/2 font weight values. This causes a bunch of problems, like mixing up Demilight (weight=350) and Regular (weight=400). Although it's possible to

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-12 Thread Mingye Wang
Let me file the fc demi report separately then. A fix is always better than a hack, and with Noto Sans CJK hacked there are still a whole bunch of Notos and other weight-rich fonts. Just realized my PPA pkg is based on 2.11.1-0ubuntu6 instead of current ubuntu8, hmm. Can't see xenial on bzr...

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
Fontconfig 2.11.9x are actually devel versions. https://www.freedesktop.org/wiki/Software/fontconfig/Devel/ These patches are relevant: ffda7c0 bf9df5a be6506c # bug 82228 introduced by ffda7c0 01bb697 80edacc -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
So updates from fontconfig for those who doesn't want to wait for the bugzilla crawler.. Fontconfig 2.11.1 is ancient, and support for demilight has been added in https://bugs.freedesktop.org/show_bug.cgi?id=81453, which ended up in those oddly-numbered releases like 2.11.91 or so. The current

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
gunnarhj: > Want to say, though, that the config file you mentioned in the upstream bug > report doesn't have anything to do with it. It's not in the Ubuntu archive > yet. Umm… The good news is they seen to point to the same problem, and on JeffBai's machine that's almost how the config was

[Touch-packages] [Bug 1556332] [NEW] Playing m4a with gst-launch on Lubuntu Xenial causes stack smashing

2016-03-11 Thread Mingye Wang
Public bug reported: gstreamer0.10-ffmpeg-5ubuntu1~vivid $ gst-launch playbin2 uri=file:///home/wax/sound//.m4a Setting pipeline to PAUSED ... Pipeline is PREROLLING ... *** stack smashing detected ***: /usr/bin/gst-launch-0.10 terminated Aborted (core dumped) ** Affects: gstreamer0.10-ffmpeg

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
gryzzli, see the two links for something about fc-match speed: * https://github.com/adobe-fonts/source-han-sans/issues/85#issuecomment-76082963 * https://bugs.freedesktop.org/show_bug.cgi?id=64766 ** Bug watch added: freedesktop.org Bugzilla #64766

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
Fontconfig bug reported upstream. And again, everything is fine with Noto CJK. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1468027 Title: change default CJK fonts

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
** No longer affects: fontconfig ** Bug watch added: freedesktop.org Bugzilla #94505 https://bugs.freedesktop.org/show_bug.cgi?id=94505 ** Also affects: language-selector via https://bugs.freedesktop.org/show_bug.cgi?id=94505 Importance: Unknown Status: Unknown ** No longer

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
Gave up with fontforge and put the files into https://nodebox.github.io/opentype.js/font-inspector.html. Everything in the font looks perfectly normal now, but I am not sure if it's the good old fontFamily-fontSubfamily & preferredFamily- preferredSubfamily that confused fontconfig. Adding

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
The strange thing with my fontforge (well, some old msys build) is that I can't find any OS/2 table, while https://github.com/googlei18n/noto- cjk/issues/18 clearly mentions something related to os2.usWeightClass. Although doing `grep` still points me to the 'Regular' value in DemiLight, you

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
After asking JeffBai about this, he found out that AOSC OS also had this font weight problem, so I decided to take a look at the font metadata embedded in these fonts. It appears that the all weights have their PS weight set to 'Regular' in NotoSansCJKsc-hinted.zip. The result is basically the

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
(Yeah, fontconfig should work, but what about the apps not using fc?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1468027 Title: change default CJK fonts to Noto

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
Regarding monospace, a +1 for musashi on prepending, since I have seen SHS HW doing terrible at distinguishing 0O 1Il. If someone can verify that these chars don't look bad in Noto Mono CJK, I guess that works too. Note that you should always only prepend half-width fonts, where

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-11 Thread Mingye Wang
Weights shouldn't be 'specified' at all under normal circumstances (like in AOSC OS). Try matching for something like Sans:weight=regular? It should be good if someone can figure out which weight LibreOffice was asking for… -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-01-10 Thread Mingye Wang
happyaron: O again, rendering, rendering, rendering. For systems with TT Bytecode support, be5invis has a release of SHS with his sfdhanautohint (for CJK) and ttfautohint applied called [Inziu]. Follow the link and fetch inziu-20\d{10}. These generally look better on lower ppem sizes (common for

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-01-10 Thread Mingye Wang
My decaying brain… I mean \d{6}. I should just say ‘anything that's not iosevka’. * * * Well the biggest blocker here is actually some application support things. Qt show poor overall handling of some OpenType features used in SHS, the most significant being LOCL used in all those Super files.

[Touch-packages] [Bug 1258778] Re: IBus input candidates not shown in GNOME Fallback session

2015-12-17 Thread Mingye Wang
albertsmuktupavels, at first I thought someone should open a separate bug on GNOME for recording that popup TODO.. Since it's now officially (i.e. by you, a GNOME & Ubuntu Dev) used as the bug that corresponds to this one, I added the remote bug watch. -- You received this bug notification

[Touch-packages] [Bug 1258778] Re: IBus input candidates not shown in GNOME Fallback session

2015-12-16 Thread Mingye Wang
** Also affects: gnome-flashback via https://bugzilla.gnome.org/show_bug.cgi?id=759083 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu.

[Touch-packages] [Bug 1258778] Re: IBus input candidates not shown in GNOME Fallback session

2015-12-06 Thread Mingye Wang
Added gnome-flashback since this may also be aflashback problem if ibus works elsewhere, and salty-horse also reported the non-working status on 14.04 LTS. An upstream flashback bug has been fixed at https://bugzilla.gnome.org/show_bug.cgi?id=759083, but they said it will be a separate problem