Re: AcceptEnv LANG LC_* vs available locales

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]


On Sun, 1 May 2022, Jochen Bern wrote:

> If that's your opinion, go ahead and implement it. Which my suggestion of a
> server-side helper evaluating the client-side-set and server-side-available
> locales

This could be… challenging. (There’s locale(1) -a, sure, but…)

It also assumes locale support on both ends in the first place.

> situation; I expect terminals to gravitate more and more towards implementing
> it, increasing the pressure on the consortium to include two codepoints to
> "shift to control" and "shift back" into its standards, laying the groundwork
> of a *global* algorithm for terminals to tell control data from content.

I highly doubt anything will change now, especially things that break

Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn •
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also,
╱ ╲ header encryption!
openssh-unix-dev mailing list

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux