From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs user manual in Spanish
Date: Mon, 03 Jul 2017 01:52:50 +0200 [thread overview]
Message-ID: <87k23qxup9.fsf@debian.uxu> (raw)
In-Reply-To: 87shiebe96.fsf@wanadoo.es
Óscar Fuentes <ofv@wanadoo.es> writes:
> You seem to think that Emacs is just a programmer's
> tool. This is wrong.
Being a programmer and being a serious Emacs user to
the point as to read the manual isn't a big difference
to me. It is both about being active with the best and
most advanced tools. Both personalities, if indeed
distinct, are vastly benefited from acquiring English.
As is actually evident from this very discussion!
> I suspect that if you ask Stallman, he would say
> that Emacs should be amenable to anyone who works
> with computers for any text-editing task.
Well, the next time Stallman has anything to say maybe
he can post a message of his own?
> The fact that Emacs has a wide acceptance as
> a programmer's tool but it is a not so popular text
> editor for other purposes is a consequence of a lack
> of development resources
At least that's one of many reasons.
> which also explains why there are no translations of
> the manual.
Indeed, if we could have professional tech translators
do it, do it well and complete, and keep it updated,
I would agree it would be good. I mean, any sufficiently
cool Spaniard could still pick up the English edition.
But there would be an option on an equal basis.
However, that isn't the case. As it is now, when
translations being at the enthusiast, spare-time
level, it is better to focus such desires on FAQs,
introductory text, and culture books, as this will
groom in people and act as a front.
When they are ready to take their game to the next
level, we'll have the reference and manual material
right at their fingertips.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-07-02 23:52 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k23qxup9.fsf@debian.uxu \
--to=moasen@zoho.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.
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).