unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: Tom Balzer <tbalzer@ksu.edu>
Cc: guix-devel@gnu.org
Subject: Re: LibreOffice Fonts
Date: Thu, 28 Sep 2017 08:12:04 +0000	[thread overview]
Message-ID: <20170928081204.t3rigpdbaeptgpvp@abyayala> (raw)
In-Reply-To: <87ing320p6.fsf@ksu.edu>

[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]

Tom Balzer transcribed 1.2K bytes:
> 
> ng0 writes:
> 
> > I have a problem with making decision on default fonts. What if someone
> > doesn't want gnu-freetype-ttf? It is not just only this font, you can use
> > any font and sometimes this will depend on fc-cache -fv which is mentioned
> > in the documentation.
> 
> By 'in the documentation', do you mean the documentation for how fonts
> work in guix, or libreoffice's documentation? If the latter, then yes I
> see that you could start libreoffice with a gtk theme definition
> to control the fonts, allowing for other font choices. But in the case
> where one just launched libre office, wouldn't you expect that it
> 'works' running out of just the package files? If you include no font
> that wouldn't work, which seems like sacrificing basic functionality in
> order to avoid including a font that someone might not desire.
> 
> Couldn't that argument be made for any features above bare minimum for
> any application?

No, that's something entirely different from propagating fonts.

> For instance, someone might not want a support library
> for emacs that enables viewing jpegs, but the default package supports
> this. I think that removing a feature from a package definition if you
> don't want a feature makes more sense than crippling a package with
> non-sane defaults.
> 
> Tom
> 


I think you want to read past discussions on this still open problem:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26877
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18640
-- 
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 --]

  reply	other threads:[~2017-09-28  8:12 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 [this message]
2017-10-02 14:48 ` Ludovic Courtès
2017-10-02 15:05   ` ng0
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=20170928081204.t3rigpdbaeptgpvp@abyayala \
    --to=ng0@infotropique.org \
    --cc=guix-devel@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).