Hacker News Reader

Comment by szszrk | Hacker News Reader

I recall era before UTF8 wide adoptiont to be a mess of many other encodings, multiple even in the same language... Not a refreshing memory for me.

View on HN

Even today, Japanese text online and elsewhere uses a variety of encodings. It's sometimes a frustrating experience. Compared to other languages, it is common to see non-Unicode encodings. In particular, Shift JIS (actually, the Windows-specific variant called Windows-932, which is incompatible with JIS X 0213:2004, called "Shift JIS 2004". Old enough Unix and Linux servers used EUC-JP, and Mac OS has its own encoding).

Well, for something like an IRC client it is up for the user to set the correct one.

:) what is the correct one? It's different for each server, or even channel. IRC clients usually supported such custom settings. But then there was the matter of the other end of your screen - your terminal and maybe screen session I which it run.

I used to have an IRC config that was different for each server and sometimes channel, then displayed that in one shared encoding with other chat apos, then converted that on the fly with screen to match encoding of other apps.

Now I just had to make sure to convert encodings and line endings of all config files, any text file, or even source code and scripts...

Nowadays you just paste emojis in code and it's there, it works anyone, including the user. Huge change.

The correct one is the one that doesn't get you yelled at and possibly banned by the rest of the channel.

Yes. Today's messaging services require no skills whatsoever. Getting yelled at the first time you log in establishes pecking order and ensures people weigh their words.

Discord doesn't have these kind of safeguards.

Reply on news.ycombinator.com