Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In your example... I wouldn't really care how it is stored, as long as it looks right on the display, and I don't have to go through contortions to enter it on an input device... for example, I don't care that 'a' maps to \x61 ... it's a value behind the scenes... it's the interface to that value.

As long as the typeface/font used can display the character/combination reasonably, and I can input reasonably it doesn't matter so much how it's used...

Now, having to type in 2-3 characters to get there, that's a different story, and one that should involve better input devices in most cases.



> I wouldn't really care how it is stored, as long as it looks right on the display

It becomes a problem when you have other uses besides reading text, such as sorting or searching.


That's why you can normalize the input to certain UTF-8 patterns for this purpose. Same should go for passwords before hashing them.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: