emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 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: Thu, 08 Feb 2024 22:51:40 -0500	[thread overview]
Message-ID: <E1rYHvQ-0002D6-QZ@fencepost.gnu.org> (raw)
In-Reply-To: <871q9nrhtq.fsf@localhost> (message from Ihor Radchenko on Wed, 07 Feb 2024 23:10:57 +0000)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

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

I know that it is possible to convert Org format to Texinfo.  I am
raising a different issue.  I think we are miscommunicating.

The question is not whether Org can be translated to Texingo.  The
question is whether Org format can represent all the distinctions that
Texinfo represents.  Or, equivalently, is it possible to translate
Texinfo text to Org format and then back to Texinfo format without
losing any information?

Last I looked, that was not possible, because of the issue I
explained in my previous message.

If things have improved and Org format is now capable of doing this, I
will consider that good news.

  > Another question is that having native Org mode constructs for
  > manual-specific markup would make things less verbose and ad-hoc.

To handle GNU manuals using Org format would not require a feature
like that.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)




      reply	other threads:[~2024-02-09  3:52 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
2024-02-09  3:51                           ` Richard Stallman [this message]

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=E1rYHvQ-0002D6-QZ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jean.christophe.helary@traductaire-libre.org \
    --cc=vincent.b.1@hotmail.fr \
    --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 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).