From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: Localized org-mode Date: Wed, 09 May 2018 12:07:36 +0000 Message-ID: References: <1525784567.2021.47.camel@gmail.com> <87bmdqtf01.fsf@nicolasgoaziou.fr> <1525801068.2021.56.camel@gmail.com> <87bmdqrosp.fsf@nicolasgoaziou.fr> <1525851919.2021.66.camel@gmail.com> <877eodutq2.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000005055ca056bc4c0e2" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43029) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fGNss-0004Q0-F1 for emacs-orgmode@gnu.org; Wed, 09 May 2018 08:07:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fGNsr-0001Y5-Di for emacs-orgmode@gnu.org; Wed, 09 May 2018 08:07:50 -0400 Received: from mail-lf0-x22d.google.com ([2a00:1450:4010:c07::22d]:45331) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fGNsr-0001V7-5c for emacs-orgmode@gnu.org; Wed, 09 May 2018 08:07:49 -0400 Received: by mail-lf0-x22d.google.com with SMTP id q2-v6so5405681lfc.12 for ; Wed, 09 May 2018 05:07:49 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Diego Zamboni Cc: Org-mode , ST , Nicolas Goaziou --0000000000005055ca056bc4c0e2 Content-Type: text/plain; charset="UTF-8" Hello all, On Wed, May 9, 2018, 8:01 AM Diego Zamboni wrote: > I really don't see the point of trying to localize org keywords. To me, > they are like the keywords in any programming language - part of the > language. Would you consider translating C or LISP keywords? > > In addition to the trouble of supporting something like this within Emacs, > think of the growing ecosystem of tools which support org mode - they would > all need to be aware of these localizations. It would be a nightmare to > maintain. > So much +1 on that! Supporting multi-language keywords will make it difficult for 3rd party Org parsers to adopt them too, resulting in even lesser Org adoption. I like Nicolas' idea where display properties are used to replace the English keywords with the translation; that way the actual Org source remains untouched. > -- Kaushal Modi --0000000000005055ca056bc4c0e2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello all,

= On Wed, May 9, 2018, 8:01 AM Diego Zamboni <diego@zzamboni.org> wrote:
I really don't see the point of trying to loc= alize org keywords. To me, they are like the keywords in any programming la= nguage - part of the language. Would you consider translating C or LISP key= words?

In addition to the trouble of supporting somethin= g like this within Emacs, think of the growing ecosystem of tools which sup= port org mode - they would all need to be aware of these localizations. It = would be a nightmare to maintain.

So much +1 on that! Supporting multi-language keywords will make i= t difficult for 3rd party Org parsers to adopt them too, resulting in even = lesser Org adoption.=C2=A0

I like Nicolas' ide= a where display properties are used to replace the English keywords with th= e translation; that way the actual Org source remains untouched.=C2=A0
--

Kaushal Modi

--0000000000005055ca056bc4c0e2--