all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
To: emacs-devel@gnu.org
Cc: vincent.b.1@hotmail.fr, stefankangas@gmail.com, eliz@gnu.org
Subject: Re: Where to contribute manual translations ? (Re: Emacs-devel Digest, Vol 238, Issue 29)
Date: Fri, 29 Dec 2023 01:23:40 +0000	[thread overview]
Message-ID: <AFA2B042-1B5F-4601-96ED-74BBF0621CED@traductaire-libre.org> (raw)
In-Reply-To: <mailman.35.1703782806.25325.emacs-devel@gnu.org>



> On Dec 29, 2023, at 9:24, Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org> wrote:
> 
>> On Dec 29, 2023, at 2:00, emacs-devel-request@gnu.org wrote:
> 
>> Message: 1
>> Date: Wed, 27 Dec 2023 21:14:06 +0000
>> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
>> To: emacs-devel <emacs-devel@gnu.org>
>> Subject: Where to contribute manual translations ?
>> Message-ID:
>> 	<PAXP192MB1608F5D8D0A89A5571C67D07849FA@PAXP192MB1608.EURP192.PROD.OUTLOOK.COM>
>> 
>> 
>> Hello,
>> 
>> Where is the right place to contribute a translation to French of the SES manual ?
>> Is it there : https://savannah.nongnu.org/projects/emacsdoc-fr
>> French GNU Emacs manual - Summary [Savannah]<https://savannah.nongnu.org/projects/emacsdoc-fr>
>> Savannah is a central point for development, distribution and maintenance of free software, both GNU and non-GNU.
>> savannah.nongnu.org
> 
> There have been many attempts at translating the manuals.
> 
> One was organized by traduc.org. I ended up "in charge" of it.
> 
> I moved the project to chapril / sr.ht a few years ago to easily include translators. The translation evolves slowly by it is also used for technical translation master student internships.
> 
> https://forge.chapril.org/brandelune/documentation_emacs/
> 
> The sources are hosted on sr.ht.
> 
> https://git.sr.ht/~brandelune/emacs_documentation_repository

I also made a presentation at EmacsConf 2021 on the subject:
https://emacsconf.org/2021/talks/omegat/

If you're interested in joining this effort, it is extremely "horizontal" → you don't have to do anything in particular. If you need to discuss terminology issues, I just created a dedicated mailing list:

https://lists.sr.ht/~brandelune/documentation_emacs

And I also created a tracker for translation/technical issues:
https://todo.sr.ht/~brandelune/documentation_emacs

You can also not join this project and that's also totally fine.

>> 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.
> 
> Eli answered that.

There is also a different issue, that comes before translation, it is fixing user facing strings, so that they can eventually be translated one day. I also made a presentation on that at EmacsConf 2022:
https://emacsconf.org/2022/talks/localizing/




-- 
Jean-Christophe Helary @jchelary@emacs.ch
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/





  parent reply	other threads:[~2023-12-29  1:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.35.1703782806.25325.emacs-devel@gnu.org>
2023-12-29  0:24 ` Where to contribute manual translations ? (Re: Emacs-devel Digest, Vol 238, Issue 29) Jean-Christophe Helary
2023-12-31  3:15   ` Richard Stallman
2023-12-31  3:29     ` Jean-Christophe Helary
2024-01-02  3:20       ` Richard Stallman
2024-01-02  3:24         ` Stefan Kangas
2024-01-02  3:32         ` Eli Zaretskii
2023-12-31  7:38     ` Eli Zaretskii
2023-12-29  1:23 ` Jean-Christophe Helary [this message]
2023-12-29  6:48   ` Eli Zaretskii
2023-12-29 14:21     ` Jean-Christophe Helary
2023-12-29 22:58       ` Vincent Belaïche
2023-12-30  1:33         ` Jean-Christophe Helary
2023-12-29  7:10   ` Emanuel Berg

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

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

  git send-email \
    --in-reply-to=AFA2B042-1B5F-4601-96ED-74BBF0621CED@traductaire-libre.org \
    --to=jean.christophe.helary@traductaire-libre.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.