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: Wed, 06 Mar 2019 20:15:44 +0200 Message-ID: <837edbdg33.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> <83a7iae9va.fsf@gnu.org> <05ed2dec-2a84-f7dc-1af5-c9d923992785@cs.ucla.edu> <87bm2p56gu.fsf@mail.linkov.net> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="45297"; mail-complaints-to="usenet@blaine.gmane.org" Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, juri@linkov.net To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 06 19:26: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 1h1bEt-000BdD-NF for ged-emacs-devel@m.gmane.org; Wed, 06 Mar 2019 19:25:59 +0100 Original-Received: from localhost ([127.0.0.1]:37366 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h1bEs-0005sH-HL for ged-emacs-devel@m.gmane.org; Wed, 06 Mar 2019 13:25:58 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60599) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h1b5D-0007W3-Je for emacs-devel@gnu.org; Wed, 06 Mar 2019 13:16:00 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46729) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h1b5A-0000MZ-UJ; Wed, 06 Mar 2019 13:15:58 -0500 Original-Received: from [176.228.60.248] (port=3935 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h1b54-0004LW-9p; Wed, 06 Mar 2019 13:15:50 -0500 In-reply-to: (message from Richard Stallman on Tue, 05 Mar 2019 21:16:07 -0500) 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:233866 Archived-At: > From: Richard Stallman > Cc: eggert@cs.ucla.edu, eliz@gnu.org, emacs-devel@gnu.org > Date: Tue, 05 Mar 2019 21:16:07 -0500 > > We could recognize all strings passed as certain arguments to certain > functions as translatable automatically, and have an explicit > way to mark other strings as translatable. That could reduce > the amount of work for developers to mark them. You mean, the function, such as 'message', that receives the string will translate it? As opposed to the alternative of translating the string _before_ it gets passed to the function? If we do that, how do we deal with strings that are computed by concatenation or formatting? They get in one piece to functions like 'message', but the catalog will not hold that concatenated string, it will have the parts separately. How will the function be able to look up the translation in such cases?