RE: Where to contribute manual translations ?

["Vincent Belaïche" <vincent.b.1@hotmail.fr>]

[-- Attachment #1: Type: text/plain, Size: 2650 bytes --]

Dear Eli,

Thank you for your quick and very complete reply. Yes, I think that the best would be for me to have this translation under the Emacs project, as it would be kept consistent with the source code. Is doc/fr/misc/ses.texi OK for the French version path, as the original is doc/misc/ses.texi ?

   V.
________________________________
De : emacs-devel-bounces+vincent.b.1=hotmail.fr@gnu.org <emacs-devel-bounces+vincent.b.1=hotmail.fr@gnu.org> de la part de Eli Zaretskii <eliz@gnu.org>
Envoyé : jeudi 28 décembre 2023 08:15
À : Vincent Belaïche <vincent.b.1@hotmail.fr>
Cc : emacs-devel@gnu.org <emacs-devel@gnu.org>
Objet : Re: Where to contribute manual translations ?

> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
> Date: Wed, 27 Dec 2023 21:14:06 +0000
> msip_labels:
>
> Where is the right place to contribute a translation to French of the SES manual ?

We don't have a place yet.  Do you intend to contribute this to the
Emacs project, so that this manual is maintained as part of Emacs and
distributed with the release tarballs, or do you intend to make it a
separately-maintained manual available from outside of emacs.git?  In
the latter case, perhaps making it a GNU ELPA package could be a
possibility?

> Is it there : https://savannah.nongnu.org/projects/emacsdoc-fr

It could be.  But I'm not sure it's the best place, at least from the
discoverability POV.

> Or can it be placed directly under the Emacs repo (or is there any git submodule planned under
> directory doc for that ?)

It can, if you'd like to contribute this manual to the Emacs project,
and keep maintaining it as part of Emacs.

> Another question : how to internationalize docstrings ? IMHO it would be great if the docstring could
> have some info manual anchor in it, and one could display it from the currently selected language
> manual. Besides, reading docstring from manual via some anchor is basically what Calc does with
> some kitchen tricks.

We don't yet have the necessary infrastructure for translating doc
strings.  This was discussed in the past several times, and the
conclusion was that it's a non-trivial project.  Some of the previous
discussions:

  https://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00750.html
  https://lists.gnu.org/archive/html/emacs-devel/2017-05/msg00645.html
  https://lists.gnu.org/archive/html/emacs-devel/2017-05/msg00751.html
  https://lists.gnu.org/archive/html/emacs-devel/2017-05/msg00806.html
  https://lists.gnu.org/archive/html/emacs-devel/2019-03/msg00081.html
  https://lists.gnu.org/archive/html/help-gnu-emacs/2021-07/msg00422.html


[-- Attachment #2: Type: text/html, Size: 5182 bytes --]