| Summary: | Accents not send to device | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Angel Docampo <docampo.angel> |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | bugs-kde, cmolina11, dev, ilikefoss, laborim, nicolas.fella, pehteimoso-kdebugs, simon |
| Priority: | NOR | ||
| Version First Reported In: | 23.08.5 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Angel Docampo
2018-12-11 20:14:05 UTC
I must say, but, I'm on version 1.10 (beta) on android while on 1.3.3 on desktop, if that matters. I can reproduce this on English (US) Fedora 27 ~v1.3.3 and English (US) Android 9 ~v1.10 I came here to report this same bug. I'm using an English keyboard, US international with dead keys. Operating System: Debian GNU/Linux KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.54.0 Kernel Version: 4.19.0-1-amd64 OS Type: 64-bit I've come to report this bug. KDE Connect Version: 1.3.3 Operating System: Linux Mint 19.1 KDE Plasma Version: 5.12.7 Qt Version: 5.9.5 KDE Frameworks Version: 5.44.0 Kernel Version: 4.15.0-50-generic OS Type: 64-bit Today I switched keyboard layouts, from "English intl, with AltGr dead keys" to "English US alt intl". For typing an accented character, the former requires pressing the ' character and then the letter: 'a brings á. This does not work with KDEConnect remote keyboard, nothing appears on the remote device. For writing non-English characters, the later keyboard layout uses the Compose key (I have mine assigned to right-side Ctrl key), so <Compose>a brings á. This works with KDEConnect, the accented character appears on the remote device. If, instead of typing the characters, they are pasted on KDEConnect's edit box, same happens: international characters do no appear on the remote device if the "dead keys" layout is active, but they do appear when the non-dead keys layout is active. Correction: the keyboard layout that uses the Compose key (and works with KDEConnect) is "English (intl., with AltGr dead keys)".
So if the character requires two separate keys ('a -> á), it doesn't work. But if the character is generated by a key plus a modifier (<Compose>a) it works.
I confirm this bug still exists. When I type a character with accent it shows in the remote keyboard field on the desktop instead of showing on the device. I am using Debian testing, KDE 5.27.11, Keyboard language PT I confirm this bug is still present. Currently on linux KDE connect version 25.08.3 Android app version 1.34.4 Operating System: KDE neon User Edition Kernel: Linux 6.14.0-35-generic Architecture: x86-64 DE: Plasma 6.5.2 When using Compose send, all special characters (like, accentuated vowels) are not typed in the destination text field, instead showing incomplete words (camión shows as camin) Also, random accents show elsewhere in the text box, AFTER the initial phrase has been received (´ mispositioned 2-3 paragraphs later), as a sign of a really late reception or processing. Of note, android keyboard (in this case, GBoard) and KDE ibus locale and language are correctly configured and match (es-es UTF-8). This is probably related to the way that KDE connect handles keyboard events inputs. It would be desirable, however, since Compose send is being used, that the function would rely on the clipboard pasting functionality instead, since this does not display the same problem / behaviour. When copying accentuated characters via clipboard, they get pasted without any issues. |