On Thu, 3 Dec 2009, Eric Blake wrote:
Thomas Dickey his.com> writes:
This means that characters 0..127 have to be treated as ASCII, but
No, it means that portable characters and control characters must be < 128.
ASCII meets this characteristic, but so does EBCDIC, as well as UTF-8. The C
l
Thomas Dickey his.com> writes:
> > This means that characters 0..127 have to be treated as ASCII, but
No, it means that portable characters and control characters must be < 128.
ASCII meets this characteristic, but so does EBCDIC, as well as UTF-8. The C
locale also implies that you can mani
On Dec 3 13:16, Andy Koppe wrote:
> 2009/12/3 Thomas Dickey:
> >> From
> >> http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html,
> >> §7.2:
> >>
> >> "The tables in Locale Definition describe the characteristics and
> >> behavior of the POSIX locale for data consisting entirely
2009/12/3 Thomas Dickey:
>> From
>> http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html,
>> §7.2:
>>
>> "The tables in Locale Definition describe the characteristics and
>> behavior of the POSIX locale for data consisting entirely of
>> characters from the portable character set
On Thu, 3 Dec 2009, Andy Koppe wrote:
2009/12/3 Linda Walsh:
C.UTF_8 doesn't exist.
...
You can't have "C" and "UTF-8", because C means no encoding (default).
UTF-8 IS an encoding, so they are mutually exclusive.
From http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html,
§
On Dec 3 07:48, Andy Koppe wrote:
> 2009/12/3 Linda Walsh:
> > C.UTF_8 doesn't exist.
>
> Well, guess what: it does in Cygwin 1.7, and it's the default locale.
Not exactly. The default locale is C.UTF-8. You can also use C.UTF8
or C.utf-8 or C.utf8, but not C.UTF_8 or C.utf_8.
Corinna
--
C
2009/12/3 Linda Walsh:
> C.UTF_8 doesn't exist.
Well, guess what: it does in Cygwin 1.7, and it's the default locale.
And it's also in the next Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522776.
Cygwin 1.7 also supports "C.ISO-8859-1", "C.CP1252", ...
> Might want to try 'Console'
Linda Walsh wrote:
> C.UTF_8 doesn't exist.
You're wrong. Please read the whole of this thread -- and the last two
months' worth of cygwin-developers.
> mintty is broken.
No, it isn't. It just doesn't work the way *you* expect it to.
> Might want to try 'Console' nstead of using mintty. Not p
Ken Brown wrote:
On 10/28/2009 6:07 PM, Andy Koppe wrote:
2009/10/28 Ken Brown:
Maybe my terminology is wrong. But if you start mintty with no
.minttyrc
and with LANG unset, mintty will set LANG=C.UTF-8.
Yep. That's primarily for emacs' benefit, which parses the locale env
variables itself
On 11/28/2009 8:34 AM, Andy Koppe wrote:
2009/11/28 Ken Brown:
On 10/28/2009 6:07 PM, Andy Koppe wrote:
2009/10/28 Ken Brown:
Maybe my terminology is wrong. But if you start mintty with no .minttyrc
and with LANG unset, mintty will set LANG=C.UTF-8.
Yep. That's primarily for emacs' benefit,
2009/11/28 Ken Brown:
> On 10/28/2009 6:07 PM, Andy Koppe wrote:
>>
>> 2009/10/28 Ken Brown:
>>>
>>> Maybe my terminology is wrong. But if you start mintty with no .minttyrc
>>> and with LANG unset, mintty will set LANG=C.UTF-8.
>>
>> Yep. That's primarily for emacs' benefit, which parses the loca
On 10/28/2009 6:07 PM, Andy Koppe wrote:
2009/10/28 Ken Brown:
Maybe my terminology is wrong. But if you start mintty with no .minttyrc
and with LANG unset, mintty will set LANG=C.UTF-8.
Yep. That's primarily for emacs' benefit, which parses the locale env
variables itself instead of using se
2009/11/3 Jon TURNEY:
> On second look, this patch doesn't seem to be quite right, as it makes the
> en_US.UTF-8 compose sequences available in C.UTF-8 (which is not the case in
> the C locale).
I think that's ok. The compose sequences don't make sense in an ASCII
locale, since ASCII doesn't conta
On 29/10/2009 20:20, Andy Koppe wrote:
2009/10/29 Jon TURNEY:
I've put a patch in bugzilla [1] which can be applied to
/usr/share/X11/locale to temporarily repair this problem.
This needs to be looked at more deeply, though, as I'm not sure I've fully
understood what that locale data is being u
2009/10/29 Jon TURNEY:
> I've put a patch in bugzilla [1] which can be applied to
> /usr/share/X11/locale to temporarily repair this problem.
>
> This needs to be looked at more deeply, though, as I'm not sure I've fully
> understood what that locale data is being used for, or specified C.UTF-8
> c
On 29/10/2009 15:01, Jon TURNEY wrote:
On 29/10/2009 14:37, Ken Brown wrote:
$ LANG=C.UTF-8 ./Xlocale.exe
Setting locale from LANG succeeded
Locale is C.UTF-8
XSupportsLocale returned false
Okay, well this makes sense now :-(
Appropriate data needs to exist in /usr/share/X11/locale for the C.
On 29/10/2009 14:37, Ken Brown wrote:
On 10/29/2009 9:42 AM, Jon TURNEY wrote:
On 29/10/2009 00:07, Andy Koppe wrote:
2009/10/28 Jon TURNEY:
On 28/10/2009 14:22, Ken Brown wrote:
X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the
server with 'LANG=C.UTF-8 /usr/bin/startxwin.ba
On 29/10/2009 13:56, Corinna Vinschen wrote:
On Oct 29 13:42, Jon TURNEY wrote:
I haven't been following the discussion about C.UTF-8 closely, but
curiously, for me at least, this test program shows that
setlocale(LC_ALL, "") fails with LANG=C.UTF-8 (so that doesn't
actually seem to be a valid l
On 10/29/2009 9:42 AM, Jon TURNEY wrote:
On 29/10/2009 00:07, Andy Koppe wrote:
2009/10/28 Jon TURNEY:
On 28/10/2009 14:22, Ken Brown wrote:
X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the
server with 'LANG=C.UTF-8 /usr/bin/startxwin.bat', the server exits
immediately, and
On Oct 29 13:42, Jon TURNEY wrote:
> I haven't been following the discussion about C.UTF-8 closely, but
> curiously, for me at least, this test program shows that
> setlocale(LC_ALL, "") fails with LANG=C.UTF-8 (so that doesn't
> actually seem to be a valid locale, although if it's the default it
>
On 29/10/2009 00:07, Andy Koppe wrote:
2009/10/28 Jon TURNEY:
On 28/10/2009 14:22, Ken Brown wrote:
X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the
server with 'LANG=C.UTF-8 /usr/bin/startxwin.bat', the server exits
immediately, and the log has complaints about the locale. I
2009/10/28 Jon TURNEY:
> On 28/10/2009 14:22, Ken Brown wrote:
>>
>> X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the
>> server with 'LANG=C.UTF-8 /usr/bin/startxwin.bat', the server exits
>> immediately, and the log has complaints about the locale. If I instead
>> use 'LANG=en_US
On 28/10/2009 14:22, Ken Brown wrote:
X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the
server with 'LANG=C.UTF-8 /usr/bin/startxwin.bat', the server exits
immediately, and the log has complaints about the locale. If I instead
use 'LANG=en_US.UTF-8', there's no problem. I've atta
> Xwin 1.6.x had no problem with "C.UTF-8".
Actually it's libX11 that makes the difference: Xwin 1.7.1 is fine
after downgrading libX11 from 1.3.2-1 to 1.2.2-2.
Andy
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Document
Thomas Dickey wrote:
> On Wed, 28 Oct 2009, Ken Brown wrote:
>
>> X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server
>
> technically speaking, there's "no such locale" as C.UTF-8,
> so I'd not expect portable code to accept it ("C" and "UTF-8" are
> mutually exclusive).
No
2009/10/28 Ken Brown:
> Maybe my terminology is wrong. But if you start mintty with no .minttyrc
> and with LANG unset, mintty will set LANG=C.UTF-8.
Yep. That's primarily for emacs' benefit, which parses the locale env
variables itself instead of using setlocale(LC_CTYPE, ""), thereby
missing ou
2009/10/28 Thomas Dickey:
>> X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server
>
> technically speaking, there's "no such locale" as C.UTF-8,
> so I'd not expect portable code to accept it ("C" and "UTF-8" are
> mutually exclusive).
Technically speaking, portable code shoul
On 10/28/2009 5:23 PM, Thomas Dickey wrote:
On Wed, 28 Oct 2009, Ken Brown wrote:
X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server
technically speaking, there's "no such locale" as C.UTF-8,
so I'd not expect portable code to accept it ("C" and "UTF-8" are
mutually e
On Wed, 28 Oct 2009, Ken Brown wrote:
X11R7.5 doesn't like the (default) locale C.UTF-8. If I start the server
technically speaking, there's "no such locale" as C.UTF-8,
so I'd not expect portable code to accept it ("C" and "UTF-8" are
mutually exclusive).
with 'LANG=C.UTF-8 /usr/bin/startxw
29 matches
Mail list logo
