From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: leonard@lausen.nl, 27505@debbugs.gnu.org
Subject: bug#27505: acknowledged by developer (Re: bug#27505: LC_CTYPE affects tutorial language)
Date: Sat, 05 Aug 2017 10:10:46 +0300 [thread overview]
Message-ID: <83ini2wkuh.fsf@gnu.org> (raw)
In-Reply-To: <87shh66a55.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Date: Fri, 04 Aug 2017 22:06:30 -0400
> Cc: 27505@debbugs.gnu.org
>
> Or should LANG should take precedence over LC_CTYPE perhaps?
That'd go against the Posix semantics of these variables, so we
shouldn't do that, because it might not be what is expected by users
who set both LANG and other LC_* variables.
As I wrote previously, I don't really understand the exact problem we
are asked to solve here. I don't think we should be discussing
solutions before we understand the actual problem. Right now, I
believe that Emacs already provides features to resolve any such
problems.
next prev parent reply other threads:[~2017-08-05 7:10 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 ` 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 [this message]
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=83ini2wkuh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27505@debbugs.gnu.org \
--cc=leonard@lausen.nl \
--cc=npostavs@users.sourceforge.net \
/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).