Re: [PATCH 1/1] remote-curl: unbreak http.extraHeader with custom allocators

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 8, 2019, 08:34 UTC
Message-ID: <xmqqimnun4v5.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.1911062029230.46@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> ... which was broken in non-US locales (most notably in a Japanese setup;
> apparently there _still_ are developers who did not yet move away from a
> Japanese locale... at least on Windows).

I think the above was a reference to a tangential comment I made in a response to Peff.

Oh, I do not expect Japanese Windows users would "move away from" Japanese locale, ever.

I do however know that an app that supports only legacy encoding is frowned upon these days. They still use and will keep using Japanese menus and messages, and they still write their documents in Japanese and not in US English.

But they store their Japenese documents encoded in UTF-8 on their system that is in Japanese locale.

There are two models of gadgets I am interested in getting, between which one of them that is slightly older supports UTF-8 and MS-Kanji (aka Shift-JIS) while the latest model only supports MS-Kanji. The list price of them are comparable (actually, the latest one lists a bit more), but the latest model is deeply discounted while the other one with UTF-8 is not as much. At shopping sites, user reviews often mention "I've migrated my text to UTF-8 already and going back to Shift JIS in this year is too cumbersome, so I'll skip this latest model".

I am hoping a software update might happen, and will pull the trigger once the latest one starts supporting UTF-8 ;-)