[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8734uonhfv.fsf@nvidia.com>
Date: Tue, 23 Jan 2024 17:05:12 +0100
From: Petr Machata <petrm@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Petr Machata <petrm@...dia.com>, Matthias May <matthias.may@...termo.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"netdev-driver-reviewers@...r.kernel.org"
<netdev-driver-reviewers@...r.kernel.org>
Subject: Re: [ANN] net-next is OPEN
Jakub Kicinski <kuba@...nel.org> writes:
> On Tue, 23 Jan 2024 14:38:24 +0100 Petr Machata wrote:
>> Matthias May <matthias.may@...termo.com> writes:
>>
>> > Also there seems to be something wrong with ending, see
>> > https://netdev-2.bots.linux.dev/vmksft-net/results/433200/81-l2-tos-ttl-inherit-sh
>> > The test outputs the results in a table with box drawing characters (┌─┬┐├─┼┤└─┴┘)
>>
>> It looks like whatever is serving the output should use MIME of
>> "text/plain;charset=UTF-8" instead of just "text/plain".
>
> 😮️ interesting. The table characters are not part of ASCII, right?
Yeah, the table is UTF-8.
> So it must be using some extended charset. Firefox hid the option
> to tweak encoding tho so IDK what it actually uses :S
My guess would be ISO-8859-1, but dunno. The developer console shows
Firefox has had to guess the encoding, but not what guess it made.
It seems weird to guess anything but UTF-8 in this day and age. Maybe
the logic is that modern web has correct content-type, because it needs
UTF-8, so if it doesn't declare encoding, it's something ancient.
Powered by blists - more mailing lists