From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: [FONTS]: Media Type Specification Changed.
Date: Sun, 10 May 2020 20:09:11 +0200 [thread overview]
Message-ID: <87d07boe60.fsf@nckx> (raw)
In-Reply-To: <079b58ef-1e0a-be90-7eac-8fbc5a0b79b2@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
Raghav,
Raghav Gururajan 写道：
> Nice! I was wondering what happend to you. ;-)
The bad things. All of them. In order.
> No, my goal was to enable other types. I happened to update it
> like that
> and assumed I did it correctly when I came across this MIME
> thing.
You did fine, only renaming ‘truetype’ -> ‘ttf’ should have been
separate. If it had been, I don't think it would have been
merged. Also omitting it from the change log feels... sneaky,
while I'm sure that wasn't your intention.
Writing commits (*including* the diff) firstly for humans is
important! Even if it feels tedious and you really really want to
git commit -a.
Anyway: since ‘share/fonts/ttf’ makes font-gnu-freefont
inconsistent with our other fonts[0] for little reason I'd like to
revert it back to ‘truetype’ & change ‘share/fonts/otf’ to
‘opentype’ as well. What do you think?
(Not sure what to do with ‘woff’ so I won't touch it.)
> But anyway, before merging I well-tested the patch. It does not
> affect
> anything.
I know :-) Fontconfig doesn't care about the subdirectory names,
it just scans them all. The names are for humans. All the more
reason not to abbreviate them IMO.
Kind regards,
T G-R
[0]: At least the ones I have installed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-10 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 14:41 [FONTS]: Media Type Specification Changed Raghav Gururajan
2020-05-10 15:55 ` Tobias Geerinckx-Rice
2020-05-10 16:13 ` Raghav Gururajan
2020-05-10 18:09 ` Tobias Geerinckx-Rice [this message]
2020-05-11 4:11 ` Raghav Gururajan
2020-05-13 16:13 ` Tobias Geerinckx-Rice
2020-05-13 19:04 ` Raghav Gururajan
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=87d07boe60.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=raghavgururajan@disroot.org \
/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).