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: Before l10n, better practices for (message) ? Date: Thu, 25 May 2017 07:35:07 +0900 Message-ID: <1BF0657B-5A1E-4527-AACC-54E5224C5DB7@gmail.com> References: <2623E5C5-4D40-4C9F-BFF6-181D2E69F984@gmail.com> <831srgnuyc.fsf@gnu.org> <6BED2506-B1C2-4005-AFDE-2BF04209F16C@gmail.com> <83zie3mndz.fsf@gnu.org> <83inkrm1ca.fsf@gnu.org> <7C2AD6EB-134C-4013-BE3F-6B302A9DBF8D@gmail.com> <67076bf4-0272-0219-88aa-1f6410fe92de@cs.ucla.edu> <7F5DC149-A21B-4A0F-B1EC-3CC66DD24873@gmail.com> <83y3tmkr1v.fsf@gnu.org> <26eb65ca-4a37-e707-8090-428fd70ac695@cs.ucla.edu> 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 1495665355 17615 195.159.176.226 (24 May 2017 22:35:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 24 May 2017 22:35:55 +0000 (UTC) Cc: Eli Zaretskii , Emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 25 00:35:49 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 1dDese-0004Mc-EC for ged-emacs-devel@m.gmane.org; Thu, 25 May 2017 00:35:48 +0200 Original-Received: from localhost ([::1]:57099 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDesi-0000rS-5Z for ged-emacs-devel@m.gmane.org; Wed, 24 May 2017 18:35:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34292) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDes9-0000rN-8I for Emacs-devel@gnu.org; Wed, 24 May 2017 18:35:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDes8-0000mW-Db for Emacs-devel@gnu.org; Wed, 24 May 2017 18:35:17 -0400 Original-Received: from mail-pf0-x241.google.com ([2607:f8b0:400e:c00::241]:36559) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dDes3-0000kY-P8; Wed, 24 May 2017 18:35:11 -0400 Original-Received: by mail-pf0-x241.google.com with SMTP id n23so34885800pfb.3; Wed, 24 May 2017 15:35:11 -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=hK8G2lh+UU+gS12SHgDrIvVE9I6DYjoiGh/9u+sB1vs=; b=RJaz/6SxGgGO3a/bICUvjzC6CXDa7sn/kfkH0klhSk9pTZUHEAlm2M2H/WMg3C5fdc LJ5IZUD+znB6qAEbwZAMACynky4SJbQnD9VvqdYp0JDSiATvWqRk3PpJlWSq2TULzC90 qzhDiv2Bf3zOjq3cSIrtj2ROJBFqaDqN739RLvT9V4T7KAssCWjA7FChCdHTlIi+1ain sKGlndMLskNcPE2tEJ0ZkLSglO9noTUWXxscW4iXvC/7wb94xVpCADRQMtr/vGmvQzRB jLmcp6V9cvbsKXVuQaCNEIYDuWjkjS86n5HJrYKOP04oVM7eyFhXjRy90wIaiHp5Raa6 qyLw== 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=hK8G2lh+UU+gS12SHgDrIvVE9I6DYjoiGh/9u+sB1vs=; b=n787iOq4/fHatt17Sl23dYevNChm7QdynFu/BEVAf3eEjt/zDLCfgifzUJDVp4q5VJ gDDoTgTcA4sJoY+zjk6SbFavwZDtN8C5QXTcN57bXTE4mWMjo8Q54BAI6BCJV5NdulWg LHeU4apsznIuJI+XhNJuwgaFVdxMfNkxynHoZ3UPqJ4XT8sCqFOdqpz4CV6Jz39YiafU tu8NANC1+OkVU1LkLOUbuwehatf/1Mh5F+UHHSbIwydnFdws7lFkGoTxZNH06GhQ6TSU ggtTKe4OaAQPJQoXKTN55hzcC3Oil/kr0XgDJIYj9c0B0TVybb5wazcdop0yWMhhRbXq q2xQ== X-Gm-Message-State: AODbwcC8tlLm48RDHSSRXeQ8TwFc+5SgEJUdBZENq4XtezULjVqMHMME IAvWvUeg88YxMVkjyZI= X-Received: by 10.84.213.143 with SMTP id g15mr46288870pli.53.1495665310661; Wed, 24 May 2017 15:35:10 -0700 (PDT) Original-Received: from [192.168.24.54] (pl25298.ag0304.nttpc.ne.jp. [133.232.153.210]) by smtp.gmail.com with ESMTPSA id r68sm10596927pfd.91.2017.05.24.15.35.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 May 2017 15:35:09 -0700 (PDT) In-Reply-To: <26eb65ca-4a37-e707-8090-428fd70ac695@cs.ucla.edu> 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::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:215184 Archived-At: > On May 25, 2017, at 7:09, Paul Eggert wrote: >=20 > On 05/24/2017 12:12 PM, Eli Zaretskii wrote: >> He most probably wanted to point out that any infrastructure of >> this kind should at least consider using gettext, if not actually use >> it. >=20 > There is no point to straightening up strings if we don't have a = translation infrastructure. As the title suggests I was talking about better practices for UI = messages regardless of whether we do l10n or not. i18n and l10n are one thing, but having manageable strings that don't = generate grammatical errors because developers consider elisp as a macro = language for Natural Languages is a different thing. It is not even a chicken and egg situation. Fixing strings and setting = rules for developers will benefit all users right now. And we can also = work on i18n, which is a totally different thing and requires a skill = set that I'm pretty sure I don't have right now (while figuring out what = a complex concat does is reasonably within what I can do right now). > In contrast, it would be helpful to have the infrastructure even if = some strings still need straightening up, because the other strings will = be translated. It would be helpful to have a lot of things. But l10n has been discussed = for a while here and nobody is working on it as far as I can tell. > This suggests that we should focus our initial efforts on getting the = infrastructure up, and worry about straightening up strings later. That = is why I suggested gettext in response to your question about where we = should start. No, this suggests that if you're interested in leading the i18n efforts, = you can go ahead. And as I just wrote to Eli, I'm fine with helping in that area but there = are people who are much more qualified in terms of experience with Emacs = and Elisp. My priority right now is to learn about Emacs and Elisp while = helping where I can, and that does not include creating a full i18n = infrastructure on my own. Jean-Christophe=20=