Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Charset="WTF-8"

wtf-8.xn--stpie-k0a81a.com

Post reply on HN
Print view View original

451–460 of 463 posts

Re: Charset="WTF-8"

#451

Post by account42 »

jojobas wrote: post #216
wruza wrote: post #127

I'll say it again: this is the consequence of Unicode trying to be a mix of html and docx, instead of a charset. It went too far for an average Joe DevGuy to understand how to deal with it, so he just selects a subset he can handle and bans everything else. HN does that too - special symbols simply get removed. Unicode screwed itself up completely. We wanted a common charset for things like latin, extlatin, cjk, cyri…

But hey, multiocular o! https://en.wikipedia.org/wiki/Cyrillic_O_variants#Multiocula... (TL;DR a bored scribe's doodle has a code point)

Huh, wasn't aware of this update.

> The character was proposed for inclusion into Unicode in 2007 and incorporated as character U+A66E in Unicode version 5.1 (2008). The representative glyph had seven eyes and sat on the baseline. However, in 2021, following a tweet highlighting the character, it came to linguist Michael Everson's attention that the character in the 1429 manuscript was actually made up of ten eyes. After a 2022 proposal to change the character to reflect this, it was updated later that year for Unicode 15.0 to have ten eyes and to extend below the baseline. However, not all fonts support the ten-eyed variant as of November 2024.

So not only did they arbitrarily add a non-character (while arbitrarily combinding other real characters) but they didn't even get the glyph right and then changed it to actually match the arbitrary doodle.

Re: Charset="WTF-8"

#452

Post by account42 »

imrejonk wrote: post #43

A system not supporting non-latin characters in personal names is pitiful, but a system telling the user that they have an invalid name is outright insulting.

It's only insulting if you want to be insulted. You'd do better learning to understand that its a computer system and not a personal attack.

Re: Charset="WTF-8"

#453

Post by account42 »

rossdavidh wrote: post #175
notanote wrote: post #126

Earlier quoted context omitted.

That’s the best one of the lot. "Dein Name ist ungültig", "Your name is invalid", written with the informal word for "your".

They're trying to say that you and the server are very close friends, you see? No, no, I get this is not correct, just a joke...

Formal pronouns in German are on their way out anyway, including in but not limited to software interfaces.

Re: Charset="WTF-8"

#454

Post by account42 »

robin_reala wrote: post #118
xigoi wrote: post #80

Earlier quoted context omitted.

This seems to only apply to banks.

It’s a general right to have incorrect personal data relating to you rectified by the data processor.

It's a silly applicaton of that right that doesn't match the original intent. An encoding in a limited character set doesn't make the data incorrect - it's as correct as it can be.

Re: Charset="WTF-8"

#455

Post by account42 »

int_19h wrote: post #402
rmrfchik wrote: post #330

Well, the labels of input fields are written in English yet user enters his name in native language. What's the reason of having name at all? You can call the person by this name. But if I write you my name in my language, what you (not knowing how to read it) can do? Only "hey, still-don't-know-you, here is your info". In my foreign passport I have name __transliterated__ to Latin alphabet. Shouldn't this be the cas…

Unfortunately, the extremely weird and idiosyncratic use of Latin script for English means that straightforward transliterations are usually pronounced incorrectly by people who try to pronounce them according to English rules. And, on the other end of the spectrum, you have attempts to spell phonetically following English orthography, which then causes issues because it's tied to a particular dialect of English. E.g…

"Usually" it's pretty close to the correct pronounciation. Pretty much always it's good enough to be understandable.

Re: Charset="WTF-8"

#456

Post by account42 »

KPGv2 wrote: post #40
cabirum wrote: post #18

How do I allow "stępień" while detecting Zalgo-isms?

I could answer your question better if I knew why you need to detect Zalgo-isms.

Because they are an attack vector. They can be used to hide important information as they overflow bounds (can be solved with clipping but then you need to do that everywhere it matters) and have the ability to slow text renderers to a crawl.

Re: Charset="WTF-8"

#457

Post by account42 »

ahoka wrote: post #134
josephcsible wrote: post #133

What would be wrong with "enter your name as it appears in the machine-readable zone of your passport" (or "would appear" for people who have never gotten one)? Isn't that the one standard format for names that actually is universal?

I would like to use my name as my parents gave it to me, thanks. Is that too much to ask for?

If your parents were smartasses, then yes.

Re: Charset="WTF-8"

#458

Post by account42 »

Etheryte wrote: post #128
ljouhet wrote: post #121

Yes, all these forms should handle existing names... but the author's own website doesn't (url: xn--stpie-k0a81a.com, bottom of the page: "© 2024 ę ń. All rights reserved.")

I think the bottom of the page is you missing the joke. It's showing only the name letters that get rejected everywhere else. Similarly for the URL, the URL renders his name correctly when you browse to it in a modern browser. What you've copied is the canonical fallback for unicode.

It's not a fallback, it's the actual domain name.

Re: Charset="WTF-8"

#459

Post by mabster »

account42 wrote: post #421
dcow wrote: post #323

Earlier quoted context omitted.

I think it’s more of an ethical question than anything. There will always be pranksters and there will never be perfect input validation for names. So who do you oppress? The people with uncommon names? Or the pranksters? I happen to think that if you do your job right, the pranksters aren’t really a problem. So why oppress those with less common names?

No one is being oppressed. Having to use an ASCII version of your name is literally a non-issue unless you WANT to be offended. Maybe also think of the other humans that will need to read and retype the name. Do you expect everyone to understand and be able to type all characters? That's not reasonable. The best person to normalize the name to something interoperable is the user himself, so make him do it at data ent…

I was saying the exact same thing about how I don't understand why people get offended when they have to transcribe their name to use Hanzi!

We should have a world vote to settle which alphabet we use.

Re: Charset="WTF-8"

#460

Post by GoblinSlayer »

account42 wrote: post #425
int_19h wrote: post #390

Earlier quoted context omitted.

For one thing, this concern applies equally to names written entirely in Latin script. Can your CSR reps correctly pronounce a French name? How about Polish? Hungarian? In any case, the proper way to handle this is to store the name as originally written, and have the app that CSRs use provide a phonetic transcription. Coincidentally, this kind of stuff is something that LLMs are very good at already (but I bet you c…

This situation is not the same at all. The CSR might mangle a name in latin script but can at least attempt to pronounce it and will end up doing so in a way that the user can understand. Add to that that natives of non-latin languages are already used to this. For better or worse, English and therefore the basic latin script is the lingua franca of the computing age. Having something universal for internation commun…

FWIW, proquint encoding allows you to pronounce any sequence of bits, though the need for pronunciation eludes me, just copypaste it.
Post reply on HN