https://bugs.kde.org/show_bug.cgi?id=477533
Johannes Zarl-Zierl <johan...@zarl-zierl.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
CC| |johan...@zarl-zierl.at
Ever confirmed|0 |1
--- Comment #1 from Johannes Zarl-Zierl <johan...@zarl-zierl.at> ---
The issue here lies with the "compressed" file format using the category name
as an XML attribute:
> <category name="2Review" ...>
> ....
> <image file="..." 2Review="test" ...>
That also means that one can create and use such a category in the
"uncompressed" file format perfectly well and than convert the database to the
"compressed" file format and totally break it.
To fix this on a database level, we need to change the database file format and
break compatibility.
Alternatively, we could just prevent creating such a category - but that seems
like a band-aid solution to me.
Since we are breaking compatibility anyways, I'm contemplating decoupling
between the category name and the XML attribute name to avoid the whole
escaping/unescaping mechanism altogether.
I'll need a few days to think about the which solution will be best to
implement...
--
You are receiving this mail because:
You are watching all bug changes.
