From: jsbien@mimuw.edu.pl (Janusz S. Bień)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs帮助邮件列表 <help-gnu-emacs@gnu.org>, "Leo Liu" <467195537@qq.com>
Subject: Re: Is there a translation platform for the Emacs manual
Date: Sat, 09 Jan 2021 18:13:51 +0100 [thread overview]
Message-ID: <87im86jank.fsf@mimuw.edu.pl> (raw)
In-Reply-To: <jwv7domf4mv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 09 Jan 2021 11:39:25 -0500")
On Sat, Jan 09 2021 at 11:39 -05, Stefan Monnier wrote:
>> I'm using its free version and it works pretty well.
>> Those who are interested can come and have a look.
>>
>> https://crowdin.com/project/emacs-manual-chinese <https://crowdin.com/project/emacs-manual-chinese>
>
> Cursory look suggests this is "free as in free beer", i.e. proprietary,
> so not something the Emacs project can recommend (or even just
> point to. Actually even pointing to such services in `help-gnu-emacs`
> is frowned upon).
I was using it some time ago and I think its main advantage is a
dictionary of phrases making reasonable suggestion.
So instead od frowning offer a good alternative. E.g. you can revive
https://web.archive.org/web/20070317101647/http://open-tran.eu:80/
https://web.archive.org/web/20131230040211/http://open-tran.eu/
The code is here
https://github.com/sliwers/open-tran
but requires substantial updating, cf.
https://groups.google.com/forum/#!msg/open-tran/gO_c6ScjMUk/xAAXxFmWEAAJ
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
next prev parent reply other threads:[~2021-01-09 17:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 4:19 Is there a translation platform for the Emacs manual Leo Liu
2021-01-06 5:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-01-06 14:40 ` Takesi Ayanokoji
2021-01-06 14:59 ` =?gb18030?B?UmWjuiBJcyB0aGVyZSBhIHRyYW5zbGF0aW9uIHBsYXRmb3JtIGZvciB0aGUgRW1hY3MgbWFudWFs?= =?gb18030?B?sbzF3LXE0KGy3Q==?=
2021-01-06 15:13 ` Is there a translation platform for the Emacs manual Takesi Ayanokoji
2021-01-06 15:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-01-06 15:45 ` Takesi Ayanokoji
2021-01-06 16:18 ` tomas
2021-01-06 17:05 ` Re： " Stefan Monnier
2021-01-09 15:03 ` Leo Liu
2021-01-09 16:39 ` Stefan Monnier
2021-01-09 17:13 ` Janusz S. Bień [this message]
2021-10-17 10:23 ` Takesi Ayanokoji
2021-10-17 10:47 ` Jean-Christophe Helary
2021-10-17 10:54 ` Takesi Ayanokoji
2021-10-18 10:04 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
2021-10-18 14:25 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
2021-10-18 14:46 ` Jean-Christophe Helary
2021-10-18 16:12 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
2021-01-06 15:13 ` Eli Zaretskii
2021-01-06 15:34 ` Takesi Ayanokoji
2021-01-07 0:50 ` 黃炳熙
2021-01-07 1:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-01-07 9:32 ` Byung-Hee HWANG
2021-01-07 9:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-01-07 3:02 ` 奔跑的小草
2021-01-07 3:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-01-07 9:35 ` 黃炳熙
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=87im86jank.fsf@mimuw.edu.pl \
--to=jsbien@mimuw.edu.pl \
--cc=467195537@qq.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).