Subject: Re: bug#20258: 24.5; format-time-string miscounting of multibyte characters

From: Eli Zaretskii <[email-masked]>
Date: Mon, 30 Sep 2019 17:44:24 +0300

> From: Gunnar Horrigmo <[email-masked]>
> Cc: Eli Zaretskii <[email-masked]>,  <[email-masked]>,
>   <[email-masked]>,  <[email-masked]>,
>   <[email-masked]>
> Date: Mon, 30 Sep 2019 16:30:55 +0200
> 
> Lars Ingebrigtsen <[email-masked]> writes:
> 
> > I was pondering whether any users had a locale of *.UTF-16.
> 
> Windows users might

I don't think so.  AFAIK, UTF-16 is not a valid codeset of any Windows
locale.  Windows uses UTF-16 internally, and exposes it in the Windows
APIs, but APIs that came from Posix (and locale is one of them) only
support single-byte and DBCS encodings as their codeset.