From: "Héctor Lahoz" <hectorlahoz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs user manual in Spanish
Date: Tue, 4 Jul 2017 10:24:36 +0200 [thread overview]
Message-ID: <20170704082436.GA3227@workstation> (raw)
In-Reply-To: <8637aexz6l.fsf@zoho.com>
Emanuel Berg wrote:
> And: Why wouldn't Spanish-speaking programmers
> and user of advanced technology acquire
> English? Many, many have already done so and in
> one or two generations it will be even
> more widespread.
I like English for its simplicity. And it is clear
that we need a universal language. And I think
English is a good choice. But free software is
about freedom. I don't like people who try to
impose their thoughts or their language. If
someone doesn't want to invest time and effort to
acquire some language, he is in his right. And I
think it would be good that someone who doesn't
speak English could use Emacs efficiently for
non-programming tasks. I'm not talking about
translating commands which would be (maybe)
nonsense. But the manual is the starting point.
I think it should be available in other languages.
Not just Spanish.
> If they don't, it is a huge mistake on their
> part and translating the manual won't help, I'm
> afraid. No, trust the people. Every programmer
> on this planet will soon know good
> enough English!
I agree.
But bear in mind that Emacs is not just for
programmers. All the modes for human languages can
be used by non-programmers. And many users of
Emacs are not programmers.
next prev parent reply other threads:[~2017-07-04 8:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 8:24 Emacs user manual in Spanish Héctor Lahoz
2017-07-02 19:08 ` Emanuel Berg
2017-07-02 22:02 ` Drew Adams
2017-07-02 22:16 ` Emanuel Berg
2017-07-02 22:30 ` Jean-Christophe Helary
2017-07-02 22:40 ` Emanuel Berg
2017-07-02 23:14 ` Jean-Christophe Helary
2017-07-02 23:27 ` Emanuel Berg
2017-07-02 23:39 ` Óscar Fuentes
2017-07-02 23:52 ` Emanuel Berg
2017-07-03 1:49 ` Jean-Christophe Helary
2017-07-03 2:32 ` Emanuel Berg
2017-07-03 3:30 ` Jean-Christophe Helary
2017-07-03 4:01 ` Emanuel Berg
2017-07-03 13:58 ` Aurélien Aptel
2017-07-03 14:04 ` Jean-Christophe Helary
2017-07-03 18:20 ` Nick Dokos
2017-07-03 22:44 ` Jean-Christophe Helary
2017-07-04 9:49 ` Emanuel Berg
2017-07-04 9:59 ` Jean-Christophe Helary
2017-07-04 11:20 ` Emanuel Berg
2017-07-05 17:54 ` Nick Dokos
2017-07-05 23:01 ` Jean-Christophe Helary
2017-07-06 13:27 ` Nick Dokos
2017-07-06 13:37 ` Stephen Berman
2017-07-06 15:05 ` Emanuel Berg
2017-07-06 16:34 ` Nick Dokos
2017-07-06 16:59 ` Emanuel Berg
2017-07-06 17:16 ` Óscar Fuentes
2017-07-06 19:45 ` Emanuel Berg
2017-07-06 21:56 ` Jean-Christophe Helary
2017-07-06 17:01 ` Óscar Fuentes
2017-07-06 19:33 ` Nick Dokos
2017-07-06 21:59 ` Jean-Christophe Helary
2017-07-06 22:51 ` Emanuel Berg
2017-07-03 16:53 ` Emanuel Berg
2017-07-03 17:39 ` Emanuel Berg
2017-07-03 18:41 ` Devin Prater
2017-07-03 20:09 ` Emanuel Berg
2017-07-03 21:01 ` Drew Adams
2017-07-07 16:19 ` Jean Louis
2017-07-04 8:24 ` Héctor Lahoz [this message]
2017-07-04 9:41 ` Emanuel Berg
2017-07-02 22:21 ` Jean-Christophe Helary
2017-07-02 22:32 ` Drew Adams
2017-07-03 5:22 ` Alex Schroeder
2017-07-03 5:42 ` Jean-Christophe Helary
2017-07-02 22:35 ` Emanuel Berg
2017-07-02 22:50 ` Jean-Christophe Helary
2017-07-02 23:17 ` Emanuel Berg
2017-07-02 23:26 ` Jean-Christophe Helary
2017-07-02 23:31 ` Emanuel Berg
2017-07-03 1:49 ` Jean-Christophe Helary
2017-07-07 16:28 ` Jean Louis
2017-07-07 17:37 ` Emanuel Berg
2017-07-03 4:52 ` Devin Prater
2017-07-03 5:11 ` Jean-Christophe Helary
2017-07-03 5:37 ` Emanuel Berg
2017-07-07 16:31 ` Jean Louis
2017-07-03 5:33 ` Emanuel Berg
2017-07-07 16:30 ` Jean Louis
2017-07-03 9:39 ` Héctor Lahoz
2017-07-03 10:17 ` Emanuel Berg
2017-07-07 16:38 ` Jean Louis
2017-07-07 17:26 ` Emanuel Berg
2017-07-08 0:57 ` Jean-Christophe Helary
2017-07-08 13:30 ` Emanuel Berg
2017-07-07 19:05 ` Emanuel Berg
2017-07-08 7:25 ` Yuri Khan
2017-07-08 13:32 ` Emanuel Berg
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=20170704082436.GA3227@workstation \
--to=hectorlahoz@gmail.com \
--cc=help-gnu-emacs@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.