unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: matthewzmd@posteo.net, emacs-devel@gnu.org, ksqsf@mail.ustc.edu.cn
Subject: Re: etc/HELLO: On Chinese and Cantonese
Date: Thu, 22 Oct 2020 16:21:49 +0300	[thread overview]
Message-ID: <83wnzil7ki.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmZMqJERVSaUMFkghPzw3wFHLPBCBcTsr8-DMEXg3K7VA@mail.gmail.com> (message from Stefan Kangas on Thu, 22 Oct 2020 04:45:23 -0700)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 22 Oct 2020 04:45:23 -0700
> Cc: emacs-devel@gnu.org
> 
> > Therefore I propose to rmeove the Cantonese line entirely, and change
> > "(中文,普通话,汉语)" to "(中文)"
> 
> The purpose of the HELLO file is to demonstrate the capabilities of
> Emacs to display various scripts (and detect problems in that support).

Indeed.  Therefore, the requirement to be in line with how the
speakers of a particular language would say Hello is secondary.

> As far as I understand, written Chinese is pretty much always the same
> but there are two ways to write the characters: traditional and
> simplified.  In contrast, the spoken languages (of which there are many)
> can be completely different.
> 
> So perhaps we should ideally just replace "Chinese" and "Cantonese" with
> these two entries:
> 
> Chinese (simplified)
> Chinese (traditional)
> 
> And then try to find some greetings that are actually different in the
> two scripts.  I don't think they need to be natural in spoken language,
> but they would have to be technically correct in the written language.
> If they are unusual, that is fine, because the purpose is mostly to show
> the difference between the scripts.
> 
> Does that proposal make sense?

AFAIR, there are some non-trivial aspects here, some of them political
and even ideological.  There's PRC and there's ROC (a.k.a. Taiwan),
and I'm not sure what will each group say about the proposed changes.

So unless we have a representative group of Chinese speakers from both
camps (traditional and simplified), and they agree on some change
without any controversies, I'd rather not touch this ticking bomb with
a 3-mile stick.  The current text might not be 100% accurate, but it
has been there for many years.  I'd rather not risk causing a
diplomatic incident by a change in Emacs.



  reply	other threads:[~2020-10-22 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  6:25 etc/HELLO: On Chinese and Cantonese Kai Ma
2020-10-22  6:45 ` Mingde (Matthew) Zeng
2020-10-22 11:45   ` Stefan Kangas
2020-10-22 13:21     ` Eli Zaretskii [this message]
2020-10-22 15:35       ` Stefan Kangas
2020-10-22 15:58         ` Werner LEMBERG
2020-10-22 15:44       ` Yuan Fu
2020-10-22 17:29       ` Eric Abrahamsen
2020-10-22 20:37         ` Karl Fogel
2020-10-23  3:41       ` Richard Stallman
2020-10-23  6:56         ` Eli Zaretskii
2020-10-23  7:55           ` Mingde (Matthew) Zeng
2020-10-23 10:57             ` Eli Zaretskii
2020-10-23 11:16           ` Basil L. Contovounesios
2020-10-23 11:30             ` Eli Zaretskii
2020-10-23 16:27               ` Eric Abrahamsen
2020-10-22 23:03     ` Mingde (Matthew) Zeng
2020-10-22 15:46   ` Yuan Fu

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=83wnzil7ki.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ksqsf@mail.ustc.edu.cn \
    --cc=matthewzmd@posteo.net \
    --cc=stefankangas@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).