Updated Home (markdown)

Home.md

@@ -258,11 +258,42 @@ You can use either X- or Wayland-native terminal emulator with little difference
 
 [termite](https://github.com/Thestinger/termite) (which is Wayland-native) is a popular recommendation, along with other VTE-based terminals like GNOME Terminal. X-based `urxvt` is another popular option. [Kitty](https://sw.kovidgoyal.net/kitty/) will use Wayland without additional configuration.
 
-
 ### Why am I getting `Error on line XX […] Unknown key`?
 
 In your config, you should replace at line XX `bindsym` by `bindcode`.
 
+### Locale-specific configuration tricks
+
+#### Workspace switching on the French layout
+
+Because French number keys only produce numbers when Shift is pressed (or Caps Lock is active), you'll need to setup key bindings with the various special characters under the numbers (&, é, ", etc):
+
+```
+bindsym $mod+ampersand workspace 1
+bindsym $mod+eacute workspace 2
+bindsym $mod+quotedbl workspace 3
+bindsym $mod+apostrophe workspace 4
+bindsym $mod+parenleft workspace 5
+bindsym $mod+minus workspace 6
+bindsym $mod+egrave workspace 7
+bindsym $mod+underscore workspace 8
+bindsym $mod+ccedilla workspace 9
+bindsym $mod+agrave workspace 10
+```
+
+#### Key bindings on a dual US/Russian layout
+
+If you have configured your keyboard with a US and a Russian layout (`input * xkb_layout us,ru`), your bindings using Latin script letters won't work when the Russian keyboard is active (for instance, `$mod+f` won't work, because you can't produce the letter `f` with the Russian layout).
+
+To make key bindings work regardless of the currently active layout, you can use `bindsym --to-code`:
+
+```
+bindsym --to-code {
+    $mod+b splith
+    $mod+v splitv
+}
+```
+
 ## Troubleshooting
 
 ### How do I report issues?