Re: Adding text/org MIME type to jshttp/mime-db

[Max Nikulin <manikulin@gmail.com>]

On 02/08/2024 02:55, Joseph Turner wrote:
> Support for "text/org" in <https://github.com/jshttp/mime-db> would let
> the Agregore browser (<https://agregore.mauve.moe/>) render Org files.
> Then hyperdrive.el users could share Org files to be viewed in Agregore.
> 
> John Kitchin opened a PR back in 2017, which was rejected:
> 
> https://github.com/jshttp/mime-db/pull/82
[...]
>> I would suggest opening a new PR.
[...]
> I'd like to open a new PR.  Would you elaborate on "de facto mimetype"?

Nothing more than my opinion:

I think, if you are going to convince somebody outside of Org community 
then you should mention that the format is supported by GitHub and 
GitLab. Org files are rendered using org-ruby gem. Only a part of 
features is available, but still useful.
<https://github.com/github/markup/>

shared-mime-info used by Linux desktop applications has .org text/org 
association:
<https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/data/freedesktop.org.xml.in>
(though text/x-org alias and -*- mode: org -*- magic are missed).
Thunderbird sends .org attachments as text/org without explicit 
configuration.

Till finalizing of https://orgmode.org/worg/org-syntax.html and writing 
spec (RFC) there is no point to send a request to IANA.

Emacs will continue to use text/x-org till somebody manages to convince 
developers that transition to text/org does not break backward compatibility
<https://debbugs.gnu.org/68687>
Actually Emacs will continue to use application/vnd.lotus-organizer in 
some cases since to /etc/mime.types has higher priority.

I am not familiar with Agregore, but my opinion that media type 
associations should be configurable in applications and either 
shared-mime-info or /etc/mime.types should has higher priority than any 
built-in mapping, perhaps besides some exceptions for media types 
directly related to the application.