Overview
Request 1069566 accepted
- Revert back to efont-unicode-bitmap-fonts from babelstone-han-fonts.
The latter are apparently broken for Japanese at least.
- Fix changelog entries with invalid format.
- fix: reintroduce efont-unicode-bitmap-fonts so that there is a fallback
- feat: Add noto-fonts and noto-sans-cjk-fonts to fonts_opt pattern
- remove: efont-unicode-bitmap-fonts and google-droid-sans from fonts_opt pattern
- fix: rpmlintrc filter, no-binary is now an error rather than warning
- Created by favogt
- In state accepted
- 6 package maintainers
Request History
favogt created request
- Revert back to efont-unicode-bitmap-fonts from babelstone-han-fonts.
The latter are apparently broken for Japanese at least.
- Fix changelog entries with invalid format.
- fix: reintroduce efont-unicode-bitmap-fonts so that there is a fallback
- feat: Add noto-fonts and noto-sans-cjk-fonts to fonts_opt pattern
- remove: efont-unicode-bitmap-fonts and google-droid-sans from fonts_opt pattern
- fix: rpmlintrc filter, no-binary is now an error rather than warning
jengelh accepted request
See https://old.reddit.com/r/openSUSE/comments/11h16uc/opensuse_broke_japanese_font_rendering_in_a/
It did change in appearance inasfar as that it's now a serif instead of a sans-serif font, and one where kana occupy less of the square box than kanji would. It ain't broken, but it's a bad tradeoff.
Is the removal of google-droid-sans space related? Its Monospace font is preferred by alot of people over the other google / adobe fonts.
(I am not involved in the original pattern change, but curious nevertheless)
https://www.reddit.com/r/typography/comments/480zna/what_are_differences_between_notodroid_and_open/
So if Noto is Droid + more glyphs, that seems sensible. It's just that there is no(?) Noto Mono, and the packaging of droid does not allow for droid-mono to be separately installed.