From 3d0a34254ae502cf72b3814c9cec69cbff1c5dd9 Mon Sep 17 00:00:00 2001 From: Kovid Goyal Date: Sun, 12 Apr 2026 12:48:45 +0530 Subject: [PATCH] ... --- docs/dnd-protocol.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/dnd-protocol.rst b/docs/dnd-protocol.rst index 793c826f1..6d44c8d63 100644 --- a/docs/dnd-protocol.rst +++ b/docs/dnd-protocol.rst @@ -293,7 +293,7 @@ the ``t=o`` key indicating the offer if the data is available. To associate one or more images with the drag operation, the terminal program must transmit the data for the image with the ``idx`` value above being a negative number starting with ``-1`` for the first image and so on. Clients -**must** transmit all images consecutively in order, starting with the frist, +**must** transmit all images consecutively in order, starting with the first, then the second and so on. When transmitting images, the image data format is specified using the ``y`` key. A value of ``y=24`` mean 24bit RGB data and ``y=32`` means 32bit RGBA data. Colors in the RGB/A data must be in the sRGB @@ -301,7 +301,7 @@ color space. Using ``y=100`` means the data is a PNG image. Additionally, the ``X`` and ``Y`` keys must be used to specify the width and height of the image data in pixels. If the size of the transmitted data does not match the image dimensions the terminal must replay with ``t=E ; EINVAL``. Terminals are free -to impose a limit on the amount of image data, too avoid Denial-of-service +to impose a limit on the amount of image data, to avoid Denial-of-service attacks. If the image data is too much or the image is too large they must reply with ``t=E ; EFBIG`` and abort the drag. By default, the drag will be started using the first image, if any. During the drag, the terminal program