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: Tue, 25 Jul 2017 00:34:54 +0900 Message-ID: <7F1C3549-B097-4797-9329-FD180D1C5511@gmail.com> 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> <8360eh99jf.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 1500910562 7510 195.159.176.226 (24 Jul 2017 15:36:02 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 24 Jul 2017 15:36:02 +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 17:35:58 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 1dZfOj-0001Wm-R2 for ged-emacs-devel@m.gmane.org; Mon, 24 Jul 2017 17:35:54 +0200 Original-Received: from localhost ([::1]:55467 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dZfOp-0005UR-IF for ged-emacs-devel@m.gmane.org; Mon, 24 Jul 2017 11:35:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59081) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dZfNx-0005UE-11 for emacs-devel@gnu.org; Mon, 24 Jul 2017 11:35:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dZfNv-0003vW-S9 for emacs-devel@gnu.org; Mon, 24 Jul 2017 11:35:05 -0400 Original-Received: from mail-pf0-x235.google.com ([2607:f8b0:400e:c00::235]:36505) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dZfNq-0003pc-D6; Mon, 24 Jul 2017 11:34:58 -0400 Original-Received: by mail-pf0-x235.google.com with SMTP id z129so8668198pfb.3; Mon, 24 Jul 2017 08:34:58 -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=pENQMVyc8SuTjlHXzQHGqky9AeOPKyCMrHzWSQzchjA=; b=p8rm14wwQ/8Xo2J3eimdrT1LCGrQovIaIxuiBEfgP8YUJCunJmc5hUaPcxQeN3lWet tcy7QzQYoppVB7v+6YfguO1OWbRx6Me7CquzCdywxPZ0GUgEiq0TxsqEH/RXMGUCia9M ijY5Sg3CtuOvY0q1PTVzC2eerUibsOp7BkPIV6EEL8rLORijbyD71vJooJOiDimPQxrz XK0A3GbM+/uqvpvAqjLSQz4yaOgJZFoEl0gEeWFn2le3DQs2aMYSa+ZFQ7bNngqsvfs+ eYt7bYTRPQCJ3Tzs1HqeIjnpg+bg9qrSWd0VYtxkcsw2wb3qsCotV+U+JAaSB+AWIyfY cldQ== 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=pENQMVyc8SuTjlHXzQHGqky9AeOPKyCMrHzWSQzchjA=; b=uMZiwYUCsVLteCt2x8j/gpxcPSLPz7qz5aJAIRu8TeSgxj+VWN8e4bB5dUkS1VHLPJ oyzI05Xl4aEi+XwSVgpqagGhWYItnEo3zrB1LUHhGq4rSJGDc++K/F/SN7OaTKpoj4PV lhJXgHQIRw8hFnjJTxNs8cxD1Q3xm5b3/Vsusv10suEREcdwh4srZ7YDtoeOftCwGQ78 BJV+Nr3HmYIVX2tqFqHpos5g9XMjXVAOYTO16JwnVdquL7DziT7S8HpjEsWpBhm6Qy5A iDfnJG962bkD1Dfby/EgqYCFUmuWbTsIdB5dKgUFyHcTr0P3DHvqPqKZzEW/mLpwQaXl oDrw== X-Gm-Message-State: AIVw112hV/oFK/hDZ/FD8HfdNTfz4QOSZY3XsjKdwGMID45CJ0IJplJU pH2YHp4mOCi6RuwFnFY= X-Received: by 10.98.142.1 with SMTP id k1mr16146458pfe.189.1500910497304; Mon, 24 Jul 2017 08:34:57 -0700 (PDT) Original-Received: from [192.168.24.53] (pl12518.ag0304.nttpc.ne.jp. [128.53.234.230]) by smtp.gmail.com with ESMTPSA id q83sm6521225pfk.8.2017.07.24.08.34.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Jul 2017 08:34:56 -0700 (PDT) In-Reply-To: <8360eh99jf.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:c00::235 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:216967 Archived-At: > On Jul 24, 2017, at 23:47, Eli Zaretskii wrote: >=20 >> From: Jean-Christophe Helary >> Date: Mon, 24 Jul 2017 08:29:37 +0900 >> Cc: emacs-devel@gnu.org >>=20 >>> And where would someone need to add the language string manually -- = in >>> what file? >>=20 >> If the directive were not present, somebody would need to manually = add @documentlanguage [appropriate language] directive to the = docstyle.texi file of that language. >=20 > OK, thanks. But AFAIU, po4a can be told to add text to the translated > document; couldn't we simply insert @documentlanguage in the > translated manual that way, without expecting the original manuals to > add this redundant directive to the English original? I was not aware of this option, after checking the po4a manual here is = what it says: https://po4a.alioth.debian.org/man/man7/po4a.7.php "HOWTO add extra text to translations (like translator's name)?" > HOWTO add extra text to translations (like translator's name)? >=20 > Because of the gettext approach, doing this becomes more difficult in = po4a than it was when simply editing a new file along the original one. = But it remains possible, thanks to the so-called addenda. > It may help the comprehension to consider addenda as a sort of patches = applied to the localized document after processing. They are rather = different from the usual patches (they have only one line of context, = which can embed Perl regular expression, and they can only add new text = without removing any), but the functionalities are the same. >=20 > Their goal is to allow the translator to add extra content to the = document which is not translated from the original document. The most = common usage is to add a section about the translation itself, listing = contributors and explaining how to report bug against the translation. >=20 > An addendum must be provided as a separate file. The first line = constitutes a header indicating where in the produced document they = should be placed. The rest of the addendum file will be added verbatim = at the determined position of the resulting document. >=20 > The header has a pretty rigid syntax: It must begin with the string = PO4A-HEADER:, followed by a semi-colon (;) separated list of key=3Dvalue = fields. White spaces ARE important. Note that you cannot use the = semi-colon char (;) in the value, and that quoting it doesn't help. So we'd have to create and maintain as many files as there are = translations, instead of just adding 1 directive in 1 texi file and be = done with it. Jean-Christophe=20=