Set to untested for now.
It removes the "NotoMono" font as that one is deprecated in favour
of "NotoSansMono".
Problem: When using this with the "NotoSansMono" font, Appearance
prefs doesn't find the new mono font.
The previous recipe used imprecise pattern matching which led to some
important fonts being put in the regional package. This in turn led to
missing block characters in Terminal, breaking our progress bars, for
example.
* Noto: remove the UI variants. According to the FAQ [1]:
"The UI fonts were initially prepared for use in Android’s UI. They
have tighter vertical metrics, and some glyphs that would be clipped
are redrawn to fit within the constrained space."
As they look pretty much identical to the non-UI versions, we'll
keep them out of the package for the time being. If we see any clipping
they could be re-added (or put in their own sub-package).
* Noto CJK: put the Japanese CJK in a correctly named sub-package.
The 'main package' (declared in PROVIDES) is emtpy and shouldn't be
uploaded to a repo. Haikuporter could be changed to not create a
package, if the PROVIDES is empty.
[1] https://github.com/googlei18n/noto-fonts/blob/master/FAQ.md
The older recipe doesn't build anymore.
This recipe builds 4 packages:
noto_sans_cjk_tc-1.004-1-any.hpkg
noto_sans_cjk_sc-1.004-1-any.hpkg
noto_sans_cjk_kr-1.004-1-any.hpkg
noto_sans_cjk-1.004-1-any.hpkg
All packages contain the glyphs for all 4 languages, only differ in
which is the "default" (also determines the title shown in font list,
e.g. "Nano Sans CJK JP"), if I understand it correctly.
The last plain "noto_sans_cjk" hpkg contains the Japanese default.
I couldn't get the recipe to build a package "noto_sans_cjk_jp" without
ending up with an empty "noto_sans_cjk" which has to be build to reflect
the recipe name.
It's not a big problem IMO, since a custom title "Noto Sans CJK Japanese"
can be set at the HaikuDepot webserver.
Feel free to improve the recipe or suggest changes I should work on.
