ufal / charles-translator-web-frontend

Charles Translator: MT from Charles University
6 stars 7 forks source link

Simulated Cyrillic keyboard #33

Open martinpopel opened 2 years ago

martinpopel commented 2 years ago

Many users may not know how to install Ukrainian keyboard layout on their (or borrowed) device (see e.g. instructions for on-screen keyboard for Windows). Even if the keyboard is installed, the physical keyboard may be missing Cyrillic labels and (not only) pupils may not remember the layout by heart. So we could add an option to simulate a Cyrillic keyboard if the direction is set to uk->cs.

There are at least four possible ways:

  1. standard (ЙЦУКЕН) layout
  2. "phonetic" (ЯВЕРТУ) layout
  3. English transliteration, e.g. duzhe -> дуже
  4. Czech transliteration, e.g. duže -> дуже

Google Translate uses offers options 1, 3 and handwritten recognition. Option 1 comes with a virtual on-screen keyboard (in addition to "re-mapping" the keys on the standard keyboard). Option 3 comes with a clever autocomplete feature (so e.g. even duze -> дуже works). I think option 1 would be enough for the time being (we should test the on-screen keyboard and possibly disable it on mobile devices).

stranak commented 2 years ago

Is this really important? Windows do include a virtual on-screen keyboard, as does MacOS (and probably also KDE and most other wms).

So isn't it more of a question of Help / FAQ and pointing users to the on-screen keyboards they already have?

martinpopel commented 2 years ago

I think the virtual on-screen keyboard offers only the layout(s) installed in the system. So if a user does not know how to install the uk keyboard (as noted in the first sentence of this issue), the OS on-screen keyboard won't help. Note that the issue is not only about showing the on-screen keyboard, but also re-mapping the keys. I guess there is a reason why this feature is included in all the popular online translators.

That said, I agree, it is a lower priority issue (marked as an enhancement, not a bug). Maybe there are volunteers at GitHub willing to help, so we should have a list of suitable issues. Of course, meanwhile we can create/improve Help/FAQ and include links to hints on Windows/MacOS keyboard settings.

stranak commented 2 years ago

Even if the keyboard is installed, the physical keyboard may be missing Cyrillic labels and (not only) pupils may not remember the layout by heart.

Yes, my suggestion only applies to this option, but it is very simple and readily available.

stranak commented 2 years ago

Maybe there are volunteers at GitHub willing to help, so we should have a list of suitable issues. Of course, meanwhile we can create/improve Help/FAQ and include links to hints on Windows/MacOS keyboard settings.

I agree with both points. I am getting worried about the 40+ issues we have now open and solving them is currently on the 2 guys, both of whom cannot give their full attention only to the translation frontend(s).

EbrithilNogare commented 2 years ago

just info for me https://www.npmjs.com/package/kioskboard