unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 17:55:32 +0200	[thread overview]
Message-ID: <87r1vrokcr.fsf@nckx> (raw)
In-Reply-To: <392d5303-ff41-0f76-fccc-0649bc10b0f3@disroot.org>

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

Raghav,

Raghav Gururajan 写道:
> Hello Guix!

o/

I haz returned.

> As of 2017, IANA (www.iana.org) has changed the standard 
> template for
> font media types.
>

Not so much changed, but that there was previously no standard. 
The W3C was displeased with the proliferation of ad-hoc, 
inconsistent font MIME types and created [SOURCE].

> So, font/freetype and font/opentype has to be updated to 
> font/ttf and
> font/otf, respectively.

For people who deal with MIMEs, yes, but how does this affect a 
package manager like Guix?  We don't.

> Almost all font packages in guix, are using the old 
> specification.

Where?

> I have updated font-gnu-freefont a while ago. We need to update 
> other
> packages. Any ideas on how to change them all in a time-saving 
> way?

Are you talking about 5483a2d0a913fe533744699e9ef5757c6e3f6983?

Aside... I know others have mentioned this before, and this is 
another example of a commit that should have been split.  It 
silently moves the TTF fonts from /share/fonts/truetype to 
/share/fonts/ttf for reasons that aren't explained anywhere and 
aren't related to the stated goal.

Was this RFC the reason?  If so you're confusing two unrelated 
things.

  $ ls ~/.guix-profile/share/fonts
  cantarell/  opentype/  truetype/

(Seeing this I might change cantarell to use ‘opentype’, or not, 
because it's purely a matter of taste.)

These directory names are for humans.  I think ‘truetype’ was 
better than ‘ttf’.

Kind regards,

T G-R

> [SOURCE]: 
> https://www.iana.org/assignments/media-types/media-types.xhtml#font

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-05-10 15:55 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 [this message]
2020-05-10 16:13   ` Raghav Gururajan
2020-05-10 18:09     ` Tobias Geerinckx-Rice
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=87r1vrokcr.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).