Re: Problem: incompatible handling of svg files

[Ethan A M. <merritt@u.washington.edu>]

On Tuesday 17 October 2006 12:21 am, Petr Mikulik wrote:
> > 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 &#

Correct. That is what it does.
 
> Then there should be two kinds of the "escape" option, one yours and one for 
> the previous.

Huh? I don't understand what you mean here.
The "escape" option leaves in place what it was doing previously.
Except that the second version knows enough to escape utf-8
sequences correctly, which the previous version didn't. 

-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742