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@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: i18n/l10n summary
Date: Sun, 23 Jul 2017 17:39:23 +0300	[thread overview]
Message-ID: <83inij8bfo.fsf@gnu.org> (raw)
In-Reply-To: <3D8D36E8-D1F8-4733-A94F-AE5A61E1C528@gmail.com> (message from Jean-Christophe Helary on Sun, 23 Jul 2017 08:54:36 +0900)

> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
> Date: Sun, 23 Jul 2017 08:54:36 +0900
> Cc: emacs-devel@gnu.org
> 
> >> After checking the files I realized that all had "@include docstyle.texi" which already had "@documentencoding UTF-8", so I just added "@documentlanguage en_US" there.
> > 
> > en_US is the default in the absence of an explicit @documentlanguage,
> > so I'm not sure I understand why would we need to add it.  It will
> > change nothing, AFAIK.
> 
> When po4a extracts translatable text to create the pot files docstyle.texi will also have a pot file that includes "@documentlanguage en_US" and that will allow translators to change that to "@documentlanguage fr_FR" etc. If we don't had that to docstyle.texi somebody will have to add the language string manually and that's an extra task that we'll have to check.

Sorry, I don't think I follow.  Does po4a understand Texinfo in
general and the @documentlanguage directive in particular?  If it
does, why doesn't it also know that en_US is the default when no such
directive is present?  And if it doesn't understand Texinfo, why would
the presence of @documentlanguage change anything in its output?  And
where would someone need to add the language string manually -- in
what file?

Thanks.



  reply	other threads:[~2017-07-23 14:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-28  5:29 i18n/l10n summary Jean-Christophe Helary
2017-05-28 14:27 ` Drew Adams
2017-05-28 14:36   ` Jean-Christophe Helary
2017-05-28 15:33   ` Eli Zaretskii
2017-06-05 12:55   ` Jean-Christophe Helary
2017-07-17 23:22     ` Jean-Christophe Helary
2017-07-22 12:48       ` Jean-Christophe Helary
2017-07-22 13:06         ` Eli Zaretskii
2017-07-22 13:45           ` Jean-Christophe Helary
2017-07-22 14:08             ` Eli Zaretskii
2017-07-22 23:54               ` Jean-Christophe Helary
2017-07-23 14:39                 ` Eli Zaretskii [this message]
2017-07-23 23:29                   ` Jean-Christophe Helary
2017-07-24 14:47                     ` Eli Zaretskii
2017-07-24 15:34                       ` Jean-Christophe Helary
2017-07-24 15:51                         ` Eli Zaretskii
2017-07-24 16:08                           ` Jean-Christophe Helary
2017-07-24 16:29                             ` Eli Zaretskii
2017-07-24 16:48                               ` Jean-Christophe Helary
2017-07-24 16:55                                 ` Eli Zaretskii
2017-05-31 22:18 ` Philipp Stephani
2017-05-31 22:29   ` Jean-Christophe Helary
2017-06-01  5:18   ` Paul Eggert
2017-06-01  8:17     ` Philipp Stephani
2017-06-01 23:20       ` Paul Eggert
2017-06-02  6:52         ` Philipp Stephani
2017-06-03  8:37           ` Paul Eggert
2017-06-03  9:12             ` Andreas Schwab
2017-06-03  9:34             ` Philipp Stephani
2017-06-04 15:54               ` Paul Eggert
2017-06-04 16:45                 ` Eli Zaretskii
2017-06-04 18:37                   ` Paul Eggert
2017-12-03  5:43                 ` Paul Eggert
2017-06-01 14:21   ` Eli Zaretskii
2017-07-02  1:22   ` Jean-Christophe Helary
2017-07-02  2:34     ` Eli Zaretskii
2017-07-28  0:15 ` Byung-Hee HWANG (황병희, 黃炳熙)
2018-04-25 12:58 ` Jean-Christophe Helary
2018-09-21  4:18   ` Jean-Christophe Helary
     [not found] <<AA86315D-1561-41EB-A349-63100C565E8D@gmail.com>
     [not found] ` <<0aca6c65-4610-44c2-99c4-6cbe7aa68c9a@default>
     [not found]   ` <<83a85xgfo2.fsf@gnu.org>
2017-05-28 21:52     ` Drew Adams

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=83inij8bfo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@gmail.com \
    /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).