From mboxrd@z Thu Jan  1 00:00:00 1970
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: LibreOffice Fonts
Date: Mon, 02 Oct 2017 18:57:07 -0400
Message-ID: <87d1652m64.fsf@gmail.com>
References: <8760c3g7w9.fsf@ksu.edu> <87bmlpppv6.fsf@gnu.org>
	<20171002150504.73bagyq4hrmx22ip@abyayala>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34791)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <maxim.cournoyer@gmail.com>) id 1dz9eD-0002lh-EH
	for guix-devel@gnu.org; Mon, 02 Oct 2017 18:57:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <maxim.cournoyer@gmail.com>) id 1dz9eA-0003HY-4A
	for guix-devel@gnu.org; Mon, 02 Oct 2017 18:57:13 -0400
In-Reply-To: <20171002150504.73bagyq4hrmx22ip@abyayala>
	(ng0@infotropique.org's message of "Mon, 2 Oct 2017 15:05:04 +0000")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org, Tom Balzer <tbalzer@ksu.edu>

ng0 <ng0@infotropique.org> writes:

> Ludovic Court=C3=A8s transcribed 1.8K bytes:
>> Hello Tom,
>>=20
>> Tom Balzer <tbalzer@ksu.edu> skribis:
>>=20
>> > Recently I installed libreoffice in my user profile, and found that all
>> > menus require the package 'font-gnu-freetype-ttf' in order to render
>> > correctly. Without this package, every character was rendered as a
>> > rectangle indicating a missing font.
>>=20
>> Every character in the body of the text, or every character in the UI?
>>=20
>> > From the manuals description of 'propagated-inputs', it seems like
>> > this font package would fit the use case:
>> >
>> >> Lastly, =E2=80=98propagated-inputs=E2=80=99 is similar to =E2=80=98in=
puts=E2=80=99, but the
>> >> specified packages will be automatically installed alongside
>> >> the package they belong to (*note =E2=80=98guix package=E2=80=99:
>> >> package-cmd-propagated-inputs, for information on how =E2=80=98guix
>> >> package=E2=80=99 deals with propagated inputs.)
>> >>=20
>> >> For example this is necessary when a C/C++ library needs
>> >> headers of another library to compile, or when a pkg-config
>> >> file refers to another one via its =E2=80=98Requires=E2=80=99 field.
>> >
>> > I asked on #guix, and one argument against including fonts in propagat=
ed
>> > inputs is to avoid packaging the font when 'pack'ing for another
>> > system. This to me is really an argument for including the fonts, since
>> > there is no guarantee that the other system is 'rational', so to
>> > speak. To create totally portable packages I would think including this
>> > font required to render the menus would make sense.
>>=20
>> I think it=E2=80=99s a borderline case.  In a sense, the font is additio=
nal
>> material used as input by LO (and indeed LO is much less useful without
>> it, but it=E2=80=99s still LO), though I can also understand the other a=
rgument.
>>=20
>> My current inclination would be the status quo.  Otherwise we=E2=80=99d =
have to
>> worry about fonts and artwork for Abiword, Inkscape, etc. as well.
>>=20
>> Thoughts?
>>=20
>> Ludo=E2=80=99.
>>=20
>>=20
>
> What about an fontcache-service that basically
> is mcron running daily "fc-cache -f"
> or even "fc-cache -fr"?

Is there no way to provide it the way it should, i.e. as a
profile hook? I understand the issue that the cache generated would be
read-only, but that cache would be in the system and users running
fc-cache themselves would produce cache in their $HOME, so I don't
immediately see an issue there (other than I haven't had time yet to
look into it -- it's on my TODO).

Maxim