summaryrefslogtreecommitdiffstats
path: root/xrdp/xrdp_keyboard.ini
Commit message (Collapse)AuthorAgeFilesLines
* correct latam keylayout valueKoichiro IWAO2018-11-071-1/+1
|
* capitilize hex keylayout valueKoichiro IWAO2018-11-011-1/+1
|
* add Spanish (Latin Amarican) keyboardKoichiro IWAO2018-11-011-0/+3
| | | | Closes #1237.
* Update xrdp_keyboard.ini fbourqui2018-03-051-0/+3
| | | Add the missing Swiss French rdp_layout_ definitions, ch(fr) in X11
* Update xrdp_keyboard.inirkantos2017-12-141-0/+3
| | | Add the missing? Finnish rdp_layout_ definitions. Makes my install now work with Finnish keyboard layout. (same as Swedish)
* Add dvorak keyboard layoutSoedarsono2017-11-011-0/+3
|
* add Belgian keyboardKoichiro IWAO2017-09-011-0/+3
|
* add Spanish keylayoutKoichiro IWAO2017-06-171-0/+3
|
* sort xrdp_keyboard.iniKoichiro IWAO2017-06-091-7/+7
|
* Fix UK/GB keyboard layoutBen Cohen2017-06-081-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The UK/GB keyboard doesn't work properly connecting to xrdp with xorgxrdp. It does work when connecting to xrdp with x11vnc, however. This is because the layout is not declared in xrdp_keyboard.ini. It needs to be called "gb" not "uk". (There are other layouts that have km-nnnn.ini files that aren't declared in xrdp_keyboard.ini, so they might have the same bug, but I haven't tested that. This is analagous to the commits for the "ch" and "pl" layouts.) Test case: 1. Use a PC with the UK/GB keyboard layout. 2. Create /etc/xrdp/startwm.sh as follows: #!/bin/sh export LANG=en_GB.UTF-8 export MDM_LANG=en_GB.UTF-8 export XTERM_LOCALE=en_GB.UTF-8 xterm exit 0 3. Connect using rdesktop to localhost (from a session where the same environment variables are defined). 4. Test layout-specific keys such as: \ (backslash) | (bar) # (numbersign) ~ (asciitilde) £ (sterling: Shift-3) € (EuroSign: AltGr-4) These keys should produce the appropriate symbol but they don't. With the change in this commit the keys produce the correct symbol.
* Workaround for a regression of JP keyboard detection #663Koichiro IWAO2017-02-161-0/+3
| | | | | | | | | | | | | caused by 9c31bd5. This is not a complete fix but just a workaround because keylayout value of Japanese keyboard can be other than these 4 values. This workaround still doesn't cover all JP keyboards. - 0x00000411 - 0xe0010411 - 0xe0200411 - 0xe0210411 Looking for `0411` in lower 16 bits is enough to detect JP keyboards.
* Remove trailing whitespacePavel Roskin2017-02-081-1/+1
|
* Sort alphabeticallyWestporch2016-12-141-3/+3
|
* Add 'rdp_layout_kr=kr'Westporch2016-12-141-0/+3
|
* unify Japanese keymap in xrdp_keyboard.iniKoichiro IWAO2016-12-021-9/+0
|
* config: use semicolon to comment out descriptions in config filesKoichiro IWAO2016-11-161-50/+50
| | | | | | | | and use number sign to comment out actual configurations. For example: ; if set to true, enables foobar #foobar=true
* Update xrdp_keyboard.iniAkira Taniguchi2016-06-291-1/+1
|
* Fix typosPavel Roskin2016-02-131-2/+2
|
* finish for supporting swiss german keyboardThomas Spalinger2015-04-191-0/+3
|
* xrdp_keyboard.ini: Fix jp keyboard modelAkira Taniguchi2014-12-291-0/+1
|
* Add Japanese keymap codes in xrdp_keyboard.iniKoichiro IWAO2014-12-111-0/+9
|
* Install and enable 0415/pl keymapMichał Górny2014-10-271-0/+3
|
* xrdp: added xrdp_keyboard.iniJay Sorg2014-07-311-0/+105
generated by cgit v1.2.1 (git 2.18.0) at 2025-01-03 11:03:36 +0000