Displaying 3 results from an estimated 3 matches for "utf8_locale".
2018 Aug 17
4
Call for testing: OpenSSH 7.8
On 13 August 2018 at 15:06, Val Baranov <val.baranov at duke.edu> wrote:
[...]
> test_utf8: ........................
> regress/unittests/utf8/tests.c:48 test #25 "c_esc"
> ASSERT_INT_EQ(len, wantlen) failed:
> len = -1
> wantlen = 5
This boils down to meaning OpenSSH's smnprintf call failed for the
string "\033x" instead of returning the
2018 Aug 20
2
Call for testing: OpenSSH 7.8
.../or ISO8859-15, the "UK" or EN_US variant)?
> If you worry that some target system might not have a en_US.UTF-8
> locale installed, you can look at
>
> http://mandoc.bsd.lv/cgi-bin/cvsweb/configure?rev=HEAD
>
> for a way to autodetect a suitable UTF-8 locale - look for UTF8_LOCALE
> in that script.
>
> But that may be overkill for OpenSSH. Just recklessly forcing
> LC_CTYPE=en_US.UTF-8 may be good enough for OpenSSH's purposes.
> If the target system doesn't provide it, setlocale(3) will fall
> back to POSIX, which should be good enough for the tes...
2018 Aug 18
2
Call for testing: OpenSSH 7.8
...course, it would do no harm on OpenBSD either.
>
> If you worry that some target system might not have a en_US.UTF-8
> locale installed, you can look at
>
> http://mandoc.bsd.lv/cgi-bin/cvsweb/configure?rev=HEAD
>
> for a way to autodetect a suitable UTF-8 locale - look for UTF8_LOCALE
> in that script.
>
> But that may be overkill for OpenSSH. Just recklessly forcing
> LC_CTYPE=en_US.UTF-8 may be good enough for OpenSSH's purposes.
> If the target system doesn't provide it, setlocale(3) will fall
> back to POSIX, which should be good enough for the te...