add fonts to related language addons

[AlwinEsch]

Description

This adds some TTF files in order to have the corresponding character type for upcoming changes in Kodi in the respective language.

The background is that Kodi does not support the characters in very many languages and could only be fixed in a few using "Arial.ttf".
Think about relocating it here, as it is needed in the respective language and so as not to flood Kodi when everyone was in it.

Checklist:

• My code follows the add-on rules and piracy stance of this project.
• I have read the CONTRIBUTING document
• Each add-on submission should be a single commit with using the following style: [plugin.video.foo] v1.0.0

Additional information :

• Submitting your add-on to this specific branch makes it available to any Kodi version equal or higher than the branch name with the applicable Kodi dependencies limits.
• add-on development wiki page.
• Kodi pydocs provide information about the Python API
• PEP8 codingstyle which is considered best practice but not mandatory.
• This add-on repository has automated code guideline check which could help you improve your coding. You can find the results of these check at Codacy. You can create your own account as well to continuously monitor your python coding before submitting to repo.
• Development questions can be asked in the add-on development section on the Kodi forum.

[AlwinEsch]

About the other fonts I created:

• https://github.com/AlwinEsch/resource.font.excluded
• https://github.com/AlwinEsch/resource.font.limited
• https://github.com/AlwinEsch/resource.font.active

Because of the "resource.font.active" has to be kept under observation a little (if moved to Kodi), if the associated language comes in here, it would have to be moved from there to here.

[gade01]

How will this work when skins provide the fonts?
Will these fonts provided with the language addons override the fonts provided with the skins?

[AlwinEsch]

The skin is always as primary, only in case the wanted character becomes not found there, does it a fallback to this ones on language addons.

See on https://github.com/AlwinEsch/kodi/blob/fix-estuary-strings/xbmc/guilib/GUIFontTTF.cpp#L1231-L1233
The m_fontMain there relates to them where skin bring/selected.

[gade01]

@AlwinEsch That sounds really great.
I have been struggeling with adding fonts for several languages not using regular characters for years.
So this is a great solution! ;)

[AlwinEsch]

Is updated and also added on second commit, additional font addons to allow Kodi in his use case the availability.

[AlwinEsch]

This is added new to get on zh_tw and ja_jp the font file from zh_cn where contains mostly all.

Bad is that on NotoSansJP-Regular.ttf and NotoSansTC-Regular.ttf also some where not on other, thats why also inside here another one.

[gade01]

@AlwinEsch What is required for this PR to get merged?
Core support?

[AlwinEsch]

How we see the state about this? Maybe we can bring in and have ready for the request in Kodi?

@gade01 It can be come in before. The fonts inside here, then currently not used, but prepared for the request in Kodi (xbmc/xbmc#20552)

[gade01]

It looks great to me, but perhaps I'm not the right person to review this. :)

[enen92]

@AlwinEsch please check addon-checker errors, it looks like the icons you specify on addon.xml do not exist.
I am also wondering if the font files should not be font addons instead, and those font addons specified as dependencies for the language addons

[scott967]

I tested these for the CJK variants back when the core PR was fresh and the language resources did work as expected. Not sure anything gained by splitting out the fonts as the way the fonts are designed is language-specific. Unless a skin/addon provides complete coverage in a skin-provided font, then the language font is not needed. I think xbmc/xbmc#20552 needs a rebase to really test this again?

[AlwinEsch]

@AlwinEsch please check addon-checker errors, it looks like the icons you specify on addon.xml do not exist. I am also wondering if the font files should not be font addons instead, and those font addons specified as dependencies for the language addons

About the reason to combine the font with language is mainly to have on language switch immediately the needed font available, without it can come that the language is switched and user becomes asked for font and not readable then.
But I look with font add-on as dependency of language add-on, maybe it works.

I make on next days a rebase about the font pull requests and to become ready for use.