From: Diego Zamboni <diego@zzamboni.org>
To: Jean-Christophe Helary <brandelune@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Localized org-mode
Date: Wed, 9 May 2018 17:41:26 +0200 [thread overview]
Message-ID: <CAGY83EfVD-Zs+yke5rSOb5pq80Gjj2az5rtFHpJ=f=d_kceXHg@mail.gmail.com> (raw)
In-Reply-To: <236BE792-CCFF-452A-950A-CC4D3A139978@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
On Wed, May 9, 2018 at 3:48 PM, Jean-Christophe Helary <brandelune@gmail.com
> wrote:
> You misquoted me. I was talking about design constraints when C and Lisp
> were created, which kept language creators from "inventing" proper language
> localization. I was specifically replying to Diego Zamboni regarding that.
>
I don't think it was only those constraints. Imagine if C and LISP had been
designed with "keywords in your own language" in mind. I'm pretty surre
that would have largely impeded the proliferation of compilers/interpreters
that made possible the explosion of those, and many other, languages.
I fully agree with Nicolas that in this context, localization should be a
display problem and not involve modifying the source. Take for example the
educational language Scratch (https://scratch.mit.edu/), in which you can
localize the language (i.e. the blocks with which you build your programs).
However, if you download the source for your program (it's a JSON file),
it's always the same, no matter in which language you have the interface.
As a first step, you can already configure Emacs so that the markup is
minimally visible. Look at this screenshot, for example:
http://zzamboni.org/post/beautifying-org-mode-in-emacs/emacs-init-propfonts.png.
Most of the formatting is visually communicated, you can only see a few
keywords (properties, begin_src, etc.). It really is very non-intrusive in
my opinion.
--Diego
[-- Attachment #2: Type: text/html, Size: 2211 bytes --]
next prev parent reply other threads:[~2018-05-09 15:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 13:02 Localized org-mode ST
2018-05-08 14:10 ` Nicolas Goaziou
2018-05-08 17:37 ` ST
2018-05-08 18:21 ` Nicolas Goaziou
2018-05-09 7:45 ` ST
2018-05-09 8:19 ` Nicolas Goaziou
2018-05-09 11:36 ` Diego Zamboni
2018-05-09 12:07 ` Kaushal Modi
2018-05-09 12:43 ` Jean-Christophe Helary
2018-05-09 13:25 ` Nicolas Goaziou
2018-05-09 13:48 ` Jean-Christophe Helary
2018-05-09 15:41 ` Diego Zamboni [this message]
2018-05-09 23:36 ` Jean-Christophe Helary
2018-05-09 20:28 ` Kaushal Modi
2018-05-11 22:23 ` Göktuğ Kayaalp
2018-05-12 0:29 ` Jean-Christophe Helary
2018-05-12 11:07 ` Göktuğ Kayaalp
2018-05-12 11:58 ` Jean-Christophe Helary
2018-05-12 19:24 ` ST
2018-05-12 22:48 ` Göktuğ Kayaalp
2018-05-12 23:48 ` Jean-Christophe Helary
2018-05-09 12:34 ` ST
2018-05-21 14:44 ` Rasmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGY83EfVD-Zs+yke5rSOb5pq80Gjj2az5rtFHpJ=f=d_kceXHg@mail.gmail.com' \
--to=diego@zzamboni.org \
--cc=brandelune@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).