From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Emacs manuals translation readme
Date: Tue, 13 Feb 2024 02:25:32 +0000 [thread overview]
Message-ID: <F165861C-1B3A-4515-ABB9-9F01E50CF534@traductaire-libre.org> (raw)
In-Reply-To: <A0CEC6B3-59A9-418C-A3F1-A318813CE8E2@traductaire-libre.org>
I gathered all the comments and integrated them, so I think that the
patches are now ready for a formal review and eventual installation.
Are there things that I have overlooked?
> On Jan 26, 2024, at 10:04, Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org> wrote:
>
> I think I have covered all the recent comments to the original proposal.
>
> 1. the "lang" directory is renamed "translations"
>
> → the length of the name is not really relevant since we have term
> completions in Emacs
> → "translations" is more indicative of the contents of the folder than
> "lang"
>
> 2. the readme includes more references to the GNU project translation
> projects without suggesting that Emacs manual translations should be
> included in the projects.
>
>
> Let me know if there are other issues.
>
> <0001-Rename-doc-lang-to-doc-translations.patch>
>
> <0002-New-doc-translations-readme-file-for-translators.patch>
next prev parent reply other threads:[~2024-02-13 2:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 1:04 Emacs manuals translation readme Jean-Christophe Helary
2024-02-13 2:25 ` Jean-Christophe Helary [this message]
2024-02-13 2:31 ` Po Lu
2024-02-13 3:32 ` Eli Zaretskii
2024-02-13 3:51 ` Jean-Christophe Helary
2024-02-13 4:02 ` Po Lu
2024-02-17 8:55 ` Eli Zaretskii
2024-02-17 15:07 ` Jean-Christophe Helary
2024-02-17 18:18 ` Stefan Kangas
2024-02-17 18:30 ` Eli Zaretskii
2024-02-18 10:45 ` Stefan Kangas
2024-02-18 8:00 ` Eli Zaretskii
2024-02-19 11:13 ` Jean-Christophe Helary
2024-02-19 13:22 ` Eli Zaretskii
2024-02-19 14:20 ` Jean-Christophe Helary
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=F165861C-1B3A-4515-ABB9-9F01E50CF534@traductaire-libre.org \
--to=jean.christophe.helary@traductaire-libre.org \
--cc=emacs-devel@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.