Hello

임연준

unread,

Feb 20, 2024, 6:22:25 AM2/20/24

to

nice to meet you

Marco

unread,

Feb 20, 2024, 6:44:58 AM2/20/24

to

Am 20.02.2024 20:20 Uhr schrieb ______:

> nice to meet you

Please choose a proper name instead of the underscores.

--
Gruß
Marco

Spam und Werbung bitte an ichschic...@cartoonies.org

Dan Purgert

unread,

Feb 20, 2024, 7:26:36 AM2/20/24

to

On 2024-02-20, Marco wrote:
> Am 20.02.2024 20:20 Uhr schrieb ______:
>
>> nice to meet you
>
> Please choose a proper name instead of the underscores.

Seems to be an encoding issue -- my newsreader (slrn) throws a warning
about "ks_c_5601-1987".

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

Ray Banana

unread,

Feb 20, 2024, 9:42:52 AM2/20/24

to

Hi

> nice to meet you

Content-Type: text/plain; format=flowed; charset="ks_c_5601-1987"; reply-type=original
Content-Transfer-Encoding: 7bit
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 16.4.3528.331

Please use a newsreader that can properly handle Korean characters.
This will save you lots of unfriendly replies.
Many people will see random characters in your posts.

--

https://www.eternal-september.org

Adam H. Kerman

unread,

Feb 20, 2024, 9:51:04 AM2/20/24

to

Dan Purgert <d...@djph.net> wrote:
>On 2024-02-20, Marco wrote:
>>Am 20.02.2024 20:20 Uhr schrieb ______:

>>>nice to meet you

>>Please choose a proper name instead of the underscores.

>Seems to be an encoding issue -- my newsreader (slrn) throws a warning
>about "ks_c_5601-1987".

I had to look it up. Terminal emulations rarely have the translation for
it, but if it's translated at EUC-KR instead, it can be displayed. Yes,
it's the Hangul for Korean. It's an ancient code page.

Hangul was invented in the mid 15th century to improve literacy with
simpler alphabetic characters, although it came into widespread use as a
phonetic translation of words in the Sino-Korean vocabulary in
the late 19th century. Contrast Hanja, based on traditional Chinese
character, that came into use in the 4th century.

Today, Hanja is still used by some people to write words in the Sino-Korean
vocabulary, and Hangul is used for native Korean words and loan words
from other languages. And you still need to be able to read Hanja to
read older documents.

Adam H. Kerman

unread,

Feb 20, 2024, 9:57:50 AM2/20/24

to

Adam H. Kerman <a...@chinet.com> wrote:
>Dan Purgert <d...@djph.net> wrote:
>>On 2024-02-20, Marco wrote:
>>>Am 20.02.2024 20:20 Uhr schrieb ______:

>>>>nice to meet you

>>>Please choose a proper name instead of the underscores.

>>Seems to be an encoding issue -- my newsreader (slrn) throws a warning
>>about "ks_c_5601-1987".

>I had to look it up. Terminal emulations rarely have the translation for
>it, but if it's translated at EUC-KR instead, it can be displayed. Yes,
>it's the Hangul for Korean. It's an ancient code page.

I have EUC-KR as an option in my terminal emulation. No, it displayed
just one of the three characters.

I could display it using the Online MIME Header Decoder.

https://dogmamix.com/MimeHeadersDecoder/

Hans Müller

unread,

Feb 21, 2024, 8:37:47 AM2/21/24

to

Am 20.02.24 um 12:20 schrieb 임연준:
> nice to meet you
Nice to meet you too.

kyonshi

unread,

Feb 21, 2024, 8:50:52 AM2/21/24

to

for what it's worth Thunderbird seems to display it correctly.

Andy Burns

unread,

Feb 21, 2024, 2:25:15 PM2/21/24

to

Marco wrote:

> schrieb 임연준:

>
>> nice to meet you
>
> Please choose a proper name instead of the underscores.

They appear to be Korean characters (possibly transliterated as lover
year given?)

Andy Burns

unread,

Feb 21, 2024, 2:27:01 PM2/21/24

to

Adam H. Kerman wrote:

> Dan Purgert wrote:
>
>> Seems to be an encoding issue -- my newsreader (slrn) throws a warning
>> about "ks_c_5601-1987".
>

> it's the Hangul for Korean. It's an ancient code page.

Yay, thunderbird does something right!

Adam H. Kerman

unread,

Feb 21, 2024, 2:27:23 PM2/21/24

to

Fascinating. It's an obscure character set for the last several decades,
and wouldn't have been in wide use since 1980s South Korea. If the user,
not living in South Korea in the 1980s, hasn't installed the appropriate
font, how can Thunderbird possibly display it?

You do understand that Ray's concern was nothing to do with the ability
of a client or monitor or terminal emulation to display the appropriate
glyphs but the fact that an appropriate font won't be installed?

Adam H. Kerman

unread,

Feb 21, 2024, 2:32:47 PM2/21/24

to

I cannot confirm that.

It occurs to me that when I used the MIME header decoder in my browser,
it was likely wrong as well. The browser defaults to UTF-8. I could have
seen three character when there were actually six.

It must have been wrong. I probably saw Hanja, now that I know what
Hangul looks like

Andy Burns

unread,

Feb 21, 2024, 3:53:10 PM2/21/24

to

Adam H. Kerman wrote:

> Andy Burns wrote:
>
>> Yay, thunderbird does something right!
>
> I cannot confirm that.

Encoded headers using ?B? base64 are fairy uncommon (compared to ?Q?
quoted printable).

From: =?ks_c_5601-1987?B?wNO/rMHY?= <jooo...@naver.com>

using an online base64 decoder, specifically this one
<https://www.base64decode.org>

and setting the character set to EUC-KR

with source of "wNO/rMHY"

the result is the same as thunderbid displays for the O/P's from: field
i.e the three characters "임연준"

[e-s authentication playing up again]

The Bjornsdottirs - Lightning

unread,

Feb 21, 2024, 10:25:10 PM2/21/24

to

UTF-8 has been a standard for decades, and one in common use for over a
decade. Why still use codepages?

--
Lightning Bjornsson <drago...@chatspeed.net> - Member Switchposters
United for Justice - <https://spufj.trd.is./>

Some people don't like multiline signatures. I kindly request that they
keep their concerns in their own brains. Usenet isn't what it used to be.
The servers are more powerful, have more storage, and have faster uplinks
in even the worst cases. Long sigs can't hurt you anymore.