unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ruijie Yu <ruijie@netyu.xyz>
Cc: xfq.free@gmail.com, lx@shellcodes.org, emacs-devel@gnu.org
Subject: Re: Comments on TUTORIAL (was: [PATCH] updates to TUTORIAL.cn)
Date: Fri, 21 Apr 2023 10:17:30 +0300	[thread overview]
Message-ID: <83ildp4sc5.fsf@gnu.org> (raw)
In-Reply-To: <sdvfs8tyaoo.fsf@netyu.xyz> (message from Ruijie Yu on Fri, 21 Apr 2023 15:01:30 +0800)

> From: Ruijie Yu <ruijie@netyu.xyz>
> Cc: xfq.free@gmail.com, lx@shellcodes.org, emacs-devel@gnu.org
> Date: Fri, 21 Apr 2023 15:01:30 +0800
> 
> > Think about what, exactly?  If the Chinese text is simply a
> > translation of the English text, then the above comment seems to be
> > about the original English text, not about the translation, in which
> > case it should be discussed separately, not as part of improving the
> > Chinese translation of the tutorial.  If the Chinese text added some
> > explanations to the original English text, and the comment is about
> > those additions, then please tell in English what was added, and we
> > can then ask for opinions on those additions.
> 
> In my mind, being "discussed separately" means sending a separate email
> about it, which I did.  I sent two emails at the same time: one is this
> email (concerning the English version), and the other is purely about
> the quality of the Chinese translation.
> 
> From your wording, it seems that you also want to have this discussion
> in an unrelated, separate thread instead, correct?  If so, I will do
> that in a few hours when I am free again.

Yes.  I would like to install the updated Chinese translation of the
tutorial when there are no more comments about the translation and the
changes you are suggesting.  The more general issue of what should the
original English text of the tutorial say should be a subject of a
separate thread.

If there are no more issues related to the translation itself, would
you please post an updated patch for TUTORIAL.cn, so that I could
install that?  TIA



  reply	other threads:[~2023-04-21  7:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sdv8reovawk.fsf@netyu.xyz>
2023-04-19  3:08 ` [PATCH] updates to TUTORIAL.cn Ruijie Yu via Emacs development discussions.
2023-04-19  8:22   ` lux
2023-04-20  4:29   ` Ruijie Yu via Emacs development discussions.
2023-04-20 11:33     ` Eli Zaretskii
2023-04-20 14:22       ` Ruijie Yu via Emacs development discussions.
2023-04-21  0:20         ` Fuqiao Xue
2023-04-21  0:28           ` Ruijie Yu via Emacs development discussions.
2023-04-21  5:11             ` Ruijie Yu via Emacs development discussions.
2023-04-22  2:43               ` Fuqiao Xue
2023-04-22  4:21                 ` Ruijie Yu via Emacs development discussions.
2023-04-23  0:31                   ` Fuqiao Xue
2023-04-25  7:26                     ` [PATCH v6] " Ruijie Yu via Emacs development discussions.
2023-04-27  0:30                       ` Fuqiao Xue
2023-04-27 14:31                         ` Ruijie Yu via Emacs development discussions.
2023-04-28  6:12                           ` Eli Zaretskii
2023-04-21  5:12             ` Comments on TUTORIAL (was: [PATCH] updates to TUTORIAL.cn) Ruijie Yu via Emacs development discussions.
2023-04-21  6:44               ` Eli Zaretskii
2023-04-21  7:01                 ` Ruijie Yu via Emacs development discussions.
2023-04-21  7:17                   ` Eli Zaretskii [this message]
2023-04-21  8:26                     ` Ruijie Yu via Emacs development discussions.
2023-04-20  0:56 ` [PATCH] updates to TUTORIAL.cn Fuqiao Xue
2023-04-20  1:07   ` Fuqiao Xue

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=83ildp4sc5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lx@shellcodes.org \
    --cc=ruijie@netyu.xyz \
    --cc=xfq.free@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).