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

The plague of emoji insertion in French docs

bibelo.info

Post reply on HN
Print view View original

11–20 of 211 posts

Re: The plague of emoji insertion in French docs

#11

Post by amadeuspagel »

WA wrote: post #7
9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

Every small indie game ever: action buttons are x and z. Guess what, y and z are swapped on a German keyboard.

That's an illustration that the problem is not so easy.

What your parent comment complains about is that the keyboard shortcut is based on the location of the key, and not the letter.

What you complain about is that the keyboard shortcut is based on the letter, and not the location.

Obviously, these complaints don't contradict each other, both make sense in different circumstances. But figuring that out requires awareness of different keyboard layouts, and of the difference between KeyboardEvent.code (location) and KeyboardEvent.key (letter).

Re: The plague of emoji insertion in French docs

#12

Post by jefftk »

bombcar wrote: post #5
9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

Stuff like this is super, super common. Even where you have things like CTRL + X/C/V for cut/copy/paste it's clear that the letters were picked to be near each other - but then often the shortcuts will remain the same even on keyboards where those keys are nowhere near each other. This can be one of the reasons that switching to Dvorak can be super hard, all the shortcuts become quite weird unless you remap them each…

9ev: pressing the key where American layouts have a slash will [open the search box]

bombcar: often the shortcuts will remain the same even on keyboards where those keys are nowhere near each other

You're objecting to opposite things: you don't like that the shortcuts stayed with the same symbols instead of staying with the physical key, and 9ev the other way around.

(And also 9ev is objecting to misleading documentation)

Re: The plague of emoji insertion in French docs

#13

Post by nells »

9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

If people of other countries didn’t want American bias in their systems they should’ve made their own and made them better than American ones are.

Re: The plague of emoji insertion in French docs

#14

Post by 9dev »

amadeuspagel wrote: post #8
9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

That might a problem with a specific website, but you can easily implement that correctly using the event key property[1]. [1]: https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEve...

Thank you for the suggestion, but that's indeed a problem with lots of websites that get this utterly wrong. Browsing the web using a non-US keyboard is fun.

Re: The plague of emoji insertion in French docs

#15

Post by dietr1ch »

9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

I really hate that so many things break after you switch keyboard layouts.

Many shortcuts are positional, like "hjkl" or "wasd" for moving , or control/meta+numbers but there's no good way to denote them without assuming you are using a qwerty keyboard. Programming against them is possible,but many times there's limitations, ignorance about the different layouts, or straight neglect.

Re: The plague of emoji insertion in French docs

#16

Post by jxy »

aendruk wrote: post #9
9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

My latest peeve here is the websites that try to filter out non-numeric key presses in form fields. You don’t know where my number keys are! Sometimes the only way to enter a number is to copy and paste it from a text editor.

I use Dvorak-dvp, and I hate those form fields.

Re: The plague of emoji insertion in French docs

#17

Post by brookst »

Aardwolf wrote: post #3

Personally I like auto suggestions like this, but I never want it to interrupt typing, so it should never grab input when you press typing-related keyboard keys, including the enter key, space and arrow keys which you need to move the cursor around. I do not want to have to close boxes that appear at arbitrary times with the esc key to continue regular typing, since the box interrupts flow and there is a reaction tim…

I like the implementation in a bunch of IM clients, at least Teams and iMessage: emojis are treated as autocorrect, so if you type the full text version of the emoji (not just the first character!) it gets replaced with the emoji. In the rare cases it's wrong, hitting escape after the autocorrect fixes it.

I don't see why the Google Docs implementation wouldn't work that way. If it really must pop up a box, allow the user to continue typing in document and gradually reduce the list of candidate emojis. As soon as a character is typed that either complete the emoji or rules all of them out, the box goes away.

Re: The plague of emoji insertion in French docs

#18

Post by mrzool »

9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

As multilingual user constantly switching between 3 languages, that's why I fully committed to the US_intl keyboard layout a while ago and ditched the abomination that is QWERTZ. Took a while to get used to, but overall it has been a very noticeable improvement. One layout to cover all languages, no more constant switching.

Edit for clarity: I type "a to get ä and 'a to get à. If I want to type actual quotes followed by a vocal I need to “confirm” the quotes with space before typing the vocal. That’s all there is to it, really.

Re: The plague of emoji insertion in French docs

#19

Post by 9dev »

nells wrote: post #13
9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

If people of other countries didn’t want American bias in their systems they should’ve made their own and made them better than American ones are.

If American businesses wanted the money of people from other countries, they should've made their systems internationally accessible.

I mean, seriously, what kind of antiquated statement is that? Do you actually want to keep geographical borders to persist to the internet, or work towards lower barriers for everyone..?

Re: The plague of emoji insertion in French docs

#20

Post by senand »

mrzool wrote: post #18
9dev wrote: post #2

There's more of this implicit US American bias in modern computing than you would think after the whole ASCII/Unicode mess - I thought they finally learnt something about computers actually being used by other people back then, but no. One of my pet peeves: Badly implemented "press CTRL + / to search". Entering an actual slash, which requires e.g. SHIFT+7 on German keyboards, won't open the search box, but pressing t…

As multilingual user constantly switching between 3 languages, that's why I fully committed to the US_intl keyboard layout a while ago and ditched the abomination that is QWERTZ. Took a while to get used to, but overall it has been a very noticeable improvement. One layout to cover all languages, no more constant switching. Edit for clarity: I type "a to get ä and 'a to get à. If I want to type actual quotes followed…

Same here
Post reply on HN