Re: Problem: incompatible handling of svg files

[Petr M. <mi...@ph...>]

> Both add a new terminal option
> 	set term svg {raw|escaped}
>
> Variant 1 treats all encodings the same: if the "escaped" option
> is selected, then non-ascii character are replaced one byte at a
> time by the corresponding sequence &#xNN;

I would expect "raw" writes raw 8bit chars or UTF-8 chars, without any 
textual conversion to &#

Thus it is easy to "recode", "cstocs" etc to change the encoding and freely 
edit the text.

Then there should be two kinds of the "escape" option, one yours and one for 
the previous.

---
PM