I have noticed another Mystic echomail problem.
It regards word wrap on a non mystic tosser. Most other Jam capable
BBS's will wrap the words if there is no word wrap in the original message... however Mystic seems to roll the text right off in the
middle of the word.
For instance at the right margen if you had supercell not wrap it
would look like ...
Superce
ll
I think Mystic's tosser handles word wrapping for Mystic... but using
a standard tosser the word wrap is ignored and mystic let's it break
where it will break.
Golded, Elebbs, RA and other systems that use JAM will wrap the
messages automatically if the text does not break at the end of line
with a CR/LF.
Mystic will display messages properly that originate from Mystic,
Platinum Express (wildcat), PCBoard, and other systems that will put
the CR/LF at the end of the message.
I hope that the tosser can be tweaked... and hopefully G00R00 returns refreshed and renewed.
I've found that the problem doesn't lie at the feet of Mystic. The problem is that the originating messages come from OLRs or web-based
NNTP apps where the margins are set to something other than 80
columns. Those readers will inject CR/LF codes in weird places. Is
it Mystic's job to decypher what the writer meant to do?
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 199:52:52 |
Calls: | 2,083 |
Calls today: | 1 |
Files: | 11,139 |
Messages: | 947,896 |