Date: prev next · Thread: first prev next last
March 2020 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=91886

--- Comment #6 from Mike Kaganski <mikekaganski@hotmail.com> ---
(In reply to Heiko Tietze from comment #5)
Which is exactly my argument against shipping fonts that users cannot get
rid of.

How cannot they get rid of them?

All those who don't care about compatibility, use own templates,
don't want the Noto overkill...

So the punch line should have been "Let's drop Noto"?

IMHO the extension solution gives users more freedom.

Fonts-as-extensions is WRONG. You create a font (re)packaging and
(re)distribution infrastructure, where each of those fonts is not created here.
An extension is a creation of its author; it might include something from
outside, but its essence is what is unique in it. A font-as-extension is just
repackaging someone other's work. With possible licensing problems - much more
severe than with current extensions, where each of them has very high chance to
be intellectual property of those who upload them.

And then - you install such an extension, but - suddenly users *are* able to
delete installed fonts using OS features, that are not synchronized with your
extension mechanism. And then you have extensions that are easily broken from
outside.

My take is PLEASE NO FONTS AS EXTENSIONS.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.