MobileRead Forums - View Single Post

drMerry · 10-01-2011, 11:21 AM

Kiwidude,

Seems this project is on a high (forgotten?) shelf at the moment. At the other hand, included functions seem to work just fine, so why not adding it to the downloadable plugins?

I've got 2 new function requests.
A lot of my books seemed duplicates to me, after applying all fixes and do all quality checks, some just where not marked as duplicates using the duplicate checker or an external duplicate file finder.

Then I compared the files using winmerge. This resulted in 4 types of differences, 3 of which could be easily fixed by an extension of this plugin.

Type 1: File-structure.
While comparing the files, all internal files where marked equal, the only difference was the internal structure. Flat vs folders. It would be nice to change this structure without having to convert the complete file (causing other changes to be executed as well).

Type 2: comment.
A very bad one. The files where compete equal, the only difference was based on 2 lines commented out in my opf file!!! While comments in the opf are not used (in html it is possible e.g. javascript parts), It would be nice to have the option to strip html comment out of the opf and toc files.

Type 3: extra line.
Another very ugly one. Files where equal excluding one empty line at the end of my mimetype file. (Based on the specs of 2.01 this is even forbidden!)
While empty lines are not shown in html and not used in opf, I'd suggest to add an option to remove empty lines or lines that only contain white-characters \s (space, tab, \n, \r, other non-visible characters)

Type 4: metadata in opf
The last difference I found was the metadata in the opf-file. E.g. lang UND vs EN or comments versus no comments (about the book). And sometimes only a difference in sigil-version.
This last one is a task that is not easy to implement. While you're able to update the file, it is not easy to update the comment based on metadata of another file.

If it would be possible to implement function 1 2 and 3, I'd be very happy.

Yet another request is to split the metadata-update function.
I'd like to update my epub-files, but I always crop my covers for calibre. So if I update my epub, I will always change my cover in a cover with less quality. Splitting this function would make it possible to update the metadata without first having to remove the cover and later on extract the cover again.

10-01-2011, 11:21 AM	#191
drMerry Addict Posts: 293 Karma: 21022 Join Date: Mar 2011 Location: NL Device: Sony PRS-650	Kiwidude, Seems this project is on a high (forgotten?) shelf at the moment. At the other hand, included functions seem to work just fine, so why not adding it to the downloadable plugins? I've got 2 new function requests. A lot of my books seemed duplicates to me, after applying all fixes and do all quality checks, some just where not marked as duplicates using the duplicate checker or an external duplicate file finder. Then I compared the files using winmerge. This resulted in 4 types of differences, 3 of which could be easily fixed by an extension of this plugin. Type 1: File-structure. While comparing the files, all internal files where marked equal, the only difference was the internal structure. Flat vs folders. It would be nice to change this structure without having to convert the complete file (causing other changes to be executed as well). Type 2: comment. A very bad one. The files where compete equal, the only difference was based on 2 lines commented out in my opf file!!! While comments in the opf are not used (in html it is possible e.g. javascript parts), It would be nice to have the option to strip html comment out of the opf and toc files. Type 3: extra line. Another very ugly one. Files where equal excluding one empty line at the end of my mimetype file. (Based on the specs of 2.01 this is even forbidden!) While empty lines are not shown in html and not used in opf, I'd suggest to add an option to remove empty lines or lines that only contain white-characters \s (space, tab, \n, \r, other non-visible characters) Type 4: metadata in opf The last difference I found was the metadata in the opf-file. E.g. lang UND vs EN or comments versus no comments (about the book). And sometimes only a difference in sigil-version. This last one is a task that is not easy to implement. While you're able to update the file, it is not easy to update the comment based on metadata of another file. If it would be possible to implement function 1 2 and 3, I'd be very happy. Yet another request is to split the metadata-update function. I'd like to update my epub-files, but I always crop my covers for calibre. So if I update my epub, I will always change my cover in a cover with less quality. Splitting this function would make it possible to update the metadata without first having to remove the cover and later on extract the cover again.