On 24 Mar, Wakefield 2024 wrote in message
<ap.c6d44e5b46.a701a0a.m.conroy@argonet.co.uk>:

> 4.30pm, with an entrance fee of 35.

I'm guessing UTF-8 shenanigans here... that's 5 UKP, of course.

--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

In message <mpro.savljw0505yr208tk.news@stevefryatt.org.uk>
Steve Fryatt <news@stevefryatt.org.uk> wrote:

> On 24 Mar, Wakefield 2024 wrote in message
> <ap.c6d44e5b46.a701a0a.m.conroy@argonet.co.uk>:

>> 4.30pm, with an entrance fee of 35.

> I'm guessing UTF-8 shenanigans here... that's 5 UKP, of course.

Grrrr UTF-8 strikes again, but surprised it put a 3 usually its a Black
blob or a black blob with a ? in it.

--
Chris Hughes

In article <mpro.savljw0505yr208tk.news@stevefryatt.org.uk>,
Steve Fryatt <news@stevefryatt.org.uk> wrote:
> On 24 Mar, Wakefield 2024 wrote in message
> <ap.c6d44e5b46.a701a0a.m.conroy@argonet.co.uk>:

> > 4.30pm, with an entrance fee of 35.

> I'm guessing UTF-8 shenanigans here... that's 5 UKP, of course.

The c.s.a.announce Charter does clearly say:
"3. No top bit characters may be used (eg. pound sign)"

I do normally spot these and edit the post accordingly (I've given up
sending posts back and asking the originator to edit, because people
don't listen or learn), but please don't assume I will do this for you
every time. To ensure your posts are propagated across all news servers
without changes, please make sure you post in accordance with the
c.s.a.announce Charter: https://www.owlart.net/csaa/charter.html

Andrew
(Moderator, c.s.a.announce)

--
+--------------------------------------+---------------------------------+
| Andrew Conroy, Owl-Art Un-Ltd. | email: a.m.conroy@owlart.co.uk |
| Using an Acorn RiscPC SA110 | |
+--------------------------------------+---------------------------------+
The impossible I can do at once, miracles take a little longer!!

In article <5b476734aca.m.conroy@owlart.co.uk>,
Andrew Conroy <a.m.conroy@owlart.co.uk> wrote:
[Snippy]
> The c.s.a.announce Charter does clearly say:
> "3. No top bit characters may be used (eg. pound sign)"

You cannot be serious!

That's so archaic...

Dave

--

Dave Triffid

On 26 Mar, Dave wrote in message
<5b478f956ddave@triffid.co.uk>:

> In article <5b476734aca.m.conroy@owlart.co.uk>,
> Andrew Conroy <a.m.conroy@owlart.co.uk> wrote:
> [Snippy]
> > The c.s.a.announce Charter does clearly say: "3. No top bit characters
> > may be used (eg. pound sign)"
>
> You cannot be serious!
>
> That's so archaic...

Given that at least one RISC OS news/mail client was still unable to
sensibly handle endcoding details in its headers when I last looked[1], it's
kind of essential to avoid anything in a message that might have multiple
interpretations.

1. So this may have improved recently.

--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

On 26 Mar, Andrew Conroy wrote in message
<5b476734aca.m.conroy@owlart.co.uk>:

> In article <mpro.savljw0505yr208tk.news@stevefryatt.org.uk>,
> Steve Fryatt <news@stevefryatt.org.uk> wrote:
> > On 24 Mar, Wakefield 2024 wrote in message
> > <ap.c6d44e5b46.a701a0a.m.conroy@argonet.co.uk>:
>
> > > 4.30pm, with an entrance fee of 35.
>
> > I'm guessing UTF-8 shenanigans here... that's 5 UKP, of course.
>
> The c.s.a.announce Charter does clearly say: "3. No top bit characters may
> be used (eg. pound sign)"

Indeed. I didn't write this particular post, and clearly didn't check it
carefully enough for stuff that wouldn't get through.

> I do normally spot these and edit the post accordingly (I've given up
> sending posts back and asking the originator to edit, because people don't
> listen or learn), but please don't assume I will do this for you every
> time.

Um. With respect, I *don't* assume that you will correct posts for me. I can
only think of a couple of issues which have occurred with posts that I've
sent to csaa -- this one, and one where my news client appeared to have
screwed up the Subject line in a somewhat 'special' way that I now very
specifically work around when doing WROCC's announcements.

My post here about UTF-8 was simply to highlight that the price in the
announcement was incorrect, that it wasn't 35 GBP, and what had probably
happened -- I'm well aware of the ASCII limitation. I also can't see any
blame being apportioned anywhere.

Although I'm told that I may be sending a replacement post to csaa shortly,
in case anyone was scared off by the apparent 1750% increase in ticket
prices this year...

--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

On 26/03/2024 18:12, Steve Fryatt wrote:
> Although I'm told that I may be sending a replacement post to csaa shortly,
> in case anyone was scared off by the apparent 1750% increase in ticket
> prices this year...

I thought you making it a Veblen good.

---druck