[yokos]

Yeah, I found this out, too. No description.
I have written here "working" before watching result on iLiad, no good idea.

Bert, does your new java program convert the text input to UTF-8 compliant encoding? V1.1 didn't do this. We discussed this UTF-8 thing in my older manifest thread.

[EDIT] I checked version 1.2
UTF-8 bug is still there. Your java program doesn't check whether text input is compliant to UTF-8!
Non-compliant characters are written to manifest.xml. -> Contentlister can't handle manifest.xml.
See below code, "äöü" isn't correct UTF-8 encoding.

<?xml version="1.0" encoding="UTF-8"?>
<package>
    <metadata>
        <dc-metadata>
            <Title>Title</Title>
            <Description>German Umlaute äöü</Description>
            <Date>2007-04-13T10:29:55</Date>
        </dc-metadata>
        <y-metadata>
            <image>Der Spiegel 11 2007.png</image>
            <startpage>Der Spiegel 11 2007.pdf</startpage>
        </y-metadata>
    </metadata>
</package>

We solved this by changing the first line of manifest to

<?xml version="1.0" encoding="iso-8859-1"?>

iLiad screenshot shows utf-8 bug [last entry] [v1.1].