unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 68687@debbugs.gnu.org, Max Nikulin <manikulin@gmail.com>,
	emacs-orgmode@gnu.org
Subject: bug#68687: [PATCH] Use text/org media type
Date: Thu, 25 Jan 2024 23:43:14 +0000	[thread overview]
Message-ID: <87h6j1f08d.fsf__45251.9857253478$1706226093$gmane$org@localhost> (raw)
In-Reply-To: <CADwFkmn_qivb3GbHjXbdngcZe3g3LHiR9MZ9ffYjctFsWdw_yg@mail.gmail.com>

Stefan Kangas <stefankangas@gmail.com> writes:

>> I suggest to make the media type used for Org mode files consistent with
>> the one used by XDG https://gitlab.freedesktop.org/xdg/shared-mime-info
>> Currently Emacs has text/x-org, however "x-" prefix is not recommended
>> by IANA any more, see https://www.rfc-editor.org/rfc/rfc6648
>> "Deprecating the "X-" Prefix and Similar Constructs in Application
>> Protocols"
>> Ideally somebody should file a request to IANA to register the text/org
>> media type.
>> https://www.iana.org/assignments/media-types/media-types.xhtml
>
> Eli, Ihor, what do you think?

I see using text/org as an improvement. text/x-org is likely useless.
At least,
https://github.com/jeremy-compostella/org-msg/blob/master/org-msg.el
uses text/org, which may appear in email parts.

However, AFAIU, text/org will fall into "standards tree" in IANA media
type specification, which means that it MUST be registered, as described
in https://www.rfc-editor.org/rfc/rfc6838.html#section-3.1

Registering text/org media type requires syntax spec. We are
still working on format Org mode syntax specifications. See
https://list.orgmode.org/orgmode/871rjhha8t.fsf@gmail.com/ and
https://orgmode.org/worg/org-syntax.html

The spec is still not fully finalized, so we are not yet initiating the
registration, as we will need to repeat it again if we decide to make
further changes (https://www.rfc-editor.org/rfc/rfc6838.html#section-5.5)

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  reply	other threads:[~2024-01-25 23:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6d94fff4-4d30-4121-bfd1-f267cb5b637c@gmail.com>
     [not found] ` <8734uqpvgn.fsf@tec.tecosaur.net>
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:43       ` Ihor Radchenko [this message]
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
     [not found]       ` <87h6j1f08d.fsf@localhost>
2024-01-26  7:40         ` Eli Zaretskii
2024-01-26 10:52         ` Max Nikulin
     [not found]         ` <86h6j0bl0m.fsf@gnu.org>
2024-01-26 14:00           ` Ihor Radchenko
2024-01-30 19:39         ` Stefan Kangas
     [not found]         ` <CADwFkm=9EwTZwa3F4wGJVPAVgcW4KXS1kPzXLPg1msYDjJL2cw@mail.gmail.com>
2024-01-30 20:34           ` Ihor Radchenko
2024-01-27  3:38       ` Richard Stallman
     [not found]       ` <E1rTZWZ-0008Ca-EM@fencepost.gnu.org>
2024-01-28 16:35         ` Max Nikulin
2024-01-28 16:47           ` Eli Zaretskii
     [not found]           ` <8634uh5rrq.fsf@gnu.org>
2024-01-30  3:56             ` Richard Stallman
     [not found]             ` <E1rUfF4-00069N-Gu@fencepost.gnu.org>
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:51                   ` Ihor Radchenko
     [not found]                   ` <87mssmvhdw.fsf@localhost>
2024-02-02  3:38                     ` Richard Stallman
2024-02-02  4:58                       ` bug#68687: Org mode code evaluation Max Nikulin
2024-01-31 16:18                 ` bug#68687: [PATCH] Use text/org media type Max Nikulin
     [not found]                 ` <3c8e8b77-77d1-4522-85d5-5cce2cc020ca@gmail.com>
2024-01-31 16:32                   ` Ihor Radchenko
2024-02-02  3:40                 ` Richard Stallman
     [not found]                 ` <E1rVkPO-0008LA-RN@fencepost.gnu.org>
2024-02-02  7:15                   ` Eli Zaretskii
2024-01-30 12:52               ` Eli Zaretskii
2024-01-31 20:00     ` Stefan Kangas
2024-02-01 10:40       ` Max Nikulin
2024-02-02  7:09         ` Stefan Kangas
     [not found]         ` <CADwFkmknBZj0Y4H=Nwqa4sH0uQAsP70kWtMU33ZgfRiuWkX9_w@mail.gmail.com>
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87h6j1f08d.fsf__45251.9857253478$1706226093$gmane$org@localhost' \
    --to=yantar92@posteo.net \
    --cc=68687@debbugs.gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    --cc=stefankangas@gmail.com \
    /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/emacs.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).