From: Devin Prater <r.d.t.prater@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs user manual in Spanish
Date: Sun, 02 Jul 2017 23:52:14 -0500 [thread overview]
Message-ID: <8760faunpd.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <5ac97eb4-d897-4c35-b095-e76250398400@default> (Drew Adams's message of "Sun, 2 Jul 2017 15:02:46 -0700 (PDT)")
Here is one little suggestion: Why not try using Google Translate for
the roughest, but most complete start, then have people clean it up
where necisary?
--
Devin Prater
assistive Technology Instructor in training
World services for the blind
Drew Adams <drew.adams@oracle.com> writes:
>> Manuals are very tricky if they should be
>> translated or not.
>>
>> In a perfect world the Emacs techno-science
>> conglomerate would hire professional tech
>> translators to get the job done.
>>
>> However, in the imperfect anomaly which is the
>> current realm, those efforts are put on
>> enthusiasts that often underestimate the effort
>> and time to do a complete, proofread
>> translation. And when it comes to a manual, an
>> incomplete one may often be an injustice.
>
> An incomplete - or badly translated - manual might
> be an injustice. But it might still be useful.
> And an incomplete manual is not necessarily an injustice.
>
> Not really wanting to get into this discussion (in
> particular, I know nothing about it), here is a
> comment anyway.
>
> Rather than viewing that task as all-or-nothing:
> (1) translate an entire manual and (2) keep it
> up-to-date, perhaps an incremental, informal,
> contributor-best-effort approach could be taken.
>
> That's how it works on Emacs Wiki, for example.
> Users interested in translating a given wiki page
> do so. They need not be interested, qualified, or
> have the time to translate other pages. Every
> contribution can help. And others can then update
> pages or fix both technical and translation bugs.
>
> Perhaps the HTML GNU Emacs manuals could offer a
> similar possibility: Allow for anyone to translate
> a given section into a given language, or update
> such a translated section.
>
> There could also be a "locked" version of such a
> page, which is deemed pretty good at some point and
> serves as an informal reference, while an unlocked,
> "sandbox" version is open for anyone to improve upon.
>
> This wouldn't preclude any systematic, thorough
> translation effort. It would offer something less
> but easier for people to contribute to. GNU would
> not need to swear by the authority or authenticity
> of such doc. But it could still be quite helpful.
>
> Presumably anyone could already work on this, just
> by creating Emacs-Wiki pages that are translations
> of manual sections. IOW, it wouldn't even need to
> be hosted by GNU. Dunno whether there are copyright
> considerations that get in the way in that case,
> however.
>
> Just an idea.
next prev parent reply other threads:[~2017-07-03 4: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
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 [this message]
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=8760faunpd.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me \
--to=r.d.t.prater@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.