From: Stefan Kangas <stefankangas@gmail.com>
To: Jean-Christophe Helary
<jean.christophe.helary@traductaire-libre.org>,
Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs manuals translation readme
Date: Sat, 17 Feb 2024 13:18:24 -0500 [thread overview]
Message-ID: <CADwFkmkC77saJbha-eat4BEGE0FwBR8UGdf1NShKrPymu0+bDA@mail.gmail.com> (raw)
In-Reply-To: <3E7011DA-FB97-492D-B151-8459827209BE@traductaire-libre.org>
Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
writes:
>> On Feb 17, 2024, at 17:55, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> When I wrote doc/LANG/, I meant doc/fr/, doc/de/, etc. I didn't mean
>> a literal "LANG" string. So the above renaming now has an extra
>> subdirectory, which was not something I had in mind. Stefan Kangas
>> agreed with my proposal back then. So do you object to have manuals
>> translated to French in doc/fr/, rather than in doc/translations/fr/ ?
>
> I think that’s weird.
>
> We’ll end up having something like
>
> de
> emacs
> fr
> ja
> lispintro
> lispref
> man
> misc
> zh
>
> which is very confusing. I’ve never seen that. I’d understand if the
> existing English manuals were moved under doc/en, but since that’s not
> the case, I’m not sure I understand the rationale. Still, if you and
> Stefan are ok with that, I won’t object.
I agree that it seems rather unusual. I thought we were discussing
doc/translations/fr
rather than
doc/fr/
otherwise what is the point of the "translations" directory?
next prev parent reply other threads:[~2024-02-17 18:18 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkC77saJbha-eat4BEGE0FwBR8UGdf1NShKrPymu0+bDA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traductaire-libre.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).