unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leonard Lausen <leonard@lausen.nl>
To: 27505@debbugs.gnu.org
Subject: bug#27505: acknowledged by developer (Re: bug#27505: LC_CTYPE affects tutorial language)
Date: Sat, 5 Aug 2017 10:54:37 +0900	[thread overview]
Message-ID: <d6543bc3-a8f2-f825-7a5b-4d1f4f0a66fb@lausen.nl> (raw)
In-Reply-To: <handler.27505.C.150189707129878.notifdonectrl.0@debbugs.gnu.org>

Please reopen this bug. Unfortunately my previous reply was only sent to
Andreas, but not to the bug list. I am attaching it below. A short
summary is that emacs is assuming the language I occasionally need to
input is also the language I want to read by default, which is a wrong
assumption. Note that its not possible to input Chinese characters in
emacs without setting LC_CTYPE to zh_CN.


Thanks Andreas and Eli for the prompt reply.

In that case though I believe the intended emacs behavior does not make
sense. Given that I need to set LC_CTYPE=zh_CN.UTF-8 just to make it
possible to use input system input methods for Chinese characters
doesn't mean I want to actually use a Chinese language interface.

Or concretely, I am learning Chinese and am comfortable typing it or
having daily conversations, however I don't feel comfortable reading the
emacs manual in Chinese. For my language learning I also tend to keep
some notes in Chinese which I would like to edit with emacs.

Shouldn't there be a way to allow people to input Chinese (or other
non-European languages) without affecting the language environment? The
current behavior seems to discriminate language learners

What do you think?

Thanks!

Best regards
Leonard





  parent reply	other threads:[~2017-08-05  1:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871soq7pyr.fsf@users.sourceforge.net>
2017-06-27 14:48 ` bug#27505: LC_CTYPE affects tutorial language Leonard Lausen
2017-06-27 15:05   ` Eli Zaretskii
2017-06-27 15:13   ` Andreas Schwab
     [not found]   ` <handler.27505.C.150189707129878.notifdonectrl.0@debbugs.gnu.org>
2017-08-05  1:54     ` Leonard Lausen [this message]
2017-08-05  2:06       ` bug#27505: acknowledged by developer (Re: bug#27505: LC_CTYPE affects tutorial language) npostavs
2017-08-05  5:59         ` Leonard Lausen
2017-08-05  7:10         ` Eli Zaretskii
2017-08-05  7:06       ` Eli Zaretskii
2017-08-05  8:17         ` Leonard Lausen
2017-08-05  9:17           ` Eli Zaretskii
2017-08-05  9:52             ` Leonard Lausen
2017-08-05 10:15               ` Eli Zaretskii
2017-08-05 10:50                 ` Leonard Lausen
2017-08-05 11:09                   ` Andreas Schwab
2017-08-05 11:20                     ` Leonard Lausen
2017-08-05 11:22                       ` Leonard Lausen
2022-04-17 19:44                 ` bug#27505: LC_CTYPE affects tutorial language Lars Ingebrigtsen
2017-08-05  8:18         ` bug#27505: acknowledged by developer (Re: bug#27505: LC_CTYPE affects tutorial language) Leonard Lausen

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=d6543bc3-a8f2-f825-7a5b-4d1f4f0a66fb@lausen.nl \
    --to=leonard@lausen.nl \
    --cc=27505@debbugs.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 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).