Date: prev next · Thread: first prev next last
January 2013 Archives by date, by thread · List index


On 24/01/13 21:15, Rene Engelhard wrote:
On Thu, Jan 24, 2013 at 10:56:29AM -0600, Adolfo Jayme Barrientos wrote:
On Thu, Jan 24, 2013 at 4:57 AM, Rene Engelhard <rene@debian.org> wrote:

Yeah, For that reason it's /supposed to be in) non-free in Debian, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603157.

We shouldn't include non-free stuff here.

Yeah, it’s considered “non-free” by Debian, but we can apply the same
logic to the other “non-free” fonts added to LibreOffice, such as Open
Sans, Source {Code|Sans} Pro and PT Serif. But instead of removing

Err, you want to tell me we already have them in the sources?

it appears so, see
more_fonts/UnpackedTarball_{opensans,ptserif,sourcecode,sourcesans}.mk

but it can be disabled via --without-fonts

these from shipping in LibreOffice, Debian packaging should be the
place where these fonts are removed. Because its *Debian policy* which
should not obstaculize LibreOffice from shipping fonts to Windows.

Erm, you forgot this is a OSS project (aka "free software" for those who
don't like "free"[1]). So we must not ship them either.

hmm... if the problem is "can only be built from source with non-free
tools", then i'm afraid we've got a few components in extensions/ that
can only be built with MSVC, not with MinGW, and of course the Windows
binaries also bundle non-free MSVC runtime.



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.