From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: jean.christophe.helary@traductaire-libre.org, emacs-devel@gnu.org
Subject: Re: Where to contribute manual translations ? (Re: Emacs-devel Digest, Vol 238, Issue 29)
Date: Tue, 02 Jan 2024 05:32:56 +0200 [thread overview]
Message-ID: <837cks1kbb.fsf@gnu.org> (raw)
In-Reply-To: <E1rKVKF-0008Vd-A5@fencepost.gnu.org> (message from Richard Stallman on Mon, 01 Jan 2024 22:20:19 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Mon, 01 Jan 2024 22:20:19 -0500
>
> > The digest to which I responded branched out as a summary of the
> > previous discussions regarding Emacs manuals translation/localization
> > and as a description of the current state of the French translation
> > effort.
>
> > The non-digest thread involving Eli and Stefan discusses the possible
> > locations of the translation sources, etc.
>
> It sounds like this is thread is limited to how to include, in Emacs,
> translation of the manuals in Emacs. Is that right?
Basically, yes. We only touch broader issues where that is necessary,
and try to find Emacs solutions that don't change those broader
aspects, like how Texinfo and Info work in general.
next prev parent reply other threads:[~2024-01-02 3:32 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 [this message]
2023-12-31 7:38 ` Eli Zaretskii
2023-12-29 1:23 ` Jean-Christophe Helary
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=837cks1kbb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traductaire-libre.org \
--cc=rms@gnu.org \
/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.