From: 奔跑的小草 <467195537@qq.com>
To: 黃炳熙 <soyeomul@vladivostok.yw.doraji.xyz>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Is there a translation platform for the Emacs manual
Date: Thu, 7 Jan 2021 11:02:10 +0800 [thread overview]
Message-ID: <tencent_AF868948C1E8834C9EE6188742AC32289D06@qq.com> (raw)
In-Reply-To: <yw9dgjdpkia.fsf@vsyjk.oak-birch>
hi.
I think that there must be a manual in the local language first, and then a tutorial. After all, the tutorial is to summarize and simplify.
If you need to know more about the specific content, no manual would be very unfriendly.
And, the tutorial is for personal understanding of a certain version. It will be outdated and subjectively judged.
So I think the manual is more important than the tutorial.
------------------ Original ------------------
From: "黃炳熙" <soyeomul@vladivostok.yw.doraji.xyz>;
Date: Thu, Jan 7, 2021 08:50 AM
To: "help-gnu-emacs"<help-gnu-emacs@gnu.org>;
Subject: Re: Is there a translation platform for the Emacs manual
Leo Liu <467195537@qq.com> writes:
> hi，friends
>
> I am translating the Emac manual into Chinese and I have completed 10 chapters
>
> I want to know if the project has a unified translation platform or plan？Avoid duplication of work。
Because Emacs key-binding(s) are so diffcult, normal users don't touch
Emacs i guess. Rather than, i think it is better to make tutorial in
local languages such as Chinese, Japanese, Korean, etc. ...
It was another opinion.
Sincerely, Gnus fan Byung-Hee
--
^고맙습니다 _地平天成_ 감사합니다_^))//
next prev parent reply other threads:[~2021-01-07 3:02 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ń
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 ` 奔跑的小草 [this message]
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=tencent_AF868948C1E8834C9EE6188742AC32289D06@qq.com \
--to=467195537@qq.com \
--cc=help-gnu-emacs@gnu.org \
--cc=soyeomul@vladivostok.yw.doraji.xyz \
/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).