[sf-lug] .signature files collection

Akkana Peck akkana at shallowsky.com
Thu Jan 22 17:35:41 PST 2015


Rick Moen writes:
> If you have a look at http://linuxmafia.com/pub/humour/sigs-rickmoen-old , 
> i.e., view it in your Web browser, you'll see that somehow the encoding
> gets screwed up in the process of serving the file.
> 
> Like this:
> 
> Cheers,                              Tá m'árthach foluaineach lán d'eascanna.
> 
> ...instead of the correct UTF-8 encoded version:
> 
> Cheers,                              Tá m'árthach foluaineach lán d'eascanna.
> 
> I'll leave http://linuxmafia.com/pub/humour/sigs-rickmoen-old up for a
> few days so you can see what I'm talking about, but then I'll be
> removing the file.

I do see what you describe (Tá instead of Tá) but "View Page Info"
in Firefox says it's displaying the page as UTF-8.

View->Character Encoding says Unicode (I didn't think "Unicode" even
qualified as a character encoding) and won't let me change it to
anything else, for some reason. Seems like that menu used to let you
try different encodings in case the one specified by the server was
wrong, but in Firefox 35 it just seems to be a bunch of no-ops.

If I wget the file and view it in vim on my UTF-8 Debian system, I
still see TÃ. The sequence of bytes in the file for the a character
is c3 83 c2 a1; the sequence of bytes for the correct version from
your email (if I reply in mutt+vim and :w it) is c3 a1.

If I look those up on http://www.utf8-chartable.de/ , c3 83 is
"LATIN CAPITAL LETTER A WITH TILDE", c2 a1 is "INVERTED EXCLAMATION
MARK" and c3 a1 is "LATIN SMALL LETTER A WITH ACUTE". That's
consistent with what I'm seeing: when I view sigs-rickmoen-old in a
browser (or in vim or cat), I see A with a tilde, followed by an
inverted exclam (actually I thought it was a lowercase i, but that's
just my font), but in the correct example in your mail I see an a
with an acute accent.

So it seems like Firefox, vim and cat are all showing me what they
should show me for the bytes in sigs-rickmoen-old. Are the bytes
different on your end, and the server is changing your c3 a1 and
serving it to me as c3 83 c2 while still saying it's UTF-8?

        ...Akkana




More information about the sf-lug mailing list