From Newsgroup: comp.sys.acorn.apps
On 5 Sept, Dave wrote in message
<
5d139fc5d0dave@triffid.co.uk>:
I just use Pluto as is, how would I change its Font?
You don't: as I wrote, it's an encoding issue. The UK Pound Sign is a
top-bit character in some specific encodings. But Usenet doesn't support top-bit characters directly, so any posting including a Pound sign needs to
a) be in MIME encoding so that top-bit characters can be included, and b) specify the character set used as one which includes a Pound sign.
But, csa.announce (where this originated) does not support any top-bit characters in postings (indeed, point 3 of the "don'ts" in section 5 of
https://www.owlart.net/csaa/charter.html explicitly states "no top bit characters may be used (eg. pound sign), and no MIME encoding should be
used". So the posting from Elesar failed to follow the requirements for the group.
What you see as a result is the raw MIME encoding of a Pound sign in ISO
8859-1 (AKA Acorn Latin 1): the character code is 163, or &A3 in hex, and
MIME would encode that as =A3... so you can see where this is going... All
of the information to tell the reader that "=A3" is a MIME sequence has long gone, possibly stripped out by the moderation system.
And yes, I've posted MIME-encoded stuff to csaa and been caught like this,
too. It's why we still use "45 UKP" or "45 GPB" in usenet posts -- when we remember to.
(Also, since there's no MIME or encoding data in the original post that made
it to csaa, any news reader which is managing to display a Pound sign is
making some really big assumptions to get there).
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
--- Synchronet 3.22a-Linux NewsLink 1.2