From: Andreas Schwab <schwab@suse.de>
To: Leonard Lausen <leonard@lausen.nl>
Cc: 27505@debbugs.gnu.org
Subject: bug#27505: LC_CTYPE affects tutorial language
Date: Tue, 27 Jun 2017 17:13:13 +0200 [thread overview]
Message-ID: <mvmo9t9mpkm.fsf@suse.de> (raw)
In-Reply-To: <44eb186d-db67-3e93-31cd-8260f5df7781@lausen.nl> (Leonard Lausen's message of "Tue, 27 Jun 2017 23:48:41 +0900")
On Jun 27 2017, Leonard Lausen <leonard@lausen.nl> wrote:
> as far as I know the environment variable LC_CTYPE applies to
> classification and conversion of characters, and to multibyte and wide
> characters. So setting it should not influence the interface language,
> correct?
current-language-environment is set from LC_CTYPE, which also controls
the tutorial language.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2017-06-27 15:13 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 [this message]
[not found] ` <handler.27505.C.150189707129878.notifdonectrl.0@debbugs.gnu.org>
2017-08-05 1:54 ` bug#27505: acknowledged by developer (Re: bug#27505: LC_CTYPE affects tutorial language) Leonard Lausen
2017-08-05 2:06 ` 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=mvmo9t9mpkm.fsf@suse.de \
--to=schwab@suse.de \
--cc=27505@debbugs.gnu.org \
--cc=leonard@lausen.nl \
/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).