unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
Cc: emacs-devel@gnu.org, nicolas@petton.fr
Subject: Re: Translating the Emacs website
Date: Mon, 04 Mar 2024 15:14:13 +0200	[thread overview]
Message-ID: <86h6hmm95m.fsf@gnu.org> (raw)
In-Reply-To: <B8EF48BF-E18D-4309-A5A7-796864E7BE33@traductaire-libre.org> (message from Jean-Christophe Helary on Sun, 03 Mar 2024 09:04:35 +0000)

> Date: Sun, 03 Mar 2024 09:04:35 +0000
> From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
> Cc: emacs-devel@gnu.org, nicolas@petton.fr
> 
> 
> 
> > On Mar 3, 2024, at 16:32, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> >> Date: Sun, 03 Mar 2024 04:33:05 +0000
> >> From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
> >> Cc: nicolas@petton.fr
> >> 
> >> It seems to me that before we start working on the manuals, a good
> >> entry point could be the web site.
> >> 
> >> It would also be a nice way to properly introduce the fact that we have
> >> a full-fledged localised tutorial inside Emacs (I know it is referenced
> >> on the page, but there are probably other ways we can use its contents).
> >> 
> >> 
> >> To go back to the discussion about using PO or not, it seems like the
> >> GNU project web page translations use PO files:
> >> 
> >> https://www.gnu.org/server/standards/README.translations.html#tools
> >> 
> >> The tool that’s used to convert the files to PO is called GNUN
> >> (GNUnited Nations):
> >> https://www.gnu.org/software/trans-coord/manual/gnun/gnun.html
> >> 
> >> GNUN only works with HTML.
> >> 
> >> So the question is, how do we organise the Emacs page translation?
> >> Should it be handled by the GNU Project translation teams?
> > 
> > I have no idea.
> > 
> > Please note that the Web pages get updated by the person who produces
> > the release tarballs (the details are in admin/make-tarball.txt), and
> > that person cannot be expected to be able to update the translations
> > as well.  So there's a significant problem here which needs to be
> > addressed before the idea of having the Web pages translated is
> > practical.  In particular, I don't think this should be something
> > added to the job of the Emacs maintainers, and we therefore need to
> > find some other ways of maintaining the translated Web pages and
> > keeping them up to date.
> 
> I understand. So that part of the gnu site is not really handled by the 
> gnu project, but really by people here (you I guess). Is that correct?

The site was written and arranged by Nicolas, but since then most of
the changes are by the Emacs project.  However, we only make small
changes, like adding NEWS for a new release and such.



  reply	other threads:[~2024-03-04 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03  4:33 Translating the Emacs website Jean-Christophe Helary
2024-03-03  7:32 ` Eli Zaretskii
2024-03-03  9:04   ` Jean-Christophe Helary
2024-03-04 13:14     ` Eli Zaretskii [this message]
2024-03-04  3:45 ` Richard Stallman
2024-03-04  4:15   ` 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=86h6hmm95m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@traductaire-libre.org \
    --cc=nicolas@petton.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 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).