@MSGID: 1:153/757.26 9288b85a
@TID: Mystic BBS 1.12 A46
@TZUTC: 0000
The theremin’s mystery endures, and virtuosos are still fighting for
Original Article:
https://www.atlasobscura.com/articles/theremin-centennial
Happy 100th Birthday to the Theremin, Instrument of the Future
Hi Charles,
On 2020-12-08 15:30:33, you wrote to All:
@MSGID: 1:153/757.26 9288b85a
@TID: Mystic BBS 1.12 A46
@TZUTC: 0000
The theremin’s mystery endures, and virtuosos are still fighting fo
Your message contains (probably) utf-8 characters, but no CHRS: kludge. :-(
@MSGID: 1:153/757.26 9288b85afighting fo
@TID: Mystic BBS 1.12 A46
@TZUTC: 0000
The theremin’s mystery endures, and virtuosos are still
Your message contains (probably) utf-8 characters, but no CHRS:
kludge.
:-(
It could well be on the UTF-8. Is there a problem with that?
I copied the article into a text editor which saves as UTF-8 by
default since I've bee been told that direct copy/paste comes out ugly
at times.
As far as the CHRS: Kludge, I don't know what that is or where it comes s from. I'm using a normal release of Mystic, so I don't know why it wouldn't
be there.
I copied the article into a text editor which saves as UTF-8 by default since I've bee been told that direct copy/paste comes out ugl at times.
As far as the CHRS: Kludge, I don't know what that is or where it com from. I'm using a normal release of Mystic, so I don't know why itwouldn't
be there.
Without it the message editors of the readers used throughout fidonet, don't know which character set was used to post the message, and most default to plain ascii in that case, and won't show the utf-8 characters correctly. And your message becomes somewhat unreadable...
Without it the message editors of the readers used throughout
fidonet, don't know which character set was used to post the message,
and most default to plain ascii in that case, and won't show the
utf-8 characters correctly. And your message becomes somewhat
unreadable...
So copying and pasting to a text editor, then again to the default
editor in mystic didn't help on your end.....
So copying and pasting to a text editor, then again to the default editor in mystic didn't help on your end.....
I don't know. Maybe it would look even worse if you didn't? ;-)
This is what it (partly) looks like on my system:
https://susepaste.org/view/raw/d59e9325
1:153/757.26 9d058e28
On 08 Dec 2020, Wilfred van Velzen said the following...
So copying and pasting to a text editor, then again to the default
editor in mystic didn't help on your end.....
I don't know. Maybe it would look even worse if you didn't? ;-)
This is what it (partly) looks like on my system:
https://susepaste.org/view/raw/d59e9325
Interesting. So, back to the drwaing board.
Your message contains (probably) utf-8 characters, but no CHRS:
kludge.
:-(
It could well be on the UTF-8. Is there a problem with that?
Not if there is an accompanying CHRS kludge. ;)
Most of the time the "problem" is the two forms of single and double quotes (since there is a an open quote and a closed quote look for each) and the ellipses.
Put your quoted material into something like "Notepad++" with an
intitial setting ANSI, and then toggle it to UTF-8. The problem chars will then be obvious:
.
https://brorabbit.g0x.ru/pic/5fcfcdbb.jpg
Hi Wilfred!
08 Dec 20 17:52, you wrote to Charles Pierson:
Your message contains (probably) utf-8 characters, but no CHRS:
kludge.
:-(
It could well be on the UTF-8. Is there a problem with that?
Not if there is an accompanying CHRS kludge. ;)
Even my post about the book Us Conductors had an ellipses in the body. Pasting the text into Notepad did not convert it or change it. :(
I find that the most often 8-bit chars that get overlooked when copying/pasting
are the alternate representations of the double and single quotes, and
the ellipses.
It could well be on the UTF-8. Is there a problem with that?
Not if there is an accompanying CHRS kludge. ;)
Even my post about the book Us Conductors had an ellipses in the body. Pasting the text into Notepad did not convert it or change it. :(
I find that the most often 8-bit chars that get overlooked when copying/pasting are the alternate representations of the double and single quotes, and the ellipses.
Most of the time the "problem" is the two forms of single and double
quotes (since there is a an open quote and a closed quote look for
each) and the ellipses.
Put your quoted material into something like "Notepad++" with an
intitial setting ANSI, and then toggle it to UTF-8. The problem chars
will then be obvious:
.
https://brorabbit.g0x.ru/pic/5fcfcdbb.jpg
OK. There isn't a text editor for Android which I have found yet that
does ANSI. Most default to UTF8 although I have found one that has USASCII, which does make a mess of some of the characters.
However, on my MysticBBS board here, which reads the message fine, leads me
to believe that UTF8 isn't the issue. It must be the lack of CHRS: kludge that Wilfred mentioned.
Dealing internationally as we are there are always going to be some characters that don't always translate correctly. The name Bjorn, when spellled properly doesn't come across correctly, nor does most Cyrillic.
So, apparently, I need to find out why these messages are lacking that Kludge.
--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
Sysop: | Xerxes |
---|---|
Location: | Azle, Texas |
Users: | 119 |
Nodes: | 10 (0 / 10) |
Uptime: | 101:08:46 |
Calls: | 3,018 |
Calls today: | 0 |
Files: | 155 |
U/L today: |
0 files (0K bytes) |
D/L today: |
0 files (0K bytes) |
Messages: | 293,593 |
Posted today: | 0 |