On Sat, Apr 22, 2023 at 3:26 PM Thomas Passin <tbp100...@gmail.com> wrote:
> I've made a little progress. That unicode character - 0xfffc - is only > a marker and does not carry any information about the image. Iirc, the lack of identifying data with the 0xfffc character was why I abandoned this project years ago. It would be natural to allow body text to contain more than one image. Ordinary editing operations could change the order in which those images appear (or, as you say, delete images). You're correct, Leo could use uAs to associate images with 0xfffc characters *initially*, but I see no good (easy) way of *maintaining *those associations after *all* of Leo's editing operations. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3Xs7J0T8dm4PKsMpDNKe2_O-VfJ2sRpzQsm9Wo2gLTzw%40mail.gmail.com.
