Re: SVG hack for display engine

[Eli Zaretskii]

> From: Anand Tamariya <atamariya@gmail.com>
> Date: Mon, 15 Nov 2021 18:57:20 +0530
> Cc: Emacs Devel <emacs-devel@gnu.org>
> 
> In this hack, the elisp code navigates from (window-start) to (window-end) 
> reading a line of text from the
> associated buffer and displays the same in SVG. I've used (read-event) and 
> (lookup-key) to allow for key
> translations for navigation commands. Hopefully with a tighter integration, 
> all of this will not be required.

So you use the results of the display engine to display the same stuff
differently, is that right?

If so, I'm not sure I understand how to do it "properly".  The Emacs
display engine performs the layout calculations (which determine, for
example, where each screen line ends and the next one begins, or what
stuff fits into a window) by examining each character of buffer text
in turn.  Without this examination, how can we know how to display the
text as SVG?  And if we use the current code to produce this
information, then what did we gain?

I'm probably missing something.