From: Richard Stallman <rms@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
Cc: yantar92@posteo.net, 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: Tue, 06 Feb 2024 22:12:25 -0500 [thread overview]
Message-ID: <E1rXYML-0000cc-U8@fencepost.gnu.org> (raw)
In-Reply-To: <D8D45459-461B-472D-B382-81F3089B62E0@traductaire-libre.org> (message from Jean-Christophe Helary on Thu, 04 Jan 2024 12:19:21 +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. ]]]
> 1. Org mode manual itself, just like the other Emacs manuals may need to
> be translated. However, Org mode manual source is written in Org mode
> format, not texi. It is just transformed to texi as one of the export
> options.
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.
Texinfo implements semantic markup, and is designed for multiple
output formats, including Info, HTML, and DVI (whence also PDF). Two
different markup constructs that look the same in one output format
may look different in another. All these design decisions were the
result of long thought.
For instance, italic face can be the result of @dfn, @var, @emph,
@cite and @i. Each of them has a meaning -- which one to use is not a
matter of taste.
@cite is used around the title of a book.
@dfn is used around the first use of a term, to say it is being defined.
@emph is used to indicate emphasis.
@var is used around a metasyntactic variable.
@i means "use italic for this" and does not say why. It is a escape
for situations that Texinfo has no specific way to describe.
These five commands produce the same output in DVI/PDF, but different
output in Info.
I think there must be 15 different Texinfo commands to generate
fixed-width bold text in DVI/PDF.
To represent a manual source in Org format and do the job right is not
possible with Org format as it is now. To make it possible requires
extending Org format so it can make all the distinctions Texinfo can
make.
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.
--
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)
next prev parent reply other threads:[~2024-02-07 3:13 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 [this message]
2024-02-07 23:10 ` Ihor Radchenko
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=E1rXYML-0000cc-U8@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).