Much better eh?
@MSGID: 1:153/7001.250 594a0a32
@CHARSET: CP1252
Hey All!
Que son estos? -> ? Sh sh Zh zh oe OE Ye
Life is good,
Maurice
... Don't cry for me I have vi.
--- GNU bash, version 4.4.12(1)-release (x86_64-silvermont-linux-gnu)
* Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.250) SEEN-BY: 123/141 135/300 140/1 153/7001 154/10 20 30 40 700 227/201 261/38 SEEN-BY: 340/800 3634/12 15 22 24 27 50
@PATH: 153/7001 154/10 3634/12
@MSGID: 1:153/7001 594a291d
@REPLY: 1:153/7001.250 594a0a32
Hey Maurice!
After viewing it at the TUXPOWER echo on Prism you hunch about it doing nothing was correct. The characters that happen to coincide between ISO-8859-1 and CP1252 rendered perfectly but the ones that don't didn't. It does help confirm that to BBBS LATIN-1 in all likelihood is ISO-8859-1 even though it really isn't. ;-)
For the record here is the 'iconv -f cp1252 -t utf8' of the line of interest;
¿Que son estos? -> € Š š Ž ž Œ œ Ÿ
Much better eh?
Life is good,
Maurice
... Don't cry for me I have vi.
--- GNU bash, version 4.4.12(1)-release (x86_64-bonnell-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) SEEN-BY: 123/141 135/300 140/1 154/10 20 30 40 700 227/201 261/38 340/800 SEEN-BY: 3634/12 15 22 24 27 50
@PATH: 154/10 3634/12
¿Que son estos? -> € Š š Ž ž Œ œ Ÿ
I am not sure you can view the above correctly but your editor flying
the CP437 banner seems to be doing the correct thing by not messing
with the codes. The above quote shows perfectly as UTF-8 characters
as they should be. Most, if indeed not all, FTN editors get it wrong including golded so I suspect you are doing something funky there.
encapable of handling
Hey mark!
It cannot be done in CP437. The experiment was to see what BBBS would
map it out to as that would tell the tale about what LATIN-1 truly is
as far as it is concerned.
From what I could tell it really is ISO-8859-1 despite that LATIN-1 is *NOT* an alias for it and never was or will be.
Now I read that HTML5 is replacing it with CP1252 since over 90% of
users actually are using CP1252 whether or not they know that they
are.
¿Que son estos? -> € Š š Ž ž Œ œ Ÿ
I am not sure you can view the above correctly but your editor flying the CP437 banner seems to be doing the correct thing by not messing with the codes. The above quote shows perfectly as UTF-8 characters as they should be. Most, if indeed not all, FTN editors get it wrong including golded so I suspect you are doing something funky there.
i was only posting what appeared here, my friend :)
i haven't even tried to go that deep on these things
i'm an old pascal coder
i run my GoldEd+ in a cp437 wrapper.. this so i can properly view
""high ascii"" characters
i run my GoldEd+ in a cp437 wrapper.. this so i can properly view
""high ascii"" characters
Yeah right.
I'd like to see a screenshot of you viewing this message in your cp437 wrapped golded if that is possible.
€ Š š Ž ž Œ œ Ÿ
it looks just like quoted above ;)
4bytes 2bytes 2bytes 2bytes 2bytes 3bytes 3bytes 2bytes
single byte 0x00 thru 0xff as IBM intended O:)
it looks just like quoted above ;)
If indeed it is CP437 then it looks nothing like it is quoted since they are utf-8 characters to a capable editor.
4bytes 2bytes 2bytes 2bytes 2bytes 3bytes 3bytes 2bytes
Nope. The first one (Euro symbol) is 3 bytes
€
Š
š
Ž
ž
Œ
œ
Ÿ
they all have the byte counts i stated... i don't care what
symbols or characters they are...
this link is of the original message as viewed on my screen...
this link is of the original as viewed with GoldEd's "info" view
which includes hex dumps...
it will really trip you out (as it did me) because it does not
depict the ones with the tilde "~" as three byte entities like
they are displayed...
have fun :)
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 920 |
Nodes: | 10 (1 / 9) |
Uptime: | 124:28:57 |
Calls: | 12,192 |
Calls today: | 1 |
Files: | 186,528 |
Messages: | 2,238,006 |