Re: [RFC]refactor Noto CJK fonts packaging

 > But it's *really* just one font name with one weight. there's no 's' case in it.

There are many font packages ending with "-fonts" and containing only one font.

 > why?

just a rule.
https://en.opensuse.org/openSUSE:Packaging_Fonts

 > why? because it's stripped from the language specific tarballs and
 > contains all CJK support?
 >
 > the old name was 'noto-sans-mono-cjksc-fonts' (but I think it should
 > be 'noto-mono-cjksc-fonts')

According to the naming rule above, package names should come from family names.
The family name is "Noto Sans Mono CJK SC" and not "Noto Mono CJK SC".

# we can also say noto-mono-cjksc is project name although a bit strange.


 > the later is a minimal alternative of the former.

That's just a meta package providing a part of them.
So I think we cannot say it is alternative (similar but different one).

If you intend to minimize Noto fonts by removing the old package,
it would be fine.


 > BTW now I can be sure that if you install noto-sans-jp-fonts-mini, the
 > old noto-sans-cjk-fonts
 > will be uninstalled. But I didn't find a way to update
 > noto-sans-cjk-fonts and install noto-sans-jp-fonts-mini
 > automatically accordingly. I wonder can it be called 'smooth update'?

I don't think so. We will need to ask "manual update" in the release note.
So, usually, we have to provide noto-sans-cjk-fonts that provides the same font set
for the upgrade compatibility issue.

See the previous discussion.


 > PS: I think I should also make the noto-sans-jp-fonts-mini conflicts
 > with noto-sans-jp-fonts
 > because they both have regular and bold weights. the later should
 > provide the former.

Since they are meta package, so it is no problem, I think.

On 2017/04/27 0:25, Marguerite Su wrote:
> Hi, ftake
>
> On Wed, Apr 26, 2017 at 10:18 PM, Fuminobu TAKEYAMA <[email protected]> wrote:
>> 1. Package naming
>> - According to font package naming rule, the prefix is not "-font" but
>> "-fonts"
>
> But it's *really* just one font name with one weight. there's no 's' case in it.
>
> I didn't make the 'noto-sans-sc-fonts' wrong...
>
>> - "noto-sans-*-mono-fonts" should be "noto-sans-mono-cjk-*" from the naming
>> rule?
>
> why? because it's stripped from the language specific tarballs and
> contains all CJK support?
>
> the old name was 'noto-sans-mono-cjksc-fonts' (but I think it should
> be 'noto-mono-cjksc-fonts')
>
> but since I decided to use region specific variants, the 'cjksc' is no
> longer a proper name
> although it *correctly* reflects the fact that these monospace fonts
> cover all CJK locales.
>
> anyway this is open to discuss because they're not installed by default.
>
> they'll be dragged in only if the end users install
> 'noto-sans-sc-fonts' themselves.
>
>> - I am wondering if the prefix "-mini" is appropriate for our case.
>>   It is used, for example, in "systemd-mini", as an minimal *alternative* of
>> the package
>>   without "-mini".
>
> Ha, yes, noto-sans-sc-fonts contains all weights and
> noto-sans-sc-fonts-mini contains
> regular and bold weights. the later is a minimal alternative of the former.
>
> the later and those two weights can be put into the DVD, leaving everything else
> in the remote repository.
>
>> 2. Meta packages
>> - I am not sure "noto-sans-cjk-*-fonts-mini" meta packages are really
>> necessary.
>> - We need noto-sans-cjk-fonts package, which "Requires" all those fonts for
>> upgrading
>>   (even though this requires much disk space)
>
> I stripped the packages just to make sure every locale has it's own
> meta package.
>
> There's no space for another mega package (or it can exist but not
> exist in DVD so
> that a default localized installation will not install all other fonts
> for other languages)
>
> BTW now I can be sure that if you install noto-sans-jp-fonts-mini, the
> old noto-sans-cjk-fonts
> will be uninstalled. But I didn't find a way to update
> noto-sans-cjk-fonts and install noto-sans-jp-fonts-mini
> automatically accordingly. I wonder can it be called 'smooth update'?
>
> PS: I think I should also make the noto-sans-jp-fonts-mini conflicts
> with noto-sans-jp-fonts
> because they both have regular and bold weights. the later should
> provide the former.
>
>> - The meta packages does not need "%reconfigure_fonts_prereq"
>
> Sure.
>
>> 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.
>
> So I prepend/append the 'Noto Sans SC' stuff in 32-google-noto-cjk.conf to fake
> a font (although I don't know if my fontconfig grammar is correct, please help).
>
> I didn't use 'alias' because in certain cases users may make those namespaces
> available by installing those variant themselves.
>
> The same policy should be applied to serif too.
>
> 3. I have a TODO in my fork, you can check that. it's the goal we need to do:
>
> 3.1 *colored* emoji support out of the box (50-emoji.conf and a cairo patch)
>
> https://github.com/googlei18n/noto-emoji/issues/36
>
> 3.2 modern symbol font (what's the difference between emoji font and
> symbol font? are they the same?)
>
> Deepin project have a 'deepin-opensymbol-fonts' which is 6 fonts that
> provide 'MT Extra' 'Webdings'
> 'Wingding' 'Wingding 2' and two other symbol fonts on M$.
>
> So it's a 100% alternative. we don't need to rely on the ancient one
> from LibreOffice
>
> 3.3 Adobe Source Hans vs. Google Noto CJK.
>
> They're actually the same with minor difference. eg: the weight.
> https://qdan.me/list/VLPe5sfsxkFWYMmX
>
> And Source Hans has a 'HW( half weight )' weight available only in its
> language specific variants.
>
> So I think we should use fontconfig to provide Adobe Source Hans as we can.
>
> And only package those missing weights.
>
> But I didn't start working on this at all.
>
> 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?
>
> our system fontconfig is not a trash...we shouldn't put everything here.
>
> we should just have a working one, no need to prefer so many ancient
> things that few knows today.
>
> I think we can have a start by cleaning CJK substitutes.
>
>
> Because I will not be available from April. 28th to May 1st. (National
> Holiday leave).
>
> So please just step in the any of these topics and send pull requests
> to openSUSE/fonts-config
> when you're ready.
>
> Marguerite
>
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]