On Mon, 26 Feb 2024 01:03:50 +0300, Aug -> Nicholas Boel wrote:

I got the sarcasm. But then I was just wondering in general what they
have actually done. Even fixing the spelling mistakes and grammatical errors and clarifying some of the tech lingo seems ripe for avoidance.

Some just like the way the hat looks, it seems. :)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Some just like the way the hat looks, it seems. :)

I still think there should badges. :-)

Perhaps a full uniform with boots is required.
--- AfterShock/Android 1.7.5
* Origin: Mobile Pixel 3aXL (2:221/1.59)

On 25 Feb. 2024 18:47, you wrote to August:

Perhaps a full uniform with boots is required.

Maybe next election. Besides boots in my size are really hard to find.

Perhaps they can make an exception and let you wear open-toe boots or just sandals! ..as long as the color matches the official standard!!! :D
--- AfterShock/Android 1.7.5
* Origin: Mobile Pixel 3aXL (2:221/1.59)

On Wed, 28 Feb 2024 01:17:42 GMT
"Maurice Kinal -> Serak the Preparer" <2989@7001.153.1> wrote:

<Esc>:read !trans -b -no-ansi -t he "To pronounce it correctly, I would have to pull out your tongue." | sed 's/^ *//'
.ךלש ןושלה תא ףולשל ךרטצא ,ןוכנ הז תא
אטבל ידכ

Note that the above is Hebrew ... or should be ... and I took the
liberty of stripping out the leading spaces since a 4k terminal results

The hebrew letters appear to be fine under my nntp read Sylpheed.

👍 +1

However, an nntp reader is outside the scope of what fidonet is.

As shown the Hebrew Subject line is exactly 46 utf-8 characters which *should* fit into a FTN Subject which can be up to 71 characters.
However a byte count yeilds 82 bytes which the typical FTN abandonware will consider too long and chop off the last (actually first since
Hebrew is read right to left) 12 bytes. Note I say bytes and not characters since DOS-think types cannot count straight, especially when they treat stings as numbers. Very sad.

Solution: FTS should limit utf-8 chars only to the message body only.

So much for utf-8 and FTS-5003. As is that document is sadly lacking
wrt utf-8 charcters and probably should have it's own documentation in order to escape crippleware developers.

I would tend to agree.

Anyhow.. it seems that utf-8 was "approved" without the evidence of ample usage of utf-8.

Also there is no such thing as LATIN-1. It is the end result of some Gatesian nightmare you can never wake up from.

No comment.

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hey August!

Are you familiar with the UTF-8 echo?

Yes I was aware of it.

Perhaps it was set up to help promote utf-8 inclusion and use.

That sounds reasonable.

Life is good,
Maurice

o- o- -o -o -o o- -o o- o- o- -o -o -o -o -o o- /) /) (\ (\ (\ /) (\ /) /) /) (\ (\ (\ (\ (\ /) ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)