151–160 of 211 posts
Earlier quoted context omitted.
It may work for you, but there are users of languages that simply cannot be covered by QWERTY, and in these cases they would like from developers to simply fix their goddamn code, and bind to keys, not characters.
You are correct. It works for me.
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…
Google's currently demanding I settle an invoice for an account I closed... and the only way to do this, or even get support, is if you have a Google account. And zero way of replying to the email their Collections department.
On the one hand they have a massive dominant position in multiple markets. On the other hand, if you're even slightly off the happy path you don't exist.
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…
even messenger supports the backticks and triple backticks now
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…
> 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. Don't you just put it in backticks `like this`? Even for really short things, it seems clearer and it avoids the machine "helpfully" changing things. (Your general point is correct, of course, just suggesting a solution to this very particular nuisance)
I so so wish we could standardize on GitHub markdown for all these things!
Auto insertions or anything that does things behind the users' back should go die in a fire.
I didn't realize French was written with spaces before colons. It might be time to lose that space, similar to how we don't double space after period. I'm not saying G.Docs or any editor should dictate how French is written, only being pragmatic if I have to choose between (no space): or unwanted emojis ending up in docs.
Typographically speaking English language text should have a wide space following a sentence-ending period [that isn't also a paragraph-ending period]. However, because wide spaces are not easy to type on normal keyboard layouts, the simplest thing to do is to type two spaces after sentence-ending periods and let the word processor change those to wide spaces when using a proportional font. When using a fixed-width font, however, it should always be two spaces after a sentence-ending period for two reasons: to disambiguate non-sentence-ending periods, and to make it easier to read. Coders write a lot of text in fixed-width fonts, so we should write two spaces after sentence-ending periods in, e.g., code comment blocks.
I didn't realize French was written with spaces before colons. It might be time to lose that space, similar to how we don't double space after period. I'm not saying G.Docs or any editor should dictate how French is written, only being pragmatic if I have to choose between (no space): or unwanted emojis ending up in docs.
The French aren’t gonna change their language over an emoji picker. :slightly_smiling_face:
I didn't realize French was written with spaces before colons. It might be time to lose that space, similar to how we don't double space after period. I'm not saying G.Docs or any editor should dictate how French is written, only being pragmatic if I have to choose between (no space): or unwanted emojis ending up in docs.
We used to double-space after a period because that looked better on monospaced typewriters. But in French it's simply a part of punctuation, and getting it wrong means you wrote it wrong. It's as wrong as if I'm writing English and put a space before the ':' or '!', or put a comma after a quotation mark. French people shouldn't have to change their language to type in Google Docs. It should be the other way around.
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)
It's more complicated than you imagine it is. Basically you need to know both: whether the current locale is a French locale, and also whether original text was written in a French locale. The former is easy enough, but also very annoying to multilingual people since one might run in a Spanish locale but occasionally write in French. So that's not a solution. The latter is... hard to do, because while Unicode has lan…
Huh? MDN doesn’t mention this … why are they deprecated?