From a09c1f871c1cf5ea05014fa9879cfa9784ff04cd Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Sat, 29 Jul 2023 12:26:24 +0800
Subject: [PATCH] Updated FAQ (markdown)
---
FAQ.md | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/FAQ.md b/FAQ.md
index ea21133..6e13e6f 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -200,19 +200,33 @@ https://www.reddit.com/r/rustdesk/comments/14y6u8c/looking_into_rustdesk_but_hav
# Keyboard translation modes
-- Map 1:1
+
+
+
+- Map mode
With "Map 1:1", all keys are mapped from the local to the remote keyboard based on their position. For example, the key "q" on a local QWERTY keyboard will transmit an "a" character if connected to a remote device with an AZERTY keyboard.
This mode is not recommended for office work but it can be useful if the remote device uses specialty software to map macros to specific keys.
-- Translate
+- Translate mode
When "Translate" is selected, all keys will be transmitted to the remote endpoint as if the local keyboard layout is active on the remote device.
However, this layout mode may cause problems with certain programs such as video games as they use scan code to process the key presses.
-- Legacy
+- Legacy mode
This mode is for compatibility with RustDesk <= 1.1.9.
+
+# Force relay
+
+Some guys have the connection problem when you use the desktop/mobile client, but not with web client. That's because the web client always use relay for connection. You can add the suffix '/r' to the remote ID.
+
+
+
+or
+
+
+