Discussion:
[KPhotoAlbum] Duplicate members in member-group in compressed index.xml?
Robert Krawitz
2017-05-20 19:43:04 UTC
Permalink
I notice two instances of "0" as a member in the compressed index.xml
(and 0 isn't a valid index, anyway).

<member category="Keywords" group-name="vacations" members="0,0,119,149,18,183,219,255,283,301,378,385,386,387,388,389,390,391,399,406,425,430,432,440,493,494,554,556,564,571,75,77"/>
--
Robert Krawitz <***@alum.mit.edu>

*** MIT Engineers A Proud Tradition http://mitathletics.com ***
Member of the League for Programming Freedom -- http://ProgFree.org
Project lead for Gutenprint -- http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton
Robert Krawitz
2017-05-20 20:44:08 UTC
Permalink
Post by Robert Krawitz
I notice two instances of "0" as a member in the compressed index.xml
(and 0 isn't a valid index, anyway).
<member category="Keywords" group-name="vacations" members="0,0,119,149,18,183,219,255,283,301,378,385,386,387,388,389,390,391,399,406,425,430,432,440,493,494,554,556,564,571,75,77"/>
So I have a suspicion I know what happened: I may have edited the
index.xml file manually and not changed all occurrences of certain
keywords. The uncompressed format continues to work without
complaint, but when I save it in compressed format, the keyword goes
away since the numerical index is bogus.
--
Robert Krawitz <***@alum.mit.edu>

*** MIT Engineers A Proud Tradition http://mitathletics.com ***
Member of the League for Programming Freedom -- http://ProgFree.org
Project lead for Gutenprint -- http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton
Johannes Zarl-Zierl
2017-05-20 21:30:26 UTC
Permalink
Post by Robert Krawitz
Post by Robert Krawitz
I notice two instances of "0" as a member in the compressed index.xml
(and 0 isn't a valid index, anyway).
<member category="Keywords" group-name="vacations"
members="0,0,119,149,18,183,219,255,283,301,378,385,386,387,388,3
89,390,391,399,406,425,430,432,440,493,494,554,556,564,571,75,77"/
So I have a suspicion I know what happened: I may have edited the
index.xml file manually and not changed all occurrences of certain
keywords. The uncompressed format continues to work without
complaint, but when I save it in compressed format, the keyword goes
away since the numerical index is bogus.
Sounds like a valid explanation. If you introduce inconsistencies into
index.xml, all bets are off.

Loading...