From 1384ab99d287d0dadd6c955895f1e82bd12ad946 Mon Sep 17 00:00:00 2001
From: Andri Yngvason <andri@yngvason.is>
Date: Sat, 28 Mar 2020 16:58:13 +0000
Subject: [PATCH] FAQ: Answer some questions

---
 FAQ.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/FAQ.md b/FAQ.md
index 9063ca2..20182cf 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -16,3 +16,27 @@ bindsym $mod+Pause mode passthrough
 ```
 This makes it so that when you press $mod+Pause, all keybindings, except the one
 to switch back, are disabled.
+
+**Q: Wayvnc changes the Sway's keyboard layout. Can this be fixed?**
+
+A: This happens because of a bug in how the virtual keyboard protocol interacts
+with a feature in sway called smart keyboard grouping. This can be remedied by
+either putting wayvnc on a separate seat or turning off smart keyboard grouping
+in sway.
+
+Putting wayvnc in its own seat is done like this:
+```
+swaymsg seat wayvnc fallback false # create a new seat
+wayvnc --seat=wayvnc
+```
+
+Smart keyboard grouping can be turned off like this:
+```
+swaymsg seat seat0 keyboard_grouping none
+```
+
+**Q: Not all symbols show up when I'm typing. What can I do to fix this?**
+
+A: Try setting the keyboard layout in wayvnc to the one that most closely
+matches the keyboard layout that you're using on the client side. An exact
+layout isn't needed, just one that has all the symbols that you use.