From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals
Date: Sat, 01 Oct 2022 11:30:06 +0800 [thread overview]
Message-ID: <878rm02pc1.fsf@localhost> (raw)
In-Reply-To: <th6okr$112a$1@ciao.gmane.io>
Max Nikulin <manikulin@gmail.com> writes:
> On 30/09/2022 10:31, Ihor Radchenko wrote:
>>
>> Texinfo provides numerous subtle distinctions that show up clearly in
>> each of these output formats. Compare, for example, @var, @dfn and
>> @emph; compare @code, @samp, @file, @command, @option, @kbd, and @key.
>
> I have not read the emacs-devel thread, so I may ask about something
> that already has been discussed.
>
> Are there cases when texinfo may use nested formatting commands of the
> same type, something like @samp{a @code{b @samp{c} d} e}? My concern is
> that current org-element parser may be a blocker.
AFAIK, the only nested construct in Texinfo spec is
@acronym{GNU, @acronym{GNU}'s Not Unix}
https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#g_t_0040acronym
But it should not be a blocker. We can use two different elements for
this instead or employ the requirement of balanced parenthesis inside,
similar to what we do in the HEADERS for inline src blocks
https://orgmode.org/worg/dev/org-syntax.html#Source_Blocks
> Another point is that most of the mentioned commands a close to
> verbatim, but Org has much more special characters recognized as markup
> and no markup is allowed inside Org verbatim snippets. Escaping (by zero
> width spaces?) of code and samples may be prohibitively inconvenient in
> Org if markup should be recognized inside.
We need a new special object type for markup that does not suffer from
the limitations of our current single-char-style *markup* constructs.
(It is not even solely motivated by this request from RMS; we just need
something to allow whitespace in verbatim boundaries)
> One more point is external tools like pandoc export from Org to other
> formats. When Org extensions are implemented in elisp, such tools become
> hardly usable. Unsure if some kind of declarative style sheets will be
> enough.
We already have Org extensions for links. I envision supporting GNU
manuals in a similar fashion. Only a subset of universally useful
extensions will become the actual part of Org syntax spec. At the end,
Org should remain generic export format without going too far into
manual-specific requirements. Specific exports should be supported
optionally, similar to our ol-*.el libraries.
--
Ihor Radchenko,
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
next prev parent reply other threads:[~2022-10-01 3:29 UTC|newest]
Thread overview: 157+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 2:52 Org mode and Emacs Payas Relekar
2022-09-25 6:35 ` Bastien
2022-09-25 7:05 ` Ihor Radchenko
2022-09-25 7:47 ` Bastien
2022-09-25 8:01 ` Ihor Radchenko
2022-09-25 8:22 ` Bastien Guerry
2022-09-25 8:01 ` Eli Zaretskii
2022-09-25 19:47 ` Tim Cross
2022-09-26 6:12 ` Bastien
2022-09-26 6:35 ` Ihor Radchenko
2022-09-26 6:57 ` Bastien
2023-08-18 17:09 ` Ihor Radchenko
2023-08-18 18:31 ` Eli Zaretskii
2023-08-18 18:49 ` Ihor Radchenko
2023-08-18 19:11 ` Eli Zaretskii
2023-08-18 19:31 ` Ihor Radchenko
2023-08-19 5:51 ` Eli Zaretskii
2023-08-19 9:04 ` Ihor Radchenko
2023-08-19 9:26 ` Eli Zaretskii
2023-08-19 9:44 ` Ihor Radchenko
2023-08-19 10:19 ` Po Lu
2023-08-19 10:47 ` Eli Zaretskii
2023-08-19 10:48 ` Ihor Radchenko
2023-08-19 10:42 ` Eli Zaretskii
2023-08-19 10:54 ` Ihor Radchenko
2023-08-21 1:12 ` Richard Stallman
2023-08-21 7:56 ` Philip Kaludercic
2023-08-23 2:12 ` Richard Stallman
2023-08-23 9:44 ` Ihor Radchenko
2023-08-23 11:01 ` Colin Baxter
2023-08-23 11:12 ` Ihor Radchenko
2023-08-23 12:49 ` Po Lu
2023-08-23 17:18 ` Colin Baxter
2023-08-23 17:47 ` Ihor Radchenko
2023-08-23 18:02 ` Eli Zaretskii
2023-08-23 18:08 ` Ihor Radchenko
2023-08-23 18:18 ` Eli Zaretskii
2023-08-23 18:36 ` Ihor Radchenko
2023-08-23 18:46 ` Eli Zaretskii
2023-08-23 18:50 ` Ihor Radchenko
2023-08-25 1:11 ` Richard Stallman
2023-08-23 16:53 ` Colin Baxter
2023-08-23 17:56 ` Tassilo Horn
2023-08-24 11:52 ` Bastien Guerry
2023-08-24 17:51 ` T.V Raman
2023-08-24 17:55 ` Ihor Radchenko
2023-08-24 18:35 ` T.V Raman
2023-08-25 1:16 ` Richard Stallman
2023-08-25 11:45 ` Richard Stallman
2023-08-25 1:14 ` Richard Stallman
2023-08-25 9:04 ` Bastien Guerry
2023-08-25 18:56 ` Philip Kaludercic
2023-08-26 10:46 ` Ihor Radchenko
2023-08-31 2:09 ` Richard Stallman
2023-08-31 8:50 ` Ihor Radchenko
2023-08-26 2:04 ` Richard Stallman
2023-08-26 5:50 ` Eli Zaretskii
2023-08-26 16:49 ` Jose E. Marchesi
2023-08-26 16:56 ` Ihor Radchenko
2023-08-26 20:28 ` Philip Kaludercic
2023-08-26 20:58 ` Ihor Radchenko
2023-08-30 8:11 ` Bastien Guerry
2023-08-27 1:32 ` Richard Stallman
2023-08-27 8:32 ` Ihor Radchenko
2023-08-28 1:32 ` Richard Stallman
2023-08-29 8:29 ` Ihor Radchenko
2023-09-01 1:18 ` Richard Stallman
2023-09-01 6:46 ` Ihor Radchenko
2023-09-04 1:32 ` Richard Stallman
2023-09-04 22:05 ` Juergen Fenn
2023-09-05 11:04 ` Ihor Radchenko
2023-09-06 0:58 ` Richard Stallman
2023-09-06 11:29 ` Ihor Radchenko
2023-09-06 12:33 ` Eli Zaretskii
2023-09-06 12:43 ` Ihor Radchenko
2023-09-06 12:49 ` Po Lu
2023-09-06 12:54 ` Ihor Radchenko
2023-09-06 13:04 ` Po Lu
2023-09-06 13:10 ` Ihor Radchenko
2023-09-06 13:33 ` Po Lu
2023-09-06 15:28 ` Eli Zaretskii
2023-09-06 13:08 ` Eli Zaretskii
2023-09-06 13:20 ` Ihor Radchenko
2023-09-06 15:25 ` Eli Zaretskii
2023-09-06 16:12 ` Ihor Radchenko
2023-09-06 16:34 ` Eli Zaretskii
2023-09-07 11:11 ` Ihor Radchenko
2023-09-10 0:22 ` Richard Stallman
2023-09-09 0:37 ` Richard Stallman
2023-09-09 9:36 ` Ihor Radchenko
2023-09-10 0:22 ` Richard Stallman
2023-09-09 0:38 ` Richard Stallman
2023-08-30 8:11 ` Bastien Guerry
2023-09-02 1:50 ` Richard Stallman
2023-09-02 8:19 ` Ihor Radchenko
2023-09-02 8:30 ` Alfred M. Szmidt
2023-08-27 1:32 ` Richard Stallman
2023-08-27 8:35 ` Ihor Radchenko
2023-08-28 1:32 ` Richard Stallman
2023-08-28 10:04 ` Ihor Radchenko
2023-08-28 11:15 ` Yuri Khan
2023-08-28 11:21 ` Ihor Radchenko
2023-08-31 2:09 ` Richard Stallman
2023-08-31 8:53 ` Ihor Radchenko
2023-09-04 1:33 ` Richard Stallman
2023-08-30 8:14 ` Bastien Guerry
2023-08-30 8:32 ` Po Lu
2023-08-27 1:33 ` Richard Stallman
2022-09-26 8:24 ` Eli Zaretskii
2022-09-26 8:32 ` Jean Louis
2022-09-26 9:54 ` Ihor Radchenko
2022-09-26 11:04 ` Robert Pluim
2022-09-27 16:17 ` Richard Stallman
2022-09-30 3:41 ` Ihor Radchenko
2022-09-26 12:10 ` Richard Stallman
2022-09-30 3:31 ` [HELP] Fwd: Org format as a new standard source format for GNU manuals Ihor Radchenko
2022-09-30 3:49 ` Samuel Wales
2022-09-30 5:47 ` Thomas S. Dye
2022-09-30 8:25 ` Christopher M. Miles
2022-09-30 12:49 ` Max Nikulin
2022-10-01 3:30 ` Ihor Radchenko [this message]
2022-10-01 10:42 ` Max Nikulin
2022-10-01 11:01 ` Ihor Radchenko
2022-10-01 11:27 ` Max Nikulin
2022-10-02 4:59 ` Ihor Radchenko
2022-10-02 10:38 ` Fraga, Eric
2022-10-02 13:02 ` Ihor Radchenko
2022-10-02 13:21 ` Fraga, Eric
2022-10-02 13:47 ` Juan Manuel Macías
2022-10-03 4:23 ` Ihor Radchenko
2022-10-04 20:28 ` Juan Manuel Macías
2022-10-05 6:56 ` Rick Lupton
2022-10-06 3:39 ` Ihor Radchenko
2022-10-02 16:28 ` Max Nikulin
2022-10-03 4:36 ` Ihor Radchenko
2022-10-04 16:32 ` Max Nikulin
2022-10-06 5:55 ` Ihor Radchenko
2022-09-30 20:36 ` Tim Cross
2022-10-01 4:08 ` Ihor Radchenko
2022-10-01 8:01 ` Tim Cross
2022-10-01 15:08 ` Max Nikulin
2022-10-03 4:19 ` Ihor Radchenko
2022-10-07 22:48 ` Richard Stallman
2022-10-08 6:52 ` Ihor Radchenko
2022-10-08 22:34 ` Richard Stallman
2022-10-11 3:03 ` Robert Weiner
2022-10-11 12:16 ` Ihor Radchenko
2022-10-12 22:00 ` Richard Stallman
2022-09-26 3:02 ` Org mode and Emacs Ihor Radchenko
2022-09-26 5:37 ` Po Lu
2022-09-26 5:44 ` Emanuel Berg
2022-09-26 6:20 ` Bastien Guerry
2022-09-26 13:58 ` T.V Raman
2022-09-26 16:16 ` Eli Zaretskii
2022-09-26 6:36 ` Ihor Radchenko
2022-09-26 6:18 ` Bastien
2022-09-26 6:29 ` Ihor Radchenko
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=878rm02pc1.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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 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.