Bug#1026231: debian-policy: document droppage of support for legacy locales

On Sat, Jan 21, 2023 at 12:58:19PM -0800, Russ Allbery wrote: > Wouter Verhelst writes: > > On Fri, Jan 20, 2023 at 05:16:43PM +, Simon McVittie wrote: > > >> Sure, but neither of those actually require us to support GBK or GB > >> 18030 as a system locale, only as something that iconv() (or

Bug#1026231: debian-policy: document droppage of support for legacy locales

Wouter Verhelst writes: > On Fri, Jan 20, 2023 at 05:16:43PM +, Simon McVittie wrote: >> Sure, but neither of those actually require us to support GBK or GB >> 18030 as a system locale, only as something that iconv() (or whatever >> browsers actually use, which is probably their own thing)

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, Jan 20, 2023 at 05:16:43PM +, Simon McVittie wrote: > On Fri, 20 Jan 2023 at 09:54:21 -0700, Anthony Fok wrote: > > supposedly some older Chinese websites are still using "GBK" as > > encoding, probably something like: > > > > > > > > which has less than 30,000 characters and

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, Jan 20, 2023 at 10:15 AM Adam Borowski wrote: > > On Fri, Jan 20, 2023 at 03:57:17PM +0200, Wouter Verhelst wrote: > > On Thu, Jan 19, 2023 at 11:47:42AM +, Simon McVittie wrote: > > If the PRC government *requires* a non-UTF-8 encoding for things sold to > > them, we would be doing

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, 20 Jan 2023 at 09:54:21 -0700, Anthony Fok wrote: > supposedly some older Chinese websites are still using "GBK" as > encoding, probably something like: > > > > which has less than 30,000 characters and thus a very limited subset > of Unicode. And, presumably not everyone has the

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, Jan 20, 2023 at 03:57:17PM +0200, Wouter Verhelst wrote: > On Thu, Jan 19, 2023 at 11:47:42AM +, Simon McVittie wrote: > > Preferring to use Unicode does seem to be the direction that all of > > computing is going in, as a simplifying assumption - for example W3C > > advice for HTML is

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, Jan 20, 2023 at 7:27 AM Wouter Verhelst wrote: > > On Thu, Jan 19, 2023 at 11:47:42AM +, Simon McVittie wrote: > > Preferring to use Unicode does seem to be the direction that all of > > computing is going in, as a simplifying assumption - for example W3C > > advice for HTML is "You

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, Jan 20, 2023 at 7:42 AM Bill Allombert wrote: > > On Thu, Jan 19, 2023 at 11:47:42AM +, Simon McVittie wrote: > > On Wed, 18 Jan 2023 at 16:30:46 -0700, Anthony Fok wrote: > > > In their mind, GB 18030 encompasses a lot more than just > > > a character encoding mapping table. It is

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Thu, Jan 19, 2023 at 4:47 AM Simon McVittie wrote: > > On Wed, 18 Jan 2023 at 16:30:46 -0700, Anthony Fok wrote: > > In their mind, GB 18030 encompasses a lot more than just > > a character encoding mapping table. It is the full support package > > (including fonts, display, printing, input

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Wed, Jan 18, 2023 at 6:30 PM Russ Allbery wrote: > > Anthony Fok writes: > > > I'm not asking you to spend any time working on GB18030; that would be > > the job of Debian Chinese i18n/L10n team as well as the wider community > > (glibc, libiconv, Qt, etc.) All I am asking you is to maintain

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Thu, Jan 19, 2023 at 11:47:42AM +, Simon McVittie wrote: > On Wed, 18 Jan 2023 at 16:30:46 -0700, Anthony Fok wrote: > > In their mind, GB 18030 encompasses a lot more than just > > a character encoding mapping table. It is the full support package > > (including fonts, display, printing,

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Thu, Jan 19, 2023 at 11:47:42AM +, Simon McVittie wrote: > Preferring to use Unicode does seem to be the direction that all of > computing is going in, as a simplifying assumption - for example W3C > advice for HTML is "You should always use the UTF-8 character encoding"[1] > - and as we

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Wed, 18 Jan 2023 at 16:30:46 -0700, Anthony Fok wrote: > In their mind, GB 18030 encompasses a lot more than just > a character encoding mapping table. It is the full support package > (including fonts, display, printing, input methods, etc.) for Han > Chinese and all other minority languages

Bug#1026231: debian-policy: document droppage of support for legacy locales

Anthony Fok writes: > I'm not asking you to spend any time working on GB18030; that would be > the job of Debian Chinese i18n/L10n team as well as the wider community > (glibc, libiconv, Qt, etc.) All I am asking you is to maintain the > status quo, and don't discount anything other than UTF-8

Bug#1026231: debian-policy: document droppage of support for legacy locales

Hello, On Mon, Dec 19, 2022 at 2:48 PM Bill Allombert wrote: > Which raise the question: does the corresponding user group moved to UTF-8 ? > Judging from , > neither Chinese nor Japanese users have overwhelmingly moved to UTF-8, > so it

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Wed, 21 Dec 2022 at 18:15:11 +0100, Adam Borowski wrote: > On Mon, Dec 19, 2022 at 07:08:09PM +, Simon McVittie wrote: > > On Fri, 16 Dec 2022 at 19:21:37 +0100, Adam Borowski wrote: > > > * The execution environment (usually init system or a container) must > > > default to UTF-8

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Wed, Dec 21, 2022 at 03:23:09PM +0100, Adam Borowski wrote: > On Mon, Dec 19, 2022 at 10:44:12PM +0100, Bill Allombert wrote: > > Which raise the question: does the corresponding user group moved to UTF-8 ? > > Judging from , > > neither

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Mon, Dec 19, 2022 at 07:08:09PM +, Simon McVittie wrote: > On Fri, 16 Dec 2022 at 19:21:37 +0100, Adam Borowski wrote: > > As of Bookworm, legacy locales are no longer officially supported. > > For clarity, I think when you say "legacy locales" you mean locales > whose character encoding

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Mon, Dec 19, 2022 at 10:44:12PM +0100, Bill Allombert wrote: > Which raise the question: does the corresponding user group moved to UTF-8 ? > Judging from , > neither Chinese nor Japanese users have overwhelmingly moved to UTF-8, > so it

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Mon, Dec 19, 2022 at 07:08:09PM +, Simon McVittie wrote: > On Fri, 16 Dec 2022 at 19:21:37 +0100, Adam Borowski wrote: > > As of Bookworm, legacy locales are no longer officially supported. > > For clarity, I think when you say "legacy locales" you mean locales > whose character encoding

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, 16 Dec 2022 at 19:21:37 +0100, Adam Borowski wrote: > As of Bookworm, legacy locales are no longer officially supported. For clarity, I think when you say "legacy locales" you mean locales whose character encoding is either explicitly or implicitly something other than UTF-8 ("legacy

Bug#1026231: debian-policy: document droppage of support for legacy locales

On Fri, Dec 16, 2022 at 07:21:37PM +0100, Adam Borowski wrote: > Package: debian-policy > Version: 4.6.1.1 > Severity: wishlist > > Hi! > As of Bookworm, legacy locales are no longer officially supported. In order > to not break testsuites, they're mostly working if you install locales-all, >

Bug#1026231: debian-policy: document droppage of support for legacy locales

Package: debian-policy Version: 4.6.1.1 Severity: wishlist Hi! As of Bookworm, legacy locales are no longer officially supported. In order to not break testsuites, they're mostly working if you install locales-all, and you may manually request their generation by editing /etc/locale.gen -- but