From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.emacs.devel Subject: Re: Emacs i18n Date: Sat, 9 Mar 2019 11:44:09 +0900 Message-ID: <75275F9B-D257-4C9E-85A0-A7F57C93FD64@gmail.com> References: <87o97aq6gz.fsf@jidanni.org> <87tvgoud56.fsf@mail.linkov.net> <83o96wk2mi.fsf@gnu.org> <87k1hjfvjd.fsf@mail.linkov.net> <871s3p0zdz.fsf@mail.linkov.net> <83h8ckezyt.fsf@gnu.org> <83o96qegv1.fsf@gnu.org> <32b1ab1b-bef4-629a-8830-b1dcc6915087@cs.ucla.edu> <83a7iae9va.fsf@gnu.org> <05ed2dec-2a84-f7dc-1af5-c9d923992785@cs.ucla.edu> <87bm2p56gu.fsf@mail.linkov.net> <838sxrdgco.fsf@gnu.org> <83mum6bv11.fsf@gnu.org> <87zhq6nwsi.fsf@mail.linkov.net> <8336nxbxfi.fsf@gnu.org> <2539FAB2-2D71-44F5-B8D9-2C4AFE52ACEC@gmail.com> <83wol986to.fsf@gnu.org> Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="88266"; mail-complaints-to="usenet@blaine.gmane.org" To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 09 04:16:18 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h2STC-000MmK-H9 for ged-emacs-devel@m.gmane.org; Sat, 09 Mar 2019 04:16:18 +0100 Original-Received: from localhost ([127.0.0.1]:53311 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h2STB-0000qg-D9 for ged-emacs-devel@m.gmane.org; Fri, 08 Mar 2019 22:16:17 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48353) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h2ST5-0000qP-2o for emacs-devel@gnu.org; Fri, 08 Mar 2019 22:16:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h2ST3-00086B-Mm for emacs-devel@gnu.org; Fri, 08 Mar 2019 22:16:11 -0500 Original-Received: from mail-pf1-x433.google.com ([2607:f8b0:4864:20::433]:38887) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h2ST3-00084O-DK for emacs-devel@gnu.org; Fri, 08 Mar 2019 22:16:09 -0500 Original-Received: by mail-pf1-x433.google.com with SMTP id n125so15498838pfn.5 for ; Fri, 08 Mar 2019 19:16:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=J3U1G72nWW4Bwfggw0bALv5TejTvo45wsnfbau96h+Q=; b=L25rnJp5BEx1gkgWWZ19Nuby9PbuhAlTDoW9fOJ+BFtAw50jGl4HMQdwNpQm/rBkN3 g/v6Ie5Sv9Am8EH0NGZIsub6MBEWUtXFAWq5jkfArB3T4Dw9M48Ow3qq/B3LTL03p46V 4XEJ8nWkionlroMR06i/76Pg/YBnEZVCxmdkijFnlZeNdH/UBszghsBgRqARtF1iPb3Z 0PJMdNsPmal4RY9AxnMbx6X1ZAzCmfc5jiTOlgh171V9eN0kz1zVhzodIr4IL5mPq06b Bv2j4vAnr+CQkCCNbdB09ccxDX4guyWyPfuuu0LjQpkffr8jhVwlsL9U0mxRsbFtIlzM pJ8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=J3U1G72nWW4Bwfggw0bALv5TejTvo45wsnfbau96h+Q=; b=iu7uc3SsUXIglDKjhNJouZBR0hRy1YwYVSiT/FFFgG5q1bAbGNXUPrfdONnJnvx8O3 Dj4m2+4A9+K0Wz6T9aL6Itn57sUKEI/AvGzdJNEvmPVaQSB72++DM4ZJlWb5Edg4NP2I 1a82mxeCPHiRrYYGnkQJIriNVB7szZ08Va/gecAAgGL9BBgg2ZpVk/SLR1zcUC4zYecH cqTCmS2AvCj4lrs7Plzqs/3pLIBXdQqDb7I9YEcWhcVW8GzJhUBT4K6A/Pto2yaPDXAe muheJlTTyTSSIQ3YjY26dCUmb5WC3I6qktsWCKz1f2AQgvchP+zvGae3YULrTgYKHR9v l24w== X-Gm-Message-State: APjAAAU+StimX+NJoknFRLbiX7g7C320ndgnkKkTdgHbZQJZaCdllbDC Pob3gm/D0Im9SPqqWek65E/gLanP X-Google-Smtp-Source: APXvYqyH+VnR4i7ddXNfM4CUChBpeeZDXjo8XF5GWh8p0TkrAcpzaQX0Atiz0sHCAQduQSFe49tFDg== X-Received: by 2002:a17:902:2a48:: with SMTP id i66mr21552754plb.14.1552101367365; Fri, 08 Mar 2019 19:16:07 -0800 (PST) Original-Received: from [10.0.2.11] (y175126.ppp.asahi-net.or.jp. [118.243.175.126]) by smtp.gmail.com with ESMTPSA id f192sm32476073pfc.180.2019.03.08.19.16.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Mar 2019 19:16:06 -0800 (PST) In-Reply-To: <83wol986to.fsf@gnu.org> X-Mailer: Apple Mail (2.3445.102.3) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::433 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:233944 Archived-At: > On Mar 9, 2019, at 5:11, Eli Zaretskii wrote: >=20 >> From: Jean-Christophe Helary >> Date: Sat, 9 Mar 2019 00:11:24 +0900 >>=20 >>> Extraction is just a technicality, it can be done in either of = several possible ways. >>=20 >> Sure. I just meant that l10n issues (is PO "efficiency", etc.) are = already solved, but i18n in general has to be implemented from scratch. >=20 > No sure I understand: what part(s) we would need to implement from = scratch? We already have the capability of inserting arbitrary = non-ASCII text into any buffer and displaying such text as echo area = messages. What I mean by "from scratch" is that we have the possibility to extract = text and insert text, but i18n is inexistant in emacs. So we have to = build an i18n system that works for emacs and that does not exist yet, = at all. Also, the "how to load catalogs on demand" point that you mention below = is part of i18n and as you seem to say has to be developed from scratch. >>> and (b) how to arrange the message catalogs so that they will be = easy to maintain and update, given the modular nature of Emacs. >>=20 >> I'm not sure what you mean in "how to arrange ..." Do you mean: how = to provide the l10n packages to translator communities ? >=20 > No, I mean how many catalogs should we have and what should be their = granularity. Isn't that related to the below item ? > Also, how to merge several catalogs (the need for this might disappear = if, for example, we decide that each .el file will have its own = catalog), Won't this depend on the extracting tool's options ? And wouldn't that = be more practical in the first place to not merge anything but have one = catalog per .el file ? (practical in terms of = translation/testing/management, as far as I can tell from experience, = etc.) > and how to load catalogs on demand when the corresponding code is = loaded/executed. I guess you mean the technicalities involved in the obvious (?) "we = check the user preferred locale and display the catalog corresponding to = that locale" ? >> Can't we start with a survey of the strings we want extracted in a = given number of emacs core packages ? >=20 > How would such a survey help us? We generally want all of the strings = that are displayed to the user translated. We don't need any survey for = that decision. Of course, but a survey (sorry, I don't have a better word) of a few = packages can help us see the workload, build prototypes, test them, = establish best practices for developers, etc. Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune