emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	stefankangas@gmail.com, vincent.b.1@hotmail.fr,
	emacs-devel@gnu.org, rms@gnu.org, emacs-orgmode@gnu.org
Subject: Translation of the Org mode manual (was: Translation of manuals (was: SES manual French translation))
Date: Thu, 04 Jan 2024 11:34:31 +0000	[thread overview]
Message-ID: <877ckp72ns.fsf@localhost> (raw)
In-Reply-To: <3E7CF23D-CE62-4581-80D6-E6266CEE4DF5@traductaire-libre.org>

Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
> I’m not sure this is the place to discuss translation theory...

Let me steer this discussion to non-texi manuals - Org mode manual.
We also had a few requests about translations, although Org mode needs
are more general compared to a very focused task of translating texi

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

2. Org mode website has several translations (French, Japanese, and
   Mandarin). The website sources are written in Org mode, but the work
   of translation was done be enthusiasts, and we have no good system to
   maintain the main English version of the website in sync with the

3. A number of Org mode users are using Org sources to publish
   multi-lingual books. Such publishing is a bit more challenging
   compared to translation as it requires special book layout.

Therefore, there is a demand to have a toolset for translating Org mode

So far, I have been thinking about some way to support translations with
ideas rather similar to raised in this topic:

1. Mark paragraphs/headings/other structural elements with an ID

2. Split translation into chunks linked to the original source IDs and
   their text hash

3. When exporting from Org source to target format (texi, html, pdf,
   etc), allow choosing the target language(s) and ensure consistency
   between translations and their possibly changed sources.

However, I did not know about po4a. It is possible that many of the
necessary design decisions are already in place in po4a.

> ...
> I think po-mode already does that and all the "out of emacs" tools do 
> too.

May you share the most important features of po-mode that you find
essential to your translation work?

>> @node Display Margins
>>  @subsection Displaying in the Margins
>>  @cindex display margins
>>  @cindex margins, display
> As long as the above strings are to be translated, they need an ID too.
>>  @c para 1234
>>  @c para 1235
>>  @c para 1236
> Is the numbering automatic?
> What if you add paragraphs in the middle, like Vincent did? Will the 
> author have to check the IDs and add a number that’s not used already?
> There are plenty of issues with static IDing parts of a document.

May you please elaborate on the issues with static IDs?

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-04 11:32 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                   ` Ihor Radchenko [this message]
2024-01-04 12:19                     ` Translation of the Org mode manual (was: Translation of manuals (was: SES manual French translation)) Jean-Christophe Helary
2024-02-07  3:12                       ` Richard Stallman
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:

  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=877ckp72ns.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jean.christophe.helary@traductaire-libre.org \
    --cc=rms@gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=vincent.b.1@hotmail.fr \


* 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


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).