From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Where to contribute manual translations ? (Re: Emacs-devel Digest, Vol 238, Issue 29) Date: Fri, 29 Dec 2023 08:48:51 +0200 Message-ID: <838r5d7bcc.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11780"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, vincent.b.1@hotmail.fr, stefankangas@gmail.com To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 29 07:49:52 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rJ6gq-0002pq-Eg for ged-emacs-devel@m.gmane-mx.org; Fri, 29 Dec 2023 07:49:52 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rJ6g7-0006SG-9x; Fri, 29 Dec 2023 01:49:07 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rJ6g4-0006S8-SH for emacs-devel@gnu.org; Fri, 29 Dec 2023 01:49:04 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rJ6g3-0006RU-T8; Fri, 29 Dec 2023 01:49:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=K5eRHBCC0wjMjjGjEj9u0e7gKQfV6t3/4OfvBDLUt/A=; b=US2gYMZLrWBf g/L5A26mnapMQJWcrKYraZmYqjGA0yuoBwUJGxD1dSGC3aknZ7hhqqyyC6N0atxdU6UZ2dUh0Z+5F gz+JFHI0HQN71pdaj2RisT7OPaJI2ovy8qA8bMe9ywTFOqrwP0ZAEw5Hx6ejIeopzTeqG1rkjFPmE dkv+XRK1T34OkGMMnN2MQl/d11V2CyECsmYGOiho+LT8IKLm0M+Gib2evHJWA2tOu0rqR+6jkWwxo aZtAmRHG2gA6ZrFSg296uu5s9Jv1bijFNvkXJgFvMQcsZZDhpzB4NUXqZlz6bbZVezVGSmqVxmMqS qCfZ+dMgV+8mql6IWl9xTg==; In-Reply-To: (message from Jean-Christophe Helary on Fri, 29 Dec 2023 01:23:40 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314309 Archived-At: > Date: Fri, 29 Dec 2023 01:23:40 +0000 > From: Jean-Christophe Helary > Cc: vincent.b.1@hotmail.fr, stefankangas@gmail.com, eliz@gnu.org > > >> Another question : how to internationalize docstrings ? IMHO it would be great if the docstring could have some info manual anchor in it, and one could display it from the currently selected language manual. Besides, reading docstring from manual via some anchor is basically what Calc does with some kitchen tricks. > > > > Eli answered that. > > There is also a different issue, that comes before translation, it is fixing user facing strings, so that they can eventually be translated one day. I also made a presentation on that at EmacsConf 2022: > https://emacsconf.org/2022/talks/localizing/ I believe this issue was also raised in the discussions whose pointers I provided. AFAIR, this issue is a much harder one, since manipulating such strings is pervasive in Emacs, and mostly in Lisp, not in C.