From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Tom Balzer <tbalzer@ksu.edu>
Subject: Re: LibreOffice Fonts
Date: Mon, 2 Oct 2017 15:05:04 +0000 [thread overview]
Message-ID: <20171002150504.73bagyq4hrmx22ip@abyayala> (raw)
In-Reply-To: <87bmlpppv6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
Ludovic Courtès transcribed 1.8K bytes:
> Hello Tom,
>
> Tom Balzer <tbalzer@ksu.edu> skribis:
>
> > 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.
>
> Every character in the body of the text, or every character in the UI?
>
> > From the manuals description of 'propagated-inputs', it seems like
> > this font package would fit the use case:
> >
> >> Lastly, ‘propagated-inputs’ is similar to ‘inputs’, but the
> >> specified packages will be automatically installed alongside
> >> the package they belong to (*note ‘guix package’:
> >> package-cmd-propagated-inputs, for information on how ‘guix
> >> package’ deals with propagated inputs.)
> >>
> >> 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 ‘Requires’ field.
> >
> > I asked on #guix, and one argument against including fonts in propagated
> > 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.
>
> I think it’s a borderline case. In a sense, the font is additional
> material used as input by LO (and indeed LO is much less useful without
> it, but it’s still LO), though I can also understand the other argument.
>
> My current inclination would be the status quo. Otherwise we’d have to
> worry about fonts and artwork for Abiword, Inkscape, etc. as well.
>
> Thoughts?
>
> Ludo’.
>
>
What about an fontcache-service that basically
is mcron running daily "fc-cache -f"
or even "fc-cache -fr"?
That would be the closest to a post-setup hook
refreshing font caches like people could be used
to from Archlinux etc.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-02 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 21:15 LibreOffice Fonts Tom Balzer
2017-09-27 22:41 ` ng0
2017-09-27 23:15 ` Tom Balzer
2017-09-28 8:12 ` ng0
2017-10-02 14:48 ` Ludovic Courtès
2017-10-02 15:05 ` ng0 [this message]
2017-10-02 22:57 ` Maxim Cournoyer
2017-10-04 14:12 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171002150504.73bagyq4hrmx22ip@abyayala \
--to=ng0@infotropique.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=tbalzer@ksu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).