From: Jean-Christophe Helary <brandelune@gmail.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Localized org-mode
Date: Sat, 12 May 2018 09:29:41 +0900 [thread overview]
Message-ID: <5EE3D3F1-C41E-4BBA-BEEE-9964359929CA@gmail.com> (raw)
In-Reply-To: <ygmpo217rx4.fsf@gkayaalp.com>
[-- Attachment #1: Type: text/plain, Size: 2750 bytes --]
> On May 12, 2018, at 7:23, Göktuğ Kayaalp <self@gkayaalp.com> 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?
>>
>> There are no practical reasons why that should not be possible. The
>> current state of affairs is only due to design constraints when the
>> languages were conceived.
>>
>> In Scheme, for ex. you can actually redefine all the language keywords
>> very easily without any impact on the interpreter.
>
> Practical reason: communication. I'm a Turkish speaker, suppose I'm
> monolingual, and I have a problem with the function
> ‘güncel-devamla-çağır’ in Scheme.
If you have a problem with that function and you use Scheme, you know that it is mapped to call-with-current-continuation and you know where to look for information. And if you're monolingual, chances are that you won't be able to make sense of what you find in English.
> The language of programming is English.
And of course, when 2 Turkish programmers talk about programming they shift to English... No, they don't. Keywords are arbitrary strings. Try APL and see how "English" applies.
> Org allows drawers with
> arbitrary names to be defined (e.g. I have :remotes:\n...\n:end: or
> :NEXT:\n...\n:END: in a file), with a couple names like :PROPERTIES: and
> :LOGBOOK: reserved. This means that you can't reliably know if anybody
> has :PROPRIÉTÉS: or :PROPRIETÀ:, which renders translations impossible.
> Same thing with todo keywords, tags, etc.
And that is a good thing.
>> Localization, when properly done is never a nightmare to maintain.
>
> I appreciate your efforts on i18n and l10n on Emacs, but unfortunately I
> am yet to find a properly localised piece of software, especially in the
> FOSS community.
Proprietary software has so many issues that most pro-grade software is not even localized.
> Also, when I need help online, I need the English
> messages anyways (and translated manuals, if they ever exist, are a joke
> all the time).
If FOSS activists took as much time fixing manuals as they take for fixing code that would not be an issue. l10n is not as good as code *because* it is not defined with a higher priority and a better consciousness of the linguistic issues, and that is because monolingual activists think one language is sufficient (funny how that does not apply to programming languages, but they don't seem to be conscious of that contradiction...)
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
[-- Attachment #2: Type: text/html, Size: 5164 bytes --]
next prev parent reply other threads:[~2018-05-12 0:29 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5EE3D3F1-C41E-4BBA-BEEE-9964359929CA@gmail.com \
--to=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.