| |
DF3VI > HELP 27.11.05 15:11l 37 Lines 1850 Bytes #999 (30) @ WW
BID : RBFDB0II_093
Read: DO7NDM GUEST
Subj: Re: Suffix 2 again.
Path: DB0FHN<DB0MRW<OK0PPL<DB0RES<DB0LJ<DB0OVN<DB0II
Sent: 051127/1402z @:DB0II.#NRW.DEU.EU [BCM M'Gladbach] obcm1.06b55 LT:030
From: DF3VI @ DB0II.#NRW.DEU.EU (Patrick)
To: HELP @ WW
Reply-To: DF3VI @ DB0OVN.#NRW.DEU.EU
X-Info: Sent with login password
Hello Dick.
Character sets become a strange thing when you leave the ASCII characters
(32-127). There are so many national code pages, and each and every has
different signs at the same character number. Not only special aphabet
letters (as French accents and German Umlaute) appear at different positions,
also other special symbols are scattered differently across the code page.
To make things more complex, even within the same codepage symbols are not
equal when it comes to different fonts. And to make things more complex,
Microsoft also changed character sets during the developement of Windows;
Win 3.1 is different from Win95. Still both character sets exist in WinXP,
and special letters (Umlaute) writen e.g. in the MS-Notepad editor will not be
displayed correctly with WinWord or MS-WordPad.
So, here on my PC, I have three different apperances for the squared-symbol,
even though all through this program (WPP) the same font (Courier) is used.
I see a squared symbol for alt-253 (²), but when switching to the other
codepage it becomes a square. In the message list, the same character is a
"y" with an accent (´) on top (ý)! Isn't that crazy?
But it becomes even more strange when I see you writing:
> Well, Clyde, I received E=MC² (CHR$178) not (CHR$ 253), so I would like to
The symbol I see is 253, not 178. The alt-178 you mention would be a vertical
bar (¦) here on my screen.
I wonder what you see instead?
Why your program changes characters when you're backscrolling I don't know.
My program doesn't do it. But sometimes it mixes up code pages after a
disconnect, and special characters are displayed differently than before.
It seems to be a common windows problem somehow...
73, Patrick
Read previous mail | Read next mail
| |
