Live data from Hacker News

The plague of emoji insertion in French docs

bibelo.info

41–50 of 211 posts

Re: The plague of emoji insertion in French docs

#41
post #23

Earlier quoted context omitted.

How do you type ä ö ü ß ?

Personally, I don't. I live in Muenchen, not München. When strictly needed, CTRL+C/CTRL+V from a Google search makes the trick. When writing email/docs, autocorrector for the win. Same thing in Italian: `e instead of è. Although, the German replacement is cleaner, I'd say.

> I live in Muenchen, not München.

That's… quite certainly not an opinion shared with all of your fellow inhabitants.

Re: The plague of emoji insertion in French docs

#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 care now ?

Re: The plague of emoji insertion in French docs

#43
post #23
post #18

Earlier quoted context omitted.

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…

How do you type ä ö ü ß ?

[deleted]

Re: The plague of emoji insertion in French docs

#44
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 over the place.

The Académie Française should have dealt with this years ago, if their ass wasn't stuck in the 17th century.

[0] https://www.compart.com/en/unicode/U+202F

Re: The plague of emoji insertion in French docs

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

Unless it's changed recently, IntelliJ IDEA has similar annoyances[0]. Again, using the equivalently placed key works instead. Are they using scan-codes for some reason? Seems extra bizarre given that JetBrains isn't even a US based company!

[0] https://intellij-support.jetbrains.com/hc/en-us/community/po...

Re: The plague of emoji insertion in French docs

#46
post #4

It's the same with Gitlab issues and comments and it's a small but very real pain.

Same for Github as well. Super annoying when you're in the middle of an issue

UX testing should be done in a stressful and chaotic environment. Good UX becomes invisible, bad UX becomes abundantly obvious.

Re: The plague of emoji insertion in French docs

#47
post #18
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…

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.

Re: The plague of emoji insertion in French docs

#48
post #23
post #18

Earlier quoted context omitted.

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…

How do you type ä ö ü ß ?

French on US intl here ä ö ü ß are easy to make on such a setup but also the accented letters like é à ô or the infamous ç. It is even easier to type them in capital than it typically is on AZERTY (French keyboard) or QWERTZ (German one)

Re: The plague of emoji insertion in French docs

#49

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)

Re: The plague of emoji insertion in French docs

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

Even at a multinational like apple. I was fighting in the provisioning dash board a few years ago because it would not load. Issue was my last name which has an umlaut in it. This wasn't 1990 it was 2012 issh and I still see companies unable to deal with umlaut. I believe either FedEx or UPS still can't deal with it. In top of that Swiss mail is quite strict to how a letter is addressed and what is written on the mai…

When I was living in Japan I always had to "romanize" my Japanese address if I got something shipped from USA because USPS only allows ASCII. Even if this did create problems locally - post always arrive quicker (in my experience) if the address is in proper Japanese. When I got mail from my home country I got it forwarded via my company and they always just stuck on a printed label with my address, in Kanji. No problems there. Worked fine for years.

However, my home country postal system has since changed to an online system for sending post out of the country: You go to a website and enter the destination address, then you pay and it'll print a code which you just give to the actual post office when you bring the letter/package whatever. What's infuriating is that they don't allow Japanese addresses - I can enter it, but it just creates an error message. So I again have to come up with a crude romanized address and cross fingers that it'll arrive (which it usually does - but up to a few weeks delayed).

In short - things are not getting betters over the years.

Post reply on HN