git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] gitweb: apply fallback encoding before highlight

From
Junio C Hamano <gitster@pobox.com>
Date
May 4, 2016, 19:34 UTC
Message-ID
<xmqqeg9hhb1e.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160504083449.GA46041@skmba.local>
Shin Kojima <shin@kojima.org> writes:
> I can say this patch, to consider $fallback_encoding while
> highlighting, is fairly rational.  But I also feel this is too much
> just for specific outdated character encodings, it is completely
> useless for the most part of gitweb users in the world.

Oh, don't get me wrong. I do think what the patch does is very sensible and have no intention of rejecting it.

Unless somebody finds a new bug in it, but in that case, we won't be rejecting it but would be improving on it.

As I said, the question was "Just out of curiosity", since it's been so long since I was in any part of software work done in Japan.

Previous: Shin KojimaNext: Shin Kojima
Message 7 of 8 in “gitweb: apply fallback encoding before highlight”
  1. gitweb: apply fallback encoding before highlightShin Kojima, Apr 20, 2016
  2. Junio C HamanoMay 2, 2016
  3. Jakub NarębskiMay 2, 2016
  4. gitweb: apply fallback encoding before highlightShin Kojima, May 3, 2016
  5. Junio C HamanoMay 3, 2016
  6. Shin KojimaMay 4, 2016
  7. Junio C HamanoMay 4, 2016
  8. Shin KojimaMay 5, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.