From: Max Nikulin <manikulin@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>,
Stefan Kangas <stefankangas@gmail.com>
Cc: 68687@debbugs.gnu.org
Subject: bug#68687: [PATCH] Use text/org media type
Date: Fri, 26 Jan 2024 17:52:40 +0700 [thread overview]
Message-ID: <bf5f4296-7b08-4baf-a93d-3d2bde489bf8@gmail.com> (raw)
In-Reply-To: <87h6j1f08d.fsf@localhost>
On 26/01/2024 06:43, Ihor Radchenko wrote:
> However, AFAIU, text/org will fall into "standards tree" in IANA media
> type specification, which means that it MUST be registered,
>
> Registering text/org media type requires syntax spec. We are
> still working on format Org mode syntax specifications.
You a right. I was confused reading rfc6648 that registration procedure
had been simplified to deprecate x- prefixes. In addition, I did not
realize that application/vnd.lotus-organizer was registered without
format specification because this type belongs to the vendor tree, not
standards one.
https://www.iana.org/assignments/media-types/application/vnd.lotus-organizer
I do not think it is reasonable to use a type like text/vnd.gnu.emacs.org.
Even with format specification, I am afraid, .org file name suffix may
be an obstacle. Likely it is necessary to contact IBM and to ask them
concerning registration of Lotus. In the optimistic scenario they may
declare Lotus-related media types as obsolete since the product is
discontinued.
Changing of file name suffix for Org would be more painful than updating
emacs to use text/org instead of text/x-org.
next prev parent reply other threads:[~2024-01-26 10:52 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 13:56 Org mode MIME type Max Nikulin
2024-01-21 15:11 ` Timothy
2024-01-22 16:21 ` Max Nikulin
2024-01-24 14:43 ` bug#68687: [PATCH] Use text/org media type Max Nikulin
2024-01-25 23:10 ` Stefan Kangas
2024-01-25 23:10 ` Stefan Kangas
2024-01-25 23:43 ` Ihor Radchenko
2024-01-26 7:40 ` Eli Zaretskii
2024-01-26 7:40 ` Eli Zaretskii
2024-01-26 14:00 ` Ihor Radchenko
2024-01-26 14:00 ` Ihor Radchenko
2024-01-26 10:52 ` Max Nikulin [this message]
2024-01-30 19:39 ` Stefan Kangas
2024-01-30 19:39 ` Stefan Kangas
2024-01-30 20:34 ` Ihor Radchenko
2024-01-30 20:34 ` Ihor Radchenko
2024-01-25 23:43 ` Ihor Radchenko
2024-01-26 7:23 ` Eli Zaretskii
2024-01-26 7:23 ` Eli Zaretskii
2024-01-26 10:39 ` Max Nikulin
2024-01-26 12:22 ` Eli Zaretskii
2024-01-31 16:30 ` Max Nikulin
2024-01-31 16:30 ` Max Nikulin
2024-01-27 3:38 ` Richard Stallman
2024-01-28 16:35 ` Max Nikulin
2024-01-28 16:35 ` Max Nikulin
2024-01-28 16:47 ` Eli Zaretskii
2024-01-30 3:56 ` Richard Stallman
2024-01-30 12:13 ` Ihor Radchenko
2024-01-30 12:13 ` Ihor Radchenko
2024-01-30 17:12 ` bug#68687: Org mode code evaluation (was: bug#68687: [PATCH] Use text/org media type) Mike Kupfer
2024-01-30 17:12 ` Mike Kupfer
2024-01-30 17:51 ` bug#68687: " Ihor Radchenko
2024-01-30 17:51 ` Ihor Radchenko
2024-02-02 3:38 ` bug#68687: " Richard Stallman
2024-02-02 3:38 ` Richard Stallman
2024-02-02 4:58 ` bug#68687: Org mode code evaluation Max Nikulin
2024-02-02 4:58 ` Max Nikulin
2024-02-02 16:10 ` bug#68687: Org mode code evaluation (was: bug#68687: [PATCH] Use text/org media type) Ihor Radchenko
2024-01-31 16:18 ` bug#68687: [PATCH] Use text/org media type Max Nikulin
2024-01-31 16:18 ` Max Nikulin
2024-01-31 16:32 ` Ihor Radchenko
2024-01-31 16:32 ` Ihor Radchenko
2024-02-02 3:40 ` Richard Stallman
2024-02-02 7:15 ` Eli Zaretskii
2024-02-02 7:15 ` Eli Zaretskii
2024-02-02 3:40 ` Richard Stallman
2024-01-30 12:52 ` Eli Zaretskii
2024-01-30 12:52 ` Eli Zaretskii
2024-01-30 3:56 ` Richard Stallman
2024-01-28 16:47 ` Eli Zaretskii
2024-01-27 3:38 ` Richard Stallman
2024-01-31 20:00 ` Stefan Kangas
2024-01-31 20:00 ` Stefan Kangas
2024-02-01 10:40 ` Max Nikulin
2024-02-01 10:40 ` Max Nikulin
2024-02-02 7:09 ` Stefan Kangas
2024-02-02 7:09 ` Stefan Kangas
2024-02-02 16:28 ` bug#68687: [PATCH v2] " Max Nikulin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf5f4296-7b08-4baf-a93d-3d2bde489bf8@gmail.com \
--to=manikulin@gmail.com \
--cc=68687@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
--cc=yantar92@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.