I believe the fact that Polish uses the Latin alphabet (with a small Slavic twist to express the extra sounds) meant it was much easier for Poland to align itself westward. I think the average Pole is much closer culturally to the Western neighbours than to a Ukrainian or Russian (maybe apart from cuisine).
Just like Christianity arrived in Poland by marriage of Mieszko with Czech princess Doubravka/Dobrawa in 10th century, we also adapted Czech alphabet (and thus Latin) from Jan Hus efforts of codifying Czech language. Scholars believe that around same time Polish began to develop as a separate language. And up until the 13th century it was still possible to communicate with southern neighbors without much of issues.
Between 15th and 16th century Polish orthography forms; Stanisław Zaborowski and Jan Kochanowski tried to customize alphabet by introducing letters that would accurately reflected Polish phonology at that time - their alphabets proposals were really long.
Jumping to the Partitions period, where heavy russification aims at eradicating the Polish language and culture. There were attempts of introducing Cyrillic script but occupier's efforts eventually failed - Polish people stood up; literature of these times was full of titles exploring patriotism, love for homeland as a theme.
Linguistic reform of 1936 molds language to what we know today. The communistic period introduced second person plural within the public language, which naturally exists today in Czech and Slovak (vykání). Here it didn't lasted as it was unnatural and politically branded. While Polish language divides into dialects, that time also forms the standard Polish dialect, as post-WW2 migrations blurred the differences.
Today our language is heavily populated with borrowed words and terms from English, which in some case become "naturalized" - hater become hejter.
As I am fond of saying: "The good news about Open Source is that you've got the source code; the bad news about Open Source is that _you've_ got the source code."
That is, you may well get sucked down a rabbit hole in order to accomplish a simple task.
Fun fact: when treated with unicode Normalization Form Canonical Decomposition, 8 out of 9 polish letters (ż,ó,ć,ę,ś,ą,ź,ń) break down into base letter + combining diacritical mark, but ł stays intact. That means you can't use sqlite's unicode61 remove_diacritics tokenizer to normalize polish text for FTS.
I remember discovering that while writing some code for a job interview. The reason for it is simple, even though in many input systems (like the ABC International I use on my Macs) it’s a two-character sequence to enter ł, there is not actually a combining character for that line through the l. I’m not sure, but I think sqlite’s remove_diacritics works the way that I’ve implemented that functionality in some of my own software: convert to NCD then remove combining characters from the string. I would expect that a few other special cases also behave the same way, such as ħ or ø which also will not decompose.
The real issue here is first that browsers don't expose a simple way to check for key combinations and second that developers don't bother building their own. You'll find on any number of sites that an intended key combination can also be invoked with additional modifiers of alt or shift or whatnot. Even here, the code shown only fixes the broader issue on windows; alt+cmd+s still gets blocked.
There should be a proposal for browsers to expose a property on the keydown/up/press event containing a code for the key combination. Something like "CTRL+S", "CTRL+ALT+S", etc. The programmer could then switch over this property rather than having to check key codes and modifiers manually.
I would also propose to any web developers that they build this property themselves in their own code and check against it instead of checking modifiers directly. Not only would it protect against bugs like in the OP, it would also be a lot more convenient to use.
This bug comes from a programmer trying to fix one problem - users press Control S and get a save dialog - by altering some fundamental and bug-prone behaviour.
Imagine the damage programmers could do if they had more options to meddle easily! They have low-level APIs if they need them to hook keys. Best leave it at that.
> Polish is the second most-used Slavic language, right after Russian and just before Ukrainian
This is not exactly right regarding Ukrainian. While it is the official language of Ukraine, in reality... let's say that not all Ukrainian people are actually speaking it.
That's 11.2 million Western Ukrainians, who are overwhelmingly Ukrophone. Even if you completely ignore the rest of the country (which definitely wasn't completely Russophone and is even less now), that's still more than the number of Czech speakers.
Sadly it is not just Medium, but a bunch of other Windows apps too. For example, in Active Presenter, typing one of the letters (I think it is Ó) stops screen recording, which makes the program unusable in many situations - I cannot record myself typing anything in Polish. Other apps similarly assign shortcuts to Alt + Ctrl + letter, somehow overriding the keyboard layout driver.
Many American companies fell into that. Intel, Nvidia, AMD control panels all contained keyboard shortcut keys that interfered with Polish diacritics. Even Google at one point had the exact issue described in this article.
Medium is trying to be little too convenient here. They could just save stuff automatically every few seconds, and that wouldn't require users to press any combination of keys.
In nvidia overlay there is a shortcut Alt+Z, it's pretty annoying because it triggers on both left and right alt so polish users cannot type letter "ż" without opening the overlay or rebinding it.
31 comments
[ 2.1 ms ] story [ 49.5 ms ] threadJust like Christianity arrived in Poland by marriage of Mieszko with Czech princess Doubravka/Dobrawa in 10th century, we also adapted Czech alphabet (and thus Latin) from Jan Hus efforts of codifying Czech language. Scholars believe that around same time Polish began to develop as a separate language. And up until the 13th century it was still possible to communicate with southern neighbors without much of issues.
Between 15th and 16th century Polish orthography forms; Stanisław Zaborowski and Jan Kochanowski tried to customize alphabet by introducing letters that would accurately reflected Polish phonology at that time - their alphabets proposals were really long.
Jumping to the Partitions period, where heavy russification aims at eradicating the Polish language and culture. There were attempts of introducing Cyrillic script but occupier's efforts eventually failed - Polish people stood up; literature of these times was full of titles exploring patriotism, love for homeland as a theme.
Linguistic reform of 1936 molds language to what we know today. The communistic period introduced second person plural within the public language, which naturally exists today in Czech and Slovak (vykání). Here it didn't lasted as it was unnatural and politically branded. While Polish language divides into dialects, that time also forms the standard Polish dialect, as post-WW2 migrations blurred the differences.
Today our language is heavily populated with borrowed words and terms from English, which in some case become "naturalized" - hater become hejter.
That is, you may well get sucked down a rabbit hole in order to accomplish a simple task.
> Instead of blindly and greedily blocking Ctrl S, we could block Ctrl S only if Alt key was not pressed.
Ctrl alt s was the keyboard shortcut for the polish S. Ctrl s was blocked to improve saving. And this also blocked ctrl alt s too.
There should be a proposal for browsers to expose a property on the keydown/up/press event containing a code for the key combination. Something like "CTRL+S", "CTRL+ALT+S", etc. The programmer could then switch over this property rather than having to check key codes and modifiers manually.
I would also propose to any web developers that they build this property themselves in their own code and check against it instead of checking modifiers directly. Not only would it protect against bugs like in the OP, it would also be a lot more convenient to use.
Imagine the damage programmers could do if they had more options to meddle easily! They have low-level APIs if they need them to hook keys. Best leave it at that.
Meanwhile, there is the accesskey attribute in HTML to let you customise shortcut keys: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...
Holy crow what a mess. No wonder I'd never heard of this.
This is not exactly right regarding Ukrainian. While it is the official language of Ukraine, in reality... let's say that not all Ukrainian people are actually speaking it.
It comes bundled with xorg nowadays, you can use:
in xorg.confThe issue wasn’t so much the lack of income it was scarcity of items to purchase.
I don't even think about it. It's autosave without plugin.
Medium is trying to be little too convenient here. They could just save stuff automatically every few seconds, and that wouldn't require users to press any combination of keys.
Nvidia pls fix..