Hello Apam,

There are times when message just seem to end at some random spot.

The trouble seems to be with messages that contain UTF-8 characters.

One message (two actually) begin with "Bj~Trn" (as seen in golded). When viewing those messages in Magicka I see "Bj" and that's it. Just a blank
screen after that.

I've seen this in Fido a few times but wasn't sure what to think.

The Bj~Trn is what I see in golded when folks spell Bjorn with the two
dots obove the o in UTF-8. I think ;)

If you like I could zip up that jam base and you could have a look?

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On Wed, 23 Oct 2019 05:11:32 -0700
"Al -> apam" <0@106.4.21> wrote:

Hello Apam,

There are times when message just seem to end at some random spot.

The trouble seems to be with messages that contain UTF-8 characters.

[...]

The Bj~Trn is what I see in golded when folks spell Bjorn with the two
dots obove the o in UTF-8. I think ;)

This should be a correctly encoded UTF-8 message with some umlauts

Björn Björn Björn

äöü
ÄÖÜ

and emojis

🧙�♀️
🐉
🔮
🧙
🧙�♂️

---
* Origin: (21:1/151)

This should be a correctly encoded UTF-8 message with some umlauts

Bj�rn Bj�rn Bj�rn

I see your spelling of Bjorn just fine. :)

��� ���

and emojis

?

Your message seems to end here, no tearline, no origin although I see it
fine in golded.

Thanks!

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

This should be a correctly encoded UTF-8 message with some umlauts

Bj�rn Bj�rn Bj�rn

I see your spelling of Bjorn just fine. :)

��� ���

and emojis

?

Your message seems to end here, no tearline, no origin although I see
it fine in golded.

Not sure it's entirely Magicka's fault. Maybe JamNNTPd has some problems with UTF-8 too. My previous message was composed in Thunderbird. If I save this message and open it with a text editor, it complains about invalid characters.


--- GoldED+/LNX 1.1.5-b20180707
* Origin: this message has been mangled by Mystic BBS (21:1/151)

There are times when message just seem to end at some random spot.

The trouble seems to be with messages that contain UTF-8 characters.

It's iconv bombing out due to invalid characters. It's supposed to
replace invalid characters with a ? or something, but it's not.

I've added IGNORE to the list, so now troublesome characters will be
ignored instead, it will be available when I merge the wordwrap branch.

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: Nocturnal - nocturnal.hopto.org:2023 (21:1/125)

There are times when message just seem to end at some random spot.

The trouble seems to be with messages that contain UTF-8 characters.

It's iconv bombing out due to invalid characters. It's supposed to
replace invalid characters with a ? or something, but it's not.

It seems to be that the messages you sent identified as UTF-8 but
weren't. IE, the CP437 o with dots above it was used.

I've made a few changes again, now if iconv bombs out, it will just
display the raw text - you might get funny characters, but at least it
won't be cut off.

Andrew


--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: Nocturnal - nocturnal.hopto.org:2023 (21:1/125)

I've made a few changes again, now if iconv bombs out, it will just display the raw text - you might get funny characters, but at least it won't be cut off.

Yep, I updated and revisited those messages.. Seems to be some off
characters alright, but I can see the whole message now. So that's good progress.

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)