docs/interop: Change the vnc-ledstate-Pseudo-encoding doc into .rst

The file seems to contain perfectly valid rst syntax already, so
rename it to .rst and wire it up in the index.

Message-Id: <20221213101806[email protected]>
Signed-off-by: Thomas Huth <[email protected]>

diff --git a/docs/interop/index.rst b/docs/interop/index.rst
index b7632acb7ba3792294f81398e82d32f728b259b1..6351ff9ba6e60856281d03452315d8d99a579bd9 100644 (file)
--- a/docs/interop/index.rst
+++ b/docs/interop/index.rst
@@ -23,3 +23,4 @@ are useful for making QEMU interoperate with other software.
    vhost-user-gpu
    vhost-vdpa
    virtio-balloon-stats
+   vnc-ledstate-pseudo-encoding

diff --git a/docs/interop/vnc-ledstate-Pseudo-encoding.txt b/docs/interop/vnc-ledstate-Pseudo-encoding.txt
deleted file mode 100644 (file)
index 0f124f6..0000000
--- a/docs/interop/vnc-ledstate-Pseudo-encoding.txt
+++ /dev/null
@@ -1,50 +0,0 @@
-VNC LED state Pseudo-encoding
-=============================
-
-Introduction
-------------
-
-This document describes the Pseudo-encoding of LED state for RFB which
-is the protocol used in VNC as reference link below:
-
-http://tigervnc.svn.sourceforge.net/viewvc/tigervnc/rfbproto/rfbproto.rst?content-type=text/plain
-
-When accessing a guest by console through VNC, there might be mismatch
-between the lock keys notification LED on the computer running the VNC
-client session and the current status of the lock keys on the guest
-machine.
-
-To solve this problem it attempts to add LED state Pseudo-encoding
-extension to VNC protocol to deal with setting LED state.
-
-Pseudo-encoding
----------------
-
-This Pseudo-encoding requested by client declares to server that it supports
-LED state extensions to the protocol.
-
-The Pseudo-encoding number for LED state defined as:
-
-======= ===============================================================
-Number  Name
-======= ===============================================================
--261    'LED state Pseudo-encoding'
-======= ===============================================================
-
-LED state Pseudo-encoding
---------------------------
-
-The LED state Pseudo-encoding describes the encoding of LED state which
-consists of 3 bits, from left to right each bit represents the Caps, Num,
-and Scroll lock key respectively. '1' indicates that the LED should be
-on and '0' should be off.
-
-Some example encodings for it as following:
-
-======= ===============================================================
-Code    Description
-======= ===============================================================
-100     CapsLock is on, NumLock and ScrollLock are off
-010     NumLock is on, CapsLock and ScrollLock are off
-111     CapsLock, NumLock and ScrollLock are on
-======= ===============================================================

diff --git a/docs/interop/vnc-ledstate-pseudo-encoding.rst b/docs/interop/vnc-ledstate-pseudo-encoding.rst
new file mode 100644 (file)
index 0000000..0f124f6
--- /dev/null
+++ b/docs/interop/vnc-ledstate-pseudo-encoding.rst
@@ -0,0 +1,50 @@
+VNC LED state Pseudo-encoding
+=============================
+
+Introduction
+------------
+
+This document describes the Pseudo-encoding of LED state for RFB which
+is the protocol used in VNC as reference link below:
+
+http://tigervnc.svn.sourceforge.net/viewvc/tigervnc/rfbproto/rfbproto.rst?content-type=text/plain
+
+When accessing a guest by console through VNC, there might be mismatch
+between the lock keys notification LED on the computer running the VNC
+client session and the current status of the lock keys on the guest
+machine.
+
+To solve this problem it attempts to add LED state Pseudo-encoding
+extension to VNC protocol to deal with setting LED state.
+
+Pseudo-encoding
+---------------
+
+This Pseudo-encoding requested by client declares to server that it supports
+LED state extensions to the protocol.
+
+The Pseudo-encoding number for LED state defined as:
+
+======= ===============================================================
+Number  Name
+======= ===============================================================
+-261    'LED state Pseudo-encoding'
+======= ===============================================================
+
+LED state Pseudo-encoding
+--------------------------
+
+The LED state Pseudo-encoding describes the encoding of LED state which
+consists of 3 bits, from left to right each bit represents the Caps, Num,
+and Scroll lock key respectively. '1' indicates that the LED should be
+on and '0' should be off.
+
+Some example encodings for it as following:
+
+======= ===============================================================
+Code    Description
+======= ===============================================================
+100     CapsLock is on, NumLock and ScrollLock are off
+010     NumLock is on, CapsLock and ScrollLock are off
+111     CapsLock, NumLock and ScrollLock are on
+======= ===============================================================