GoogleCodeExporter
commented
8 years ago Thanks for including the AlbumData.xml file - that makes debugging this very
easy. I took the liberty of deleting the file after looking at it, because it
contains some personal data.
What is happening here (and something similar has happened to another Phoshare
user before) is that iPhoto actually writes invalid XML. In your case, it is
for the image
2003/Clément & Pierre-Antoine vont à Ibiza !/096.jpg
and about 6 others. The line with the problem looks like this:
<key>ImageType</key><string></string>
What you cannot see is four invisible bytes with the value 0 between <string>
and </string>. It should say JPEG. Phoshare doesn't need that field, but the 0
bytes make this invalid XML, and reading and parsing of the file contents stops
at that point on the XML level. I've attached a file that shows all the places
where this occurs. Maybe you can see a pattern, e.g. do these images have
something in common.
There is no easy way to work around this in Phoshare. When I came across this
with another user before, it was about unprintable characters in event
descriptions. The user was able to fix it by editing the descriptions to erase
the bad characters. In your case, the bad characters are in data owned by
iPhoto. Short of deleting those images from your library, there is nothing you
can do on your end.
I will check if it is possible to add a pre-processing stage for the
AlbumData.xml file into Phoshare that simply removes any unprintable
characters. Stay tuned.
Original comment by tsporkert on 22 Nov 2010 at 6:18
- Changed state: Accepted
Attachments:
Original issue reported on code.google.com by
clement.jouberton 22 Nov 2010 at 11:26