From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs i18n Date: Tue, 26 Mar 2019 18:11:16 +0200 Message-ID: <831s2tmx97.fsf@gnu.org> 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> <87h8cjspc0.fsf@mail.linkov.net> <29a53a39-fa50-1e94-9420-a3ea1250aa44@gmail.com> <87r2azq478.fsf@mail.linkov.net> <83o963s4gx.fsf@gnu.org> <87va09ckym.fsf@mail.linkov.net> <83sgvdndt0.fsf@gnu.org> <8736ncgcnm.fsf@mail.linkov.net> <5F95E50C-2A55-4ED2-A82B-86FAAFC526ED@gmail.com> <87ef6uod20.fsf@mail.linkov.net> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="149322"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org, brandelune@gmail.com, juri@linkov.net To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 26 17:12:23 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 1h8ogY-000ck2-KW for ged-emacs-devel@m.gmane.org; Tue, 26 Mar 2019 17:12:22 +0100 Original-Received: from localhost ([127.0.0.1]:34562 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8ogX-0000lv-M2 for ged-emacs-devel@m.gmane.org; Tue, 26 Mar 2019 12:12:21 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:56364) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8ofQ-0008Rs-7H for emacs-devel@gnu.org; Tue, 26 Mar 2019 12:11:13 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57412) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8ofP-0001X6-Av; Tue, 26 Mar 2019 12:11:11 -0400 Original-Received: from [176.228.60.248] (port=2999 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h8ofO-0000s1-EH; Tue, 26 Mar 2019 12:11:11 -0400 In-reply-to: (message from Paul Eggert on Mon, 25 Mar 2019 15:31:14 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:234749 Archived-At: > From: Paul Eggert > Date: Mon, 25 Mar 2019 15:31:14 -0700 > Cc: Jean-Christophe Helary , > Emacs developers > > 2. While you're thinking about (1) here are some other questions. How > will ngettext determine the message catalog? Is the catalog visible to > users as a global variable, or as a hidden part of the global state, or > is it something explicit? How will catalogs from multiple packages be > used? How would a multi-lingual application work in Emacs if the message > catalog is part of global state? This seems to be a crucial issue, I'd > say. For example, should Emacs export dcngettext to Lisp code, instead > of just plain ngettext? (Emacs could then define ngettext in terms of > dcngettext.) Do we have any reasons not to follow the CLISP example of factoring these issues? > 5. When calling the C-level ngettext, strings are not properly recoded. Did you mean decoding the translated string that ngettext returns? If so, we will need some way of getting at the encoding of the strings in the catalog, I think. Or will we mandate that Emacs catalogs need always to be in UTF-8 encoding?