I had to upgrade 'trans' to make this work. As of this post it is 0.9.7.1-release.
I had to upgrade 'trans' to make this work. As of this post it is
0.9.7.1-release.
Works for me although the msg header *NEEDS* a complete overhaul in order to properly count characters rather than bytes. Speaking for myself I see
little to nothing in current standards worth salvaging.
Oh well, not my call thank goodness.
Would you like another nomination to the FTSC so that everyone
shuts down any attempt for you to make things better for today's
standards again? :)
On Sat, 24 Feb 2024 03:54:58 GMT, Maurice Kinal -> MauriceKinal wrote:
Would you like another nomination to the FTSC so that everyone shuts down any attempt for you to make things better for today's standards again? :)
What has the current FTSC group accomplished since the last
election? If nothing changes, what's the point in having it?
It's not the FTSC's job to suggest changes.
If you want changes, you have to implement them as a developper.
And have other developpers follow your changes. If enough nodes
start using those changes, it can be documented by the FTSC as
current practice...
It's not the FTSC's job to suggest changes. If you want
changes, you have to implement them as a developper. And
have other developpers follow your changes. If enough
nodes start using those changes, it can be documented by
the FTSC as current practice...
It's not the FTSC's job to suggest changes. If you want
changes, you have to implement them as a developper. And
have other developpers follow your changes. If enough
nodes start using those changes, it can be documented by
the FTSC as current practice...
But why the necessity of so many people overlooking practically
a non-event? Do, the members have a commitment to keep their
finger on the pulse where development is occurring?
What has the current FTSC group accomplished since the last
election? If nothing changes, what's the point in having it?
On Sat, 24 Feb 2024 15:44:00 -0500, August Abolins -> Nicholas Boel wrote:
What has the current FTSC group accomplished since the lastIf you re-read my message to Maurice, there was definitely some subtle sarcasm there. In fact, the *only* thing that has happened since the last election has been criticism against any new ideas and them being shut down so they don't have to do any actual work. :)
election?   If nothing changes, what's the point in having it?
Regards,
Nick
... "Take my advice, I don't use it anyway."
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. :)
Some just like the way the hat looks, it seems. :)
I still think there should badges. :-)
Perhaps a full uniform with boots is required.
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!
<Esc>:read !trans -b -no-ansi -t he "To pronounce it correctly, I would have to pull out your tongue." | sed 's/^ *//' .?????? ?????????? ?ª?? ?£???????? ?????????? ,???????? ???? ?ª?? ???????? ??????
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.
maybe the expectation of having utf-8 is overrated in this hobby
network?
<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
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.
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.
Also there is no such thing as LATIN-1. It is the end result of some Gatesian nightmare you can never wake up from.
.ךלש ןושלה תא ףולשל ךרטצא ,ןוכנ הז תא
אטבל ידכ
The hebrew letters appear to be fine under my nntp read Sylpheed.
However, an nntp reader is outside the scope of what fidonet is.
Solution: FTS should limit utf-8 chars only to the message body
only.
it seems that utf-8 was "approved" without the evidence of ample
usage of utf-8.
No comment.
More reason NOT to let developers lead the standardization process,
nevermind the users of their apps. There is definetly a confict of interest, nevermind the ones who are clueless as to how things REALLY work.
Are you familiar with the UTF-8 echo?
Perhaps it was set up to help promote utf-8 inclusion and use.
| Sysop: | deepend |
|---|---|
| Location: | Calgary, Alberta |
| Users: | 253 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 16:38:22 |
| Calls: | 1,646 |
| Files: | 3,994 |
| Messages: | 387,905 |