Bug 402019 - Accents not send to device
Summary: Accents not send to device
Status: CONFIRMED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 1.10
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-11 20:14 UTC by Angel Docampo
Modified: 2020-12-07 02:38 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angel Docampo 2018-12-11 20:14:05 UTC
SUMMARY
KDEConnect's remote keyboard (computer --> mobile device) doesn't seem to send those characters with accent (i.e.: á, é..), so if you send for example the word "clásico", on the device will appear "clsico", omitting the character completely.

STEPS TO REPRODUCE
1.  Configure plasmoid and device to send keystrokes to the mobile device
2.  Open some app with a text field on mobile device, select "KDE Connect Remote Keyboard"
3.  Open plasmoid on Plasma desktop, and enter some text on the text field, something with an accent. Send the text

OBSERVED RESULT
The text sent will appear without the accentuated character 

EXPECTED RESULT
The text sent should appear as written on plasmoid

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux 4.19.4
KDE Plasma Version:  5.14.4
KDE Frameworks Version:  5.52.0
Qt Version:  5.11.2

ADDITIONAL INFORMATION
Comment 1 Angel Docampo 2018-12-11 20:21:56 UTC
I must say, but, I'm on version 1.10 (beta) on android while on 1.3.3 on desktop, if that matters.
Comment 2 Simon Redman 2018-12-12 00:05:39 UTC
I can reproduce this on English (US) Fedora 27 ~v1.3.3 and English (US) Android 9 ~v1.10
Comment 3 Oscar Fuentes 2019-01-29 23:14:48 UTC
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
Comment 4 Flaviano Matos 2019-05-25 18:56:14 UTC
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
Comment 5 Oscar Fuentes 2020-12-07 02:26:43 UTC
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.
Comment 6 Oscar Fuentes 2020-12-07 02:38:10 UTC
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.