@@ -183,6 +183,22 @@ \subsection{Kitty image protocol}
183183as well as client side, yet allowing future extensions to this protocol
184184without breaking compatibility to existing implementations.
185185
186+ \subsection {DomTerm's inline image support }
187+
188+ \begin {itemize }
189+ \item DomTerm's image support appeared in 2016.
190+ \item No explicit image protocol but a "insert HTML" -protocol that does support images.
191+ \item Specification is in the source code repository's \texttt {README.md } file.
192+ \end {itemize }
193+
194+ The typical way to insert an image is to insert an HTML <img> element,
195+ with the src attribute using a data: URL scheme,
196+ with the actual data inline as base64.
197+
198+ Any image format supported by the underlying browser engine is allowed.
199+
200+ The \texttt {<img> } element can contain attributes such as width, height, alt
201+ and options to add scrollbars.
186202% }}}
187203\section {Requirements } % {{{
188204
@@ -702,7 +718,7 @@ \section{References} % {{{
702718 \item \label {ref:twg-gip }Good Image Protocol, \url {https://gitlab.freedesktop.org/terminal-wg/specifications/-/issues/26}
703719 \item \label {ref:image-sixel }Sixel Image Protocol, \url {https://vt100.net/docs/vt3xx-gp/chapter14.html}
704720 \item \label {ref:image-item2 }iTerm2's image protocol, \url {https://iterm2.com/documentation-images.html}
705- \item \label {ref:image-terminology }Terminology's image protocol, \url {https://www.enlightenment.org/docs/apps/ terminology.md} \todo {Terminology image protocol spec not found. ;-( }
721+ \item \label {ref:image-terminology }Terminology's image protocol, \url {https://github.com/borisfaure/ terminology/blob/master/README .md#available-commands }
706722 \item \label {ref:image-kitty }Kitty's image protocol, \url {https://sw.kovidgoyal.net/kitty/graphics-protocol.html}
707723\end {enumerate }
708724% }}}
0 commit comments