From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jean.christophe.helary@traductaire-libre.org, emacs-devel@gnu.org
Subject: Re: Emacs manuals translation readme
Date: Sun, 18 Feb 2024 05:45:07 -0500 [thread overview]
Message-ID: <CADwFkmkHhVb_6mecUkEjZX1hMBOS_LqyOiGrYvQL7bc70+Hevg@mail.gmail.com> (raw)
In-Reply-To: <86v86nrlic.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> I agree that it seems rather unusual. I thought we were discussing
>>
>> doc/translations/fr
>>
>> rather than
>>
>> doc/fr/
>
> No, we weren't. You agreed to the doc/fr/ suggestion.
I had to look at the archives, and I think I see where the confusion is
coming from.
I agreed to this:
. Texinfo sources go into the doc/LANG/ subdirectory, under which
there should be the same subdirectories 'emacs', 'lispref', misc'
etc. (we will actually create a directory when the first
translation of the corresponding English manual will be
submitted);
For some reason, I didn't understand that LANG was a placeholder for
"de|fr|sv" (which seems obvious now) rather than "lang|translations".
> But anyway, I won't fight if you two prefer doc/translations/fr. I
> just wanted to set the record straight.
Thanks.
next prev parent reply other threads:[~2024-02-18 10:45 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
2024-02-17 18:30 ` Eli Zaretskii
2024-02-18 10:45 ` Stefan Kangas [this message]
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=CADwFkmkHhVb_6mecUkEjZX1hMBOS_LqyOiGrYvQL7bc70+Hevg@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).