From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.emacs.devel Subject: Re: i18n/l10n summary Date: Mon, 24 Jul 2017 08:29:37 +0900 Message-ID: References: <0aca6c65-4610-44c2-99c4-6cbe7aa68c9a@default> <46B40C87-EAE0-4DDA-AF4D-EF6392FF8A47@gmail.com> <83r2x88vuc.fsf@gnu.org> <10CB5E42-71F8-4F2F-80BD-A661062E9CD2@gmail.com> <83pocs8sy1.fsf@gnu.org> <3D8D36E8-D1F8-4733-A94F-AE5A61E1C528@gmail.com> <83inij8bfo.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1500852643 26002 195.159.176.226 (23 Jul 2017 23:30:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 23 Jul 2017 23:30:43 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 24 01:30:36 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dZQKT-00062Y-4C for ged-emacs-devel@m.gmane.org; Mon, 24 Jul 2017 01:30:29 +0200 Original-Received: from localhost ([::1]:52149 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dZQKY-0000e5-NL for ged-emacs-devel@m.gmane.org; Sun, 23 Jul 2017 19:30:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dZQJp-0000dh-Jp for emacs-devel@gnu.org; Sun, 23 Jul 2017 19:29:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dZQJo-0007gF-Ii for emacs-devel@gnu.org; Sun, 23 Jul 2017 19:29:49 -0400 Original-Received: from mail-pg0-x241.google.com ([2607:f8b0:400e:c05::241]:33543) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dZQJj-0007ey-8Q; Sun, 23 Jul 2017 19:29:43 -0400 Original-Received: by mail-pg0-x241.google.com with SMTP id z1so10138470pgs.0; Sun, 23 Jul 2017 16:29:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=uNx2DvqCOPiIp7nwKyZCXqxxDak1/RHProqIxT3rgJk=; b=OxmNvoIDFceKrBnjlw5WezLCeI8EdDs2f0Bzi3mDj14vltvfjZCutzyyqpntwqO2yb odElfqFg/EzxhHGmXkL5OxzipnoPehNwzcfKf5B3B1nyR9XIH1bWH0pIM1c++f+iWgt8 ZZ9v44640ZUHweQvEQxcsulZQ5S0IFBQ5X2oz8BD+yz4RqDYZtu7sGo25J4Wd9xn/ilL XVXuqgn74Cwv5wuINGgqYoleBeEtM5mlCjMkvegre3kcaBhztSgtU/LXd6RJr6VurErG 39xJUzyesIZpZYIr1xNl/MYh1XCHQ0QIjMoOpy56oHPx8DgHoG5i3LyxbBfTtOuOZ0Et yXxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=uNx2DvqCOPiIp7nwKyZCXqxxDak1/RHProqIxT3rgJk=; b=Affl52WmkhTc3HEpBnwL/u1XR1HtUsGwf1Wq20dnVgb2EdZl+uNx3H3lsWZDOaMibL QsTu5ppssk1ZT5eFyMWsqjBOu1q+IMvxE3MCFKFUi19X5Kd2ROqwAw/ibLLFbCMQrCLB i8ggs02FV/mK+rIMlQzpqGd1LIIYzw5QNSDjsvXf9zsuc5/sVghChLXsTna8dVuxt90d aACO4H4SSqEj0tf5yigT0IiUGAPY8vXfxGrNNvEdCBFkbPiKBR9W5BRXYpjqJzYteE3j Ig368grhhamMBvJMow/NY5ojCnM3Qr/4/ul7KczCvE+yXnNSUXt96a7gkwQw9nYvzKJ2 NEuQ== X-Gm-Message-State: AIVw110JIhDv5X97j+7ldfzZeMdQbnD/IR8AkSgzE4ONvFfCzNDZBXnD 7wjP0yd/rzWNGkOQK5A= X-Received: by 10.99.55.10 with SMTP id e10mr14240229pga.176.1500852580729; Sun, 23 Jul 2017 16:29:40 -0700 (PDT) Original-Received: from [192.168.24.55] (pl2587.ag0304.nttpc.ne.jp. [128.53.196.27]) by smtp.gmail.com with ESMTPSA id b18sm10111364pfe.94.2017.07.23.16.29.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Jul 2017 16:29:39 -0700 (PDT) In-Reply-To: <83inij8bfo.fsf@gnu.org> X-Mailer: Apple Mail (2.3273) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400e:c05::241 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:216953 Archived-At: > On Jul 23, 2017, at 23:39, Eli Zaretskii wrote: >=20 >> From: Jean-Christophe Helary >> Date: Sun, 23 Jul 2017 08:54:36 +0900 >> Cc: emacs-devel@gnu.org >>=20 >>>> 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. >>>=20 >>> 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. >>=20 >> 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. >=20 > Sorry, I don't think I follow. Does po4a understand Texinfo in > general and the @documentlanguage directive in particular? No, it doesn't. It just extracts text. po4a is the tool that has been = developed to allow people who are familiar with po to work with = documentation files. It just round-trips the document to and from the po = format and is not at all as smart as gettext. For ex. The current docstyle.texi is converted to a docstyle.texi.fr.po = whose contents is: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D # SOME DESCRIPTIVE TITLE # Copyright (C) YEAR Free Software Foundation, Inc. # This file is distributed under the same license as the PACKAGE = package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2017-07-24 08:11+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=3DCHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. type: Plain text #: docstyle.texi:6 msgid "@documentencoding UTF-8 @documentlanguage en_US" msgstr "" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D It is arguable that we could have something better like: #. type: documentencoding #: docstyle.texi:2 msgid "UTF-8" msgstr "" #. type: documentlanguage #: docstyle.texi:3 msgid "en_US" msgstr "" but that's a separate discussion. > And if it doesn't understand Texinfo, why would > the presence of @documentlanguage change anything in its output? po4a presents the strings to the translator for modification. As far as = the translator is concerned, that is the only place where the language = for the whole documentation set is presented and that the one and only = place that needs to be changed so that the whole documentation gets the = appropriate @documentlanguage directive. > And where would someone need to add the language string manually -- in > what file? If the directive were not present, somebody would need to manually add = @documentlanguage [appropriate language] directive to the docstyle.texi = file of that language. Jean-Christophe=20