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 (was: bug#34520: delete-matching-lines should report how many lines it deleted) Date: Mon, 04 Mar 2019 21:07:53 +0200 Message-ID: <83a7iae9va.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> <83o96qegv1.fsf@gnu.org> <32b1ab1b-bef4-629a-8830-b1dcc6915087@cs.ucla.edu> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="10531"; mail-complaints-to="usenet@blaine.gmane.org" Cc: juri@linkov.net, rms@gnu.org, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 04 21:07:01 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 1h0trY-0002bi-TH for ged-emacs-devel@m.gmane.org; Mon, 04 Mar 2019 21:07:01 +0100 Original-Received: from localhost ([127.0.0.1]:60250 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h0trX-0000Ho-PF for ged-emacs-devel@m.gmane.org; Mon, 04 Mar 2019 15:06:59 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60414) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h0swZ-0008R6-ED for emacs-devel@gnu.org; Mon, 04 Mar 2019 14:08:09 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h0swX-0007IC-OE; Mon, 04 Mar 2019 14:08:05 -0500 Original-Received: from [176.228.60.248] (port=4665 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h0swR-00055y-19; Mon, 04 Mar 2019 14:07:59 -0500 In-reply-to: <32b1ab1b-bef4-629a-8830-b1dcc6915087@cs.ucla.edu> (message from Paul Eggert on Mon, 4 Mar 2019 10:37:31 -0800) 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:233825 Archived-At: > Cc: emacs-devel@gnu.org, juri@linkov.net > From: Paul Eggert > Date: Mon, 4 Mar 2019 10:37:31 -0800 > > On 3/4/19 8:36 AM, Eli Zaretskii wrote: > > For example, it is IMO pointless to be able to display translated > > strings from 'message' without also having a convenient automated way > > of collecting translatable messages and creating a message catalog > > that such a 'message' could use > > There is longstanding technology to do that for C code. We could apply > that to Emacs, and then at least the builtin C-level messages will be > translated. Later, we could extend this to Elisp. I'm saying that IMO it makes no sense at all to do this only for C. The infrastructure used for that will most probably not work for Lisp, let alone allow separate translations for separate packages to be brought together and used in the same Emacs session.