unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Nextstep build uses iso-latin by default. WHY?
Date: Sat, 12 Mar 2016 17:55:11 +0100	[thread overview]
Message-ID: <56E449EF.1030509@alice.it> (raw)
In-Reply-To: <83twkcgp9w.fsf@gnu.org>

Il 12/03/2016 07:54, Eli Zaretskii ha scritto:
>> Cc: emacs-devel@gnu.org
>> From: Angelo Graziosi <angelo.graziosi@alice.it>
>> Date: Fri, 11 Mar 2016 23:18:48 +0100
>>
>>   From Terminal:
>>
>> $ locale
>> LANG="it_IT.UTF-8"
>> LC_COLLATE="it_IT.UTF-8"
>> LC_CTYPE="it_IT.UTF-8"
>> LC_MESSAGES="it_IT.UTF-8"
>> LC_MONETARY="it_IT.UTF-8"
>> LC_NUMERIC="it_IT.UTF-8"
>> LC_TIME="it_IT.UTF-8"
>> LC_ALL=
>>
>> but (getenv "LANG") shows 'it_IT'...
>
> But the problem is not in the Emacs session started from the
> terminal, is it?  AFAIR, the change was only for session that didn't
> begin from the shell.
>

When Emacs starts from the Dock (i.e. not from the shell) it "sees" 
LANG=it_IT and not LANG=it_IT.UTF-8 as when it starts from the shell..

Stefan Monnier wrote:
> The OSX environment has always had a very strong bias towards utf-8, so
> in the absence of a strong indication that something else than utf-8 is
> desired, we should always use utf-8 on that platform.


   Angelo




  reply	other threads:[~2016-03-12 16:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 20:27 Nextstep build uses iso-latin by default. WHY? Angelo Graziosi
2016-03-11 20:49 ` Eli Zaretskii
2016-03-11 22:18   ` Angelo Graziosi
2016-03-12  6:54     ` Eli Zaretskii
2016-03-12 16:55       ` Angelo Graziosi [this message]
2016-03-11 22:41   ` Stefan Monnier
2016-03-20 15:11     ` Alan Third
2016-03-20 15:34       ` Stefan Monnier
2016-04-02 15:45       ` Alan Third
2016-04-08 13:57         ` Anders Lindgren
2016-04-08 14:41           ` Toon Claes
2016-04-08 19:59             ` Anders Lindgren
2016-04-08 23:03               ` John Wiegley
2016-04-14  6:30               ` Toon Claes
2016-04-14  9:31                 ` Anders Lindgren
2016-04-14 12:52                   ` Regexp search in debbugs (was: Nextstep build uses iso-latin by default. WHY?) Michael Albinus
2016-04-14 13:35                     ` Regexp search in debbugs Lars Magne Ingebrigtsen
2016-04-15  0:48                   ` Nextstep build uses iso-latin by default. WHY? YAMAMOTO Mitsuharu
2016-04-16  8:31                   ` YAMAMOTO Mitsuharu
2016-04-16 13:47                     ` Stefan Monnier
2016-04-16 22:32                       ` John Wiegley
2016-04-14 12:35                 ` Stefan Monnier
2016-04-14 16:39                   ` John Wiegley
2016-04-14 22:40                   ` YAMAMOTO Mitsuharu
2016-04-14 23:26                     ` Stefan Monnier
2016-04-15  5:42                       ` Anders Lindgren
2016-04-15  9:21                       ` YAMAMOTO Mitsuharu
2016-03-11 23:43   ` Angelo Graziosi

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=56E449EF.1030509@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).