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

171–180 of 211 posts

Re: The plague of emoji insertion in French docs

#171

Post by cryptonector »

wewtyflakes wrote: post #169
shakow wrote: post #167

Earlier quoted context omitted.

I don't know, what would happen in English if you didn't capitalize the days of the week? Do people point and laugh? You get disciplined? Or would English speakers accept this as a better way to write the days of the week? No human language on Earth is in a position where it can laughs at others for their idiomatisms.

I do not think that was their point (to laugh at other languages), but rather, that there may be contemporary situations in which warrant rethinking the idioms of a language. As an aside, I do not think many people who speak english would even notice a lack of capitalization for the days of the week.

I've had colleagues who refuse to use capitals in most cases. And yet their writing is completely comprehensible.

Re: The plague of emoji insertion in French docs

#172

Post by Aardwolf »

nyanpasu64 wrote: post #123
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…

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.

In Kate you can turn off auto complete in the Settings, Editing, Auto Completion tab, or set a minimal word length to complete to something long so it's less likely to appear for common letter combinations but still possible for longer words

Of course as always no settings to have a way to enable auto completion but not use the standard typing keys :(

Re: The plague of emoji insertion in French docs

#173

Post by [deleted] »

cryptonector wrote: post #145
sdeframond wrote: post #68

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…

[deleted]

Re: The plague of emoji insertion in French docs

#174

Post by torben-friis »

jobigoud wrote: post #89
torben-friis wrote: post #39

Earlier quoted context omitted.

> I live in Muenchen, not München As someone from Espanya, I welcome you to the club.

Interestingly that's the Catalan spelling.

Not that you guys have it any better (with the ç and two, rather than one, sets of accent marks)

Re: The plague of emoji insertion in French docs

#175

Post by nephanth »

sdeframond wrote: post #68
rodelrod wrote: post #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 ov…

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)

Libreoffice, and I believe ms word too, automatically replaces the space before a colon with a non-breaking one

Re: The plague of emoji insertion in French docs

#176

Post by nephanth »

jobigoud wrote: post #101
rodelrod wrote: post #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 ov…

A modern solution is simply to have non-breaking space easily accessible in your keyboard layout for when you need it. In the BÉPO layout this is at SHIFT + space. Especially simple since all double punctuations (:?!; those that require an nbsp before them) are also accessed with SHIFT.

Azerty layout could certainly map shift-space to unbreakable space too

But honestly, rather than changing keyboards (which is hard), why doesn't Google just pick a shorthand that doesn't break typography rules, like `@` instead of `:`

Re: The plague of emoji insertion in French docs

#177

Post by derac »

derac wrote: post #107

I have a partial solution in TamperMonkey here: https://gist.github.com/derac/887efd8891caa026322b7624954893... I wrote it over my lunch break quickly, it only closes the menu the first time. I was trying to add the functionality to close it every time you enter the key combo, but it wasn't working. If someone wants to improve this feel free. MIT licensed.

doesn't really matter since they are fixing it, but I made this work

Re: The plague of emoji insertion in French docs

#178

Post by xboxnolifes »

Normille wrote: post #140
jobigoud wrote: post #101

Earlier quoted context omitted.

A modern solution is simply to have non-breaking space easily accessible in your keyboard layout for when you need it. In the BÉPO layout this is at SHIFT + space. Especially simple since all double punctuations (:?!; those that require an nbsp before them) are also accessed with SHIFT.

>A modern solution is simply to have non-breaking space easily accessible in your keyboard layout An even better solution would be --for grown up people who have progressed beyond cave-painting and want to communicate using, you know, actual words-- to be able to disable emojis completely. Fucking moronic shite that they are. I've seen people on Twatter and FB have entire conversations in bloody emojis. Talk about re…

I guess you only speak monotonically and avoid interpreting pitch, pauses, and physical cues in conversation as well, since those would be archaic, right?

Re: The plague of emoji insertion in French docs

#179

Post by 9dev »

nells wrote: post #51
9dev wrote: post #19

Earlier quoted context omitted.

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..?

> If American businesses wanted the money of people from other countries, they should've made their systems internationally accessible. They haven’t and they got the money anyway.

Assuming what they got was the maximum obtainable amount, yes :)

Re: The plague of emoji insertion in French docs

#180

Post by 9dev »

generalizations wrote: post #83
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…

There was a comment the other day in the discussion about incorporation in Germany. Someone complained that in Germany, they conduct their business in German: the justification was, it's our country, our language, get used to it. Maybe the blunt response to complaints about the US American bias is, it's our software, our (ASCII/Unicode) language, get used to it.

If I was trying to incorporate in the USA, and the registration form would be unable to process diacritics, sure — even though that would neglect a large part of your own population (see the ASCII debacle) — but we’re talking about internet services marketed globally. I don’t think it’s too much to ask to have an app at least working as designed. We’re not even talking about translating stuff!
Post reply on HN