unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: [FONTS]: Media Type Specification Changed.
Date: Sun, 10 May 2020 12:13:36 -0400	[thread overview]
Message-ID: <079b58ef-1e0a-be90-7eac-8fbc5a0b79b2@disroot.org> (raw)
In-Reply-To: <87r1vrokcr.fsf@nckx>


[-- Attachment #1.1.1: Type: text/plain, Size: 1825 bytes --]

Hey Tobias!

>> Hello Guix!
> 
> o/
> 
> I haz returned.

Nice! I was wondering what happend to you. ;-)

>> 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.

Never mind, I was researching in the mean time and was about send
another email to ignore my email.

>> 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.

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. But
anyway, before merging I well-tested the patch. It does not affect
anything. What ever is next to /share/fonts/ like /share/fonts/foobar,
font-config finds it correctly. So all good i'd say. :-). Also, I hope
the used acronyms are not confusing.

Regards,
RG.

[-- Attachment #1.1.2: 0xAE6EF3046D6F7B57.asc --]
[-- Type: application/pgp-keys, Size: 2877 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-05-10 16:14 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 [this message]
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=079b58ef-1e0a-be90-7eac-8fbc5a0b79b2@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).