emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: rms@gnu.org
Cc: Jean-Christophe Helary
	<jean.christophe.helary@traductaire-libre.org>,
	vincent.b.1@hotmail.fr, emacs-devel@gnu.org,
	emacs-orgmode@gnu.org
Subject: Re: Translation of the Org mode manual (was: Translation of manuals (was: SES manual French translation))
Date: Wed, 07 Feb 2024 23:10:57 +0000	[thread overview]
Message-ID: <871q9nrhtq.fsf@localhost> (raw)
In-Reply-To: <E1rXYML-0000cc-U8@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

> Using Org format for the source of a document, and converting it to
> texi for processing (for instance, through TeX) would be a fine method
> to use, if it worked.  But it doesn't actually work.
>
> The problem is that it cannot work, given Org format as it exists now.
> It cannot properly represent manuals that use the GNU standard style
> because it does not have ways to represent all the distinctions that
> are needed.
> ...

This is not true. We can generate a precise TeXinfo markup from Org
files even now using export snippets: @@texinfo:<direct texinfo code>@@

So, Org mode manual in particular can be adapted if absolutely
necessary.

Another question is that having native Org mode constructs for
manual-specific markup would make things less verbose and ad-hoc. But
that question is out of scope of this particular discussion, which is
focused on translation tools.

> I would like Org format to be extended in this way.
>
> Texinfo format is often misunderstood.  People write GNU manuals
> without knowing of all these constructs, so they use the wrong
> construct.  If Org format were extended to do _the whole job_, we
> could convert all manuals to Org format once and for all.
>
> A few years ago I raised this idea, but nobody wanted to work on it.

Your idea is not forgotten. But the resources for Org mode development
are limited. In particular, I am currently not prioritizing adding
brand-new features in favour of helping contributors, improving the
existing functionality, and fixing the existing problems.

If somebody is interested to work on adding new Org mode features like
custom inline markup, please contact Org mode mailing list. We can guide
the volunteers through the contribution process and help with any
questions when they arise.
See https://orgmode.org/worg/org-contribute.html

-- 
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-02-07 23:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PAXP192MB1608F5D8D0A89A5571C67D07849FA@PAXP192MB1608.EURP192.PROD.OUTLOOK.COM>
     [not found] ` <8A22A273-11F5-449C-A2A4-2E8C68CCF1FE@traductaire-libre.org>
     [not found]   ` <83ttnvzwlw.fsf@gnu.org>
     [not found]     ` <5D3D13BC-E621-4C40-88D7-3E5805F631AB@traductaire-libre.org>
     [not found]       ` <83sf3fzvk4.fsf@gnu.org>
     [not found]         ` <CADwFkmnvx3=kevSGb9qb9_yXs7s__crsOfpb39+7MtU6QYDM9A@mail.gmail.com>
     [not found]           ` <835y0azhvo.fsf@gnu.org>
     [not found]             ` <E9136A1F-CCD1-4A31-8018-CC4D6703BC85@traductaire-libre.org>
     [not found]               ` <83wmsqy14p.fsf@gnu.org>
     [not found]                 ` <3E7CF23D-CE62-4581-80D6-E6266CEE4DF5@traductaire-libre.org>
2024-01-04 11:34                   ` Translation of the Org mode manual (was: Translation of manuals (was: SES manual French translation)) Ihor Radchenko
2024-01-04 12:19                     ` Jean-Christophe Helary
2024-02-07  3:12                       ` Richard Stallman
2024-02-07 23:10                         ` Ihor Radchenko [this message]
2024-02-09  3:51                           ` Richard Stallman

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.orgmode.org/

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

  git send-email \
    --in-reply-to=871q9nrhtq.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jean.christophe.helary@traductaire-libre.org \
    --cc=rms@gnu.org \
    --cc=vincent.b.1@hotmail.fr \
    /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/org-mode.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).