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: Sun, 2 Jul 2017 10:22:28 +0900 Message-ID: <66D36CDA-5C32-4B53-971B-25BDB2E21CB9@gmail.com> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_C05E72E6-A58F-4903-BBAB-DB52076FD4D7" X-Trace: blaine.gmane.org 1498958608 17213 195.159.176.226 (2 Jul 2017 01:23:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 2 Jul 2017 01:23:28 +0000 (UTC) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 02 03:23:22 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 1dRTbd-00049M-Vq for ged-emacs-devel@m.gmane.org; Sun, 02 Jul 2017 03:23:22 +0200 Original-Received: from localhost ([::1]:56365 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dRTbj-0003d4-71 for ged-emacs-devel@m.gmane.org; Sat, 01 Jul 2017 21:23:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58063) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dRTav-0003ab-6m for emacs-devel@gnu.org; Sat, 01 Jul 2017 21:22:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dRTas-0005TS-13 for emacs-devel@gnu.org; Sat, 01 Jul 2017 21:22:37 -0400 Original-Received: from mail-pf0-x230.google.com ([2607:f8b0:400e:c00::230]:33633) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dRTar-0005S5-Ok for emacs-devel@gnu.org; Sat, 01 Jul 2017 21:22:33 -0400 Original-Received: by mail-pf0-x230.google.com with SMTP id e7so83969398pfk.0 for ; Sat, 01 Jul 2017 18:22:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=rVIMMzdKgfAvjaSf5h+sJpLXemB+Gi5NI1XBgFKCe14=; b=Pa8kofxx+R52S3mUSlF6h0l86kZOBNAn6oZVxfu5z1Cb9rHljwvrBTPQ6L0ex4E+bP zXO+9urkikuAFtMeKjBrJYNSIeV0OQN1ziewcvHWWWslg8oXKyaX4smyW7qBf+cD5Agt XCU+MljI/jRkcQalVLX58JCDhVw8srDaJDTusxU1IzUDZ+j8NjH1Ok4QRu3njv3k255e FqakfgRJsRBFGy4JZwuO0hFzhR3c93otIYc8ZK4kysypWORV0xWxywnHZmAfZchRo6yU jegpURAGfPTu+wPML+nq11ePEcTJxJOHw/PeRL16UdEZqAHJlyiR63utlPNjv1k/f4Pu caTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=rVIMMzdKgfAvjaSf5h+sJpLXemB+Gi5NI1XBgFKCe14=; b=VSN9VGjZd6kRneD4LqhXCA34xaKFmRPsY8QrLzXcScYq8OTQzRT23dvsDZhbiBQBwc TLnckKuOBmMhCvrTYPl1qVuieTmfqc+JJ/84UvI0GGOQtK3gtM2NR/twIgZ+ZFOdedFf cabZk7Kq4snor2AEgLEMVvb6SPsRmC04t+Q1SW/Ln5B/evfjGCGt5eQP2HjTDtsLQMy9 XXO+lh9d5E/yyfTfJX/mXD/3uguHJwSKhTrZT3kJZiyhUAL1iKfdolm2eAURH6EG/oDg g8VKpdpnVE4PXNZJWyrdC8jMXVQUoRR1Kz98l12KStUSuiQL5iBo1J/mgf3LB88wH4Cw /ztw== X-Gm-Message-State: AIVw1121s+M30eIa/tC23nfxzb6kq3Qiq7W9e/MauApk+CE2AYNIzQy/ M7CdDa0mhB5pRu83VR0= X-Received: by 10.99.7.129 with SMTP id 123mr3117919pgh.171.1498958552635; Sat, 01 Jul 2017 18:22:32 -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 t26sm29490066pfe.88.2017.07.01.18.22.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Jul 2017 18:22:30 -0700 (PDT) In-Reply-To: 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::230 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:216080 Archived-At: --Apple-Mail=_C05E72E6-A58F-4903-BBAB-DB52076FD4D7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I was wondering if that patch (and the fixes that came after) had been = committed ? Have some people started to use it ? Jean-Christophe=20 > On Jun 1, 2017, at 7:18, Philipp Stephani = wrote: >=20 >=20 >=20 > Jean-Christophe Helary > schrieb am So., 28. Mai 2017 = um 07:29 Uhr: > The discussion so far seems to point at modifying 'message' and the = likes so that developers don't have to bother with any l10n mechanism on = their part (besides for writing clean strings). >=20 > =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > On May 27, 2017, at 10:52, Jean-Christophe Helary = > wrote: >=20 >> My very uninformed idea is that we need an independent function that = handles the preferred language check and the catalog parsing based on a = key, and all the string displaying functions (message etc) would be = redefined to call that function when a non default preferred langage = (currently English) is detected. >=20 > On May 27, 2017, at 16:43, Eli Zaretskii > wrote: >=20 >> Yes but from what I've seen in package/el, a lot of translatable = texts are not displayed with "message". Some >> use "error", some use other mechanisms. >=20 > Internally, they all boil down to a small set of C functions, which is > where we should make these changes. > =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >=20 > Since it's C, I'm not going to be able to contribute to that before I = understand the language, and the function definitions. I guess it's time = I open that K&R that's been on my shelves forever... >=20 > One small aspect would be to implement field numbers for `format' so = that argument indices can be explicitly specified. That is probably = quite important because the word order is different between languages, = but it's also useful in other situations (e.g. when repeating an = argument). I've implemented this in the attached patch.=20 > <0001-Implement-field-numbers-in-format-strings.txt> --Apple-Mail=_C05E72E6-A58F-4903-BBAB-DB52076FD4D7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
I was wondering if that patch (and the fixes = that came after) had been committed ?

Have some people started to use it = ?

Jean-Christophe 

On Jun 1, 2017, at 7:18, = Philipp Stephani <p.stephani2@gmail.com> wrote:



Jean-Christophe Helary <jean.christophe.helary@gmail.com> schrieb am So., 28. = Mai 2017 um 07:29 Uhr:
The= discussion so far seems to point at modifying 'message' and the likes = so that developers don't have to bother with any l10n mechanism on = their part (besides for writing clean strings).

=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
On May 27, 2017, at 10:52, = Jean-Christophe Helary <jean.christophe.helary@gmail.com> wrote:

My very uninformed idea is = that we need an independent function that handles the preferred = language check and the catalog parsing based on a key, and all the = string displaying functions (message etc) would be redefined to = call that function when a non default preferred langage = (currently English) is detected.

On May 27, 2017, at 16:43, Eli Zaretskii = <eliz@gnu.org> wrote:

Yes but from what I've seen in package/el, a lot of = translatable texts are not displayed with "message". Some
use "error", some use other mechanisms.

Internally, they all boil down to = a small set of C functions, which is
where we should make = these changes.
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D

Since it's C, I'm not = going to be able to contribute to that before I understand the language, = and the function definitions. I guess it's time I open that K&R = that's been on my shelves forever...

One small aspect would = be to implement field numbers for `format' so that argument indices can = be explicitly specified. That is probably quite important because the = word order is different between languages, but it's also useful in other = situations (e.g. when repeating an argument). I've implemented this in = the attached patch. 
<0001-Implement-field-numbers-in-format= -strings.txt>

= --Apple-Mail=_C05E72E6-A58F-4903-BBAB-DB52076FD4D7--