https://bugs.documentfoundation.org/show_bug.cgi?id=172824
--- Comment #9 from V Stuart Foote <[email protected]> --- (In reply to Heiko Tietze from comment #8) > Noto _feels_ wrong to me, so a weak -1 from my side. Assuming we change the > default, does it mean to not bundle Liberation anymore (the packed tarball > takes 2.3MB)? Guess we run into layout issues for old documents then. Wrong how? Red Hat is effectively out of the game, and their IBM leadership would probably prefer a broader move over the their Plex superfamily font offering (it is SIL OFL). They certainly have no interest in further efforts on Liberation font. Liberation v.2 along with Google's CrOS Extra (Chrome OS extra fonts--Carlito (for Calibri) and Caladea (for Cambria)) should absolutely remain included. They still are the best metric equivs to the MS Office suite delivered fonts, with suitable SIL OFL. But then the Chrome folks have not moved at all on an Aptos metric equiv font--so stalled there. While the proposed TDF tender funding for work an Aptos equiv font was shelved. Should note that Aptos actually reduced its Unicode coverage, and MS deploys more regional font families appropriate to supported locales. So, the question for LO becomes what would be the most functional for users, and secondly would be most likely to fit with os/DE we support. In that context, IMNSHO a clear choice is the Noto Superfamily (including its CJK and indic support) fully under SIL OFL and available to distribute--or steer users toward. Conversely Adobe's Source family offerings have large gaps, Liberation is done at v.2 with large gaps, DejaVu, also done, has large gaps. And I think any promotion of IBMs Plex superfamily (admittedly with similar coverage to Noto) would just be too hard a pill to swallow for users. -- You are receiving this mail because: You are the assignee for the bug.
