I already managed to implement the above said.
Suggestion:
For the part.xml I think it make sense for the following:
<FileEntry .....>
<Author Realname="" Username="PTadmin">
<Keywords>
<Keyword>word1</Keyword>
<Keyword>word2</Keyword>
</Keywords>
<History Date="2004-11-06" Author="PTadmin" >Official Update 2004-04</History>
<FileEntry>
This means the Author and Keywords attributes for FileEntry will go into elements.
I would eliminate the "[]" brackets from the username as they are not part of the username.
Also the "{}" brackets if they occur.
As we have now a version out we have to care also about versions of this.
We should introduce a new element at start
<Version Number="2" />
If version is not present, then it is version 1
I'll go now and implement the version question and if it is not 1 then part.xml can not be used currently.
Edit:
Just finished LDFind adjustment for versions.
If the version tag is present and the Number is another than 1 then LDFind will not parse the parts.xml file.
Suggestion:
For the part.xml I think it make sense for the following:
<FileEntry .....>
<Author Realname="" Username="PTadmin">
<Keywords>
<Keyword>word1</Keyword>
<Keyword>word2</Keyword>
</Keywords>
<History Date="2004-11-06" Author="PTadmin" >Official Update 2004-04</History>
<FileEntry>
This means the Author and Keywords attributes for FileEntry will go into elements.
I would eliminate the "[]" brackets from the username as they are not part of the username.
Also the "{}" brackets if they occur.
As we have now a version out we have to care also about versions of this.
We should introduce a new element at start
<Version Number="2" />
If version is not present, then it is version 1
I'll go now and implement the version question and if it is not 1 then part.xml can not be used currently.
Edit:
Just finished LDFind adjustment for versions.
If the version tag is present and the Number is another than 1 then LDFind will not parse the parts.xml file.