[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: string-ports issue on Windows
From: |
Eli Zaretskii |
Subject: |
Re: string-ports issue on Windows |
Date: |
Thu, 18 Apr 2019 21:51:41 +0300 |
> From: Christopher Lam <address@hidden>
> Date: Thu, 18 Apr 2019 16:22:24 +0000
> Cc: guile-user <address@hidden>
>
> scheme@(guile-user)> (setlocale LC_ALL "")
> $15 = "English_Australia.1252"
> scheme@(guile-user)> (locale-encoding)
> $16 = "CP1252"
> scheme@(guile-user)> (setlocale LC_ALL "C")
> $17 = "C"
> scheme@(guile-user)> (locale-encoding)
> $18 = "CP1252"
The above is expected, if codepage 1252 is your system codepage.
Here's what I get, FWIW:
scheme@(guile-user)> (use-modules (ice-9 i18n))
scheme@(guile-user)> (locale-encoding)
$1 = "CP1252"
scheme@(guile-user)> (setlocale LC_ALL "French_France.1250")
$2 = "French_France.1250"
scheme@(guile-user)> (locale-encoding)
$3 = "CP1250"
scheme@(guile-user)> (setlocale LC_ALL "")
$4 = "English_United States.1252"
scheme@(guile-user)> (locale-encoding)
$5 = "CP1252"
scheme@(guile-user)> (setlocale LC_ALL "C")
$6 = "C"
scheme@(guile-user)> (locale-encoding)
$7 = "CP1255"
My system locale is 1255, as you might have guessed.
HTH
- string-ports issue on Windows, Christopher Lam, 2019/04/16
- Re: string-ports issue on Windows, Eli Zaretskii, 2019/04/16
- Re: string-ports issue on Windows, Mark H Weaver, 2019/04/16
- Re: string-ports issue on Windows, Christopher Lam, 2019/04/16
- Re: string-ports issue on Windows, Mark H Weaver, 2019/04/17
- Re: string-ports issue on Windows, Christopher Lam, 2019/04/18
- Re: string-ports issue on Windows,
Eli Zaretskii <=
- Re: string-ports issue on Windows, Mark H Weaver, 2019/04/18
- Re: string-ports issue on Windows, Mark H Weaver, 2019/04/18
- Re: string-ports issue on Windows, Christopher Lam, 2019/04/19