This commit is contained in:
Kovid Goyal 2026-04-12 12:48:45 +05:30
parent 916173dcb3
commit 3d0a34254a
No known key found for this signature in database
GPG key ID: 06BC317B515ACE7C

View file

@ -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