unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leonard Lausen <leonard@lausen.nl>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 27505@debbugs.gnu.org
Subject: bug#27505: acknowledged by developer (Re: bug#27505: LC_CTYPE affects tutorial language)
Date: Sat, 5 Aug 2017 20:22:11 +0900	[thread overview]
Message-ID: <aa8ffbc9-c7b9-71e4-98a3-a682ac87c7a3@lausen.nl> (raw)
In-Reply-To: <61e641ab-83bf-5c93-8dda-15db547c6c4c@lausen.nl>

On 08/05/2017 08:20 PM, Leonard Lausen wrote:
>>> So I agree with the previous comment that LANG should take precedence
>>> over LC_CTYPE with regards to the interface language. Not sure if the
>>> current emacs implementation allows that change without affecting the
>>> settings where LC_CTYPE does change precedence over LANG.
>>
>> LANG never takes precedence over other LC_* values, it only serves as
>> the default for them.  An interface that uses LC_CTYPE must ignore LANG
>> when LC_CTYPE is set.
> 
> I agree that LC_CTYPE always takes precedence for the things that
> LC_CTYPE defines according to the POSIX standard. However, as far as I
> understand the display language is not defined by LC_CTYPE. LC_CTYPE
> defines "Character classification and case conversion".
> 
> The closest would be LC_MESSAGES ("Formats of informative and diagnostic
> messages and interactive responses."). I just tried, and for example vim
> uses indeed LC_MESSAGES to decide on the interface language. So does
> Chromium and KDE applications such as okular..

So what I mean to say is that LANG should take precedence over LC_CTYPE
with respect to the interface language. At least as long as LC_MESSAGES
is not defined. Of course you can argue if the interface language is the
same as "Formats of informative and diagnostic messages and interactive
responses.". But if you disagree with that, then LANG should always take
precedence.





  reply	other threads:[~2017-08-05 11:22 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
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 [this message]
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=aa8ffbc9-c7b9-71e4-98a3-a682ac87c7a3@lausen.nl \
    --to=leonard@lausen.nl \
    --cc=27505@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).