var x:Pointer;
The :P changes to tongue out emoji
111–120 of 211 posts
var x:Pointer;
The :P changes to tongue out emoji
Earlier quoted context omitted.
Or, word processors could understand that the pattern "some-chars" + + ":" must be treated as a single word in French. (I guess it's more complicated than I imagine it is, alright)
And thus impossible to use the emoji inserting feature, and other bugs (silently replacing whitespace with different but looking the same whitespace will make for fun issues)
Earlier quoted context omitted.
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…
The issue is that a very common key to hit after a colon is Enter - which selects the emoji in question. If you simply keep typing other letters, you don't have a problem.
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…
Earlier quoted context omitted.
And thus impossible to use the emoji inserting feature, and other bugs (silently replacing whitespace with different but looking the same whitespace will make for fun issues)
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).
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.
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.
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…
Non-breaking spaces are transformed automatically when writing French by Word, LaTeX, and other text processors. Why would you want to learn the many ways of writing a spacing character, when your computer can do it for you?