Live data from Hacker News

The plague of emoji insertion in French docs

bibelo.info

121–130 of 211 posts

Re: The plague of emoji insertion in French docs

#121
post #95

Earlier quoted context omitted.

IIRC, Teams supports Markdown-style code, either `single line` or ``` multi line ```

Truly a joy on German keyboards where ` is a dead key that makes the system wait for an e, or an a to receive that accent and certain OS don't come with a nodeadkeys alternative keyboard map. I often find myself with the ` in the copy/paste buffer when worrying code-heavy markdown because pasting is so much easier...

Can't you just type [deadkey]+Space to get the ‘undead’ version? That works on Linux and MacOS and ChromeOS.

Re: The plague of emoji insertion in French docs

#122
post #42

Typographic nerd: technically, you should you use a non-breaking space (espace insécable) before colons in french. Doing that does not show the popup. Wait, what do you mean your keyboard layout does not have it? Keyboard layout nerd: you should use a keymap that has it. Like AFNOR's latest AZERTY or BÉPO. Historical nerd: traditionally wordprocessors have auto-inserted non-breaking spaces before colons, why should I…

Or you should use a line-breaking algorithm that does not suggest a break at that location. Line breaking is supposed to be tailored to language.

I'd agree, but this is even more subtle, as a sibling comment to yours said: the space is actually smaller. So text rendering should take this rule into account as well. But then you're assuming that you're doing single-language text rendering. Putting the character at writing time still seems like a simpler tradeoff (maybe with editing help like auto-replace or correction).

Re: The plague of emoji insertion in French docs

#123
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…

Interestingly, when using Kate as a Markdown editor I'm interrupted by the word-based completion panel popping up, grabbing input, and incorrectly completing words when I press Enter. I wish it either didn't auto-popup or didn't grab input in Markdown mode.

Re: The plague of emoji insertion in French docs

#124
post #82
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 live in France but use QWERTY instead of AZERTY, and I once had an opposite problem: on a French website, there was an for phone number, validating that it stays [0-9] on each keystroke. The validation was done by checking for the AZERTY-specific key combos that result in 0-9; on AZERTY to get a you need to press SHIFT+ . So if you had a QWERTY keyboard, you could not enter your phone number, the input stayed blank…

They didn’t allow NumPad?

Re: The plague of emoji insertion in French docs

#125

This annoys the hell out of me and I only speak English. Microsoft is probably the biggest development-focused company in the world, but their own work communications app, Teams, doesn't allow you to paste small pieces of code in a chat because it replaces punctuation with emoji. Regardless, if I want an emoji, I will type the emoji. If I typed ':)' I want ':)' not some stupid yellow face. Meta's Facebook Messenger d…

My way of getting around the emoji conversions from ':)' to a smiley face is typing it in reverse: '(:' or '):'.

I don’t remember which software, but I’ve seen those being converted as well.

Re: The plague of emoji insertion in French docs

#126

This annoys the hell out of me and I only speak English. Microsoft is probably the biggest development-focused company in the world, but their own work communications app, Teams, doesn't allow you to paste small pieces of code in a chat because it replaces punctuation with emoji. Regardless, if I want an emoji, I will type the emoji. If I typed ':)' I want ':)' not some stupid yellow face. Meta's Facebook Messenger d…

Totally agree. In some software, a strategically placed backslash helps.

Re: The plague of emoji insertion in French docs

#128

This space before the colon and other marks in French should actually be a narrow non-breaking space (U+202F) [0]. There's no key for it in the AZERTY layout. This has been a problem since the typewriter age. People having to get on with their jobs coped with it by using a full, breaking em-space. Unless this gets replaced automatically by the word processor, you get horrid typography and misplaced line breaks all ov…

> Especially simple since all double punctuations (:?!; those that require an nbsp before them) are also accessed with SHIFT.

I just tested with `setxkmap fr`. These are not shifted:

    :!;
Only this requires Shift:

    ?
Also French layouts use an inverted number row (although none of those are accessed through that row).

Re: The plague of emoji insertion in French docs

#129
So this was reported on October 31st, then escalated on November 3rd, and the "feature" is still in there. Seeing how severly this impacts users from France, this is slightly diappointing.

Here is a discussion in the product support forum:

https://support.google.com/docs/thread/186496870/how-to-deac...

Re: The plague of emoji insertion in French docs

#130

Earlier quoted context omitted.

Well, double colon :: is just as convenient, make more sense and not a problem in either French or English. Even in English, you might want to stick an emoji to the previous word. Like Hell::devil:: (my nephew would like that though).

Double colon would make talking about perl even worse (:: is namespace separator) -- it's already bad enough that any namespace starting with D becomes an emoticon in pretty much all online editors. This stuff should just stop. Operating Systems / Browser vendors should instead standardize on a hotkey to bring up an emoji selector that steals focus to filter via typing and inserts on enter key.

Code should be quoted upfront.

Finding some sequence that also isn’t a valid Perl substring is impossible, in any case.

Post reply on HN