On Thu, 27 Apr 2017 17:58:41 +0200, Marguerite Su wrote:
Another option is to install the minimal cjk noto-san-* packages (regular and bold) by upgrading noto-sans-cjk-fonts.rpm. We keep noto-sans-cjk-fonts.rpm but it becomes a meta package requiring only regular and bold CJK fonts. For users who really need the full fontset, we may provide another meta package, e.g. noto-san-cjk-full-fonts or such that drags the all relevant fonts in addition to the mini noto-san-cjk-fonts, but they'll need to install manually.
I changed like this:
* noto-sans-sc-fonts-mini -> noto-sans-sc-fonts * noto-sans-sc-fonts -> noto-sans-sc-fonts-extra
the new 'noto-sans-sc/tc/jp/kr-fonts' contains only regular and bold weights.
the new extra contains all other weights except for regular and bold.
and a new 'noto-sans-cjk-fonts' requires all four noto-sans-sc/tc/jp/kr-fonts.
The '-extra' stuff is open to discuss. I didn't make it a '-full' with regular and bold included because:
1. if so, the '-full' should provide things like 'noto-sans-sc-fonts' which is exactly the new name of the old '-mini' package to avoid the file path conflict.
then there'll be two packages provides the same functionality.
and there'll be choices that need to be handled manually by the users.
How about using the package dependency? That is, - noto-sans-cjk-fonts: containing only regular and bold - noto-sans-cjk-extra/full-fonts: containing the rest of weights, and it has "Requires: noto-sans-cjk-fonts" tag so that it fetches the full set.
2. or if the '-full' set to be conflicted with 'noto-sans-sc-fonts'
If users install '-full', then all the meta packages will be uninstalled.
I will try to hack fonts-config on vacation next week.
I've been working on it here in my fork: https://github.com/marguerite/fonts-config
1. I modified the 'serif' to use 'Noto Serif SC' instead of 'AR PL UMing' by default
2. I left the 'Noto Sans CJK SC' there in 59-*.conf
But since we will not use Super OTC or Language Specific variants any more, these font names will be non-existent actually.
I thought the font (family) names don't change after split? If so, the workaround is still needed when multiple CJK fonts are installed, I'm afraid.
The font family changed actually.
Before: (Super OTC)
The font families are 'Noto Sans CJK SC'.
Now:
The font families are 'Noto Sans SC'
Aha, interesting. When I took a look at the individual *.otf file in the past, it still showed Noto Sans CJK XX. Maybe it was changed since then?
That's why I said 'Noto Sans CJK SC' now doesn't exist on our system, it's a dummy font.
Then I used 'Noto Sans SC/TC/JP/KR' combination to fake it, see:
https://github.com/marguerite/fonts-config/blob/master/32-google-noto-cjk.co...
So:
1. If users install Super OTC themselves, that font family is available and will be used. of course the problems are still the same as before, but they choose to bear with it.
Well, the "Noto Sans CJK XX" will still appear when user installs OTC or the old OTF independently, so it's not too bad to keep it. It's harmless for now, unless such a font is installed, right?
2. If users use our packages.
2.1 on a localized system, he'll get the right order.
2.2 on a Latin system with all the fonts installed. He'll get the order in 60-family-prefer.conf.
If he didn't want Japanese glyths he can just uninstall noto-sans-jp-fonts or change the order by himself.
compared with the situation before, he can at least get what he wants to see by uninstalling package he doesn't need.
3.2 modern symbol font (what's the difference between emoji font and symbol font? are they the same?)
Conceptually yes. The difference is how they were invented and introduced to unicode :)
So?
I took a look at the fontconfig configuration to correctly display emoji on the screen, it looks like the emoji fonts were treated as the 1st choice for 'sans-serif'.
Do we still need to append these emoji fonts to 'symbol'?
Heck, I have also little idea about the fontconfig hack for emoji, too, so far...
BTW, the SR for the noto emoji font addition has been blocked because of the current noto-cjk rework. Let's rip if out from google-noto-fonts quickly, then improve fontconfig stuff.
Yes, I see and I agree.
The google-noto-fonts SR can be accepted first to make a way for the following SRs
It doesn't nothing but remove CJK.
OK, let's start with that. But maybe it's safer to keep it in M17N:fonts until the rest is worked out. Then we can submit all to FACTORY at once. (The only important thing is not to forget the procedure :)
Sounds like a good idea.
Yes. but I still don't know how to use a certain weight of a font to provide another weight of another font, eg:
Adobe Source Han Sans Light (200 weight) == Google Noto Sans CJK Light (300 weight)
So how to do the math to make a 200 weight Noto Sans CJK Light to provide the former?
Is there any 'scale' function for fontconfig?
I guess no such support, and possibly we'll have to write up the matching manually by hands...
3.4 re-evaluate the choicesin 60-family-prefer.conf
For example, we still have Wenquanyi Zen Hei in the preference of 'sans-serif', and those 'Shanghai Song Uni' and 'AR PL'
What are they? are they still installed on openSUSE by default?
I don't think so. It was some commercial fonts which was installed as default on SLE10 or such.
I see. but are you sure there're still people using SLED 10?
Maybe not, but the fonts may be still present.
Because the SLES just have TTYs which doesn't support CJK at all.
Hm? SLES is with GNOME desktop, even as default.
So at least the ancient open source CJK fonts can be cleaned up.
Yes, I have no objection for the cleanup, just explained where it came from. Please go head. thanks, Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org