Inkscape

  1. Bug #199656
  2. Comment #1

Comment 1 for bug 199656

Revision history for this message
franti (fhvill) wrote :

Hello, sorry that I could not find your bug report and created a duplicate at https://bugs.launchpad.net/bugs/229359

This bug makes the script unreadable and indeed prevents it from running.

Amazingly I got this answer from sas to my original report at 229359:

<<<<<
It's correct behaviour for <![CDATA[ ... ]]> in the XML editor to change to &lt;![CDATA[ ... ]]&gt; in the file - the XML editor shows plain text, not escaped text, and text that you type into it will be interpreted as plain text, not as escaped text.

Likewise, " changing to &quot; is OK (though unnecessary for element content, as opposed to attribute values).
>>>>>

I am wondering what "normal behaviour" means! I claim that whichever way the script text one types or imports in Inkscape is interpreted, the sole concern should be that it works for the user when one comes out of Inkscape. This indeed is a bug.

If for any reason and for some people the text inside script tags should remain unescaped, that should be an option which can be turned on inside Preferences, escaped text being the default.