Hi tkeo,
Quote:
Originally Posted by tkeo
|
I would remove all of those id= since we would not have a complete set and therefore they can't be used for actual references. The same is true for the "refines" use of id=, they can't be decoded without guessing what the id properties would have been on the title and creator and etc. Since those are lost, we can't rebuild the refines either.
That is why I store ALL of the extra metadata from the RESC inside a comment. So no need to strip out the original coverpage info as well.
Quote:
Besides, it makes simpler to generate itemref tags in mobi_opf.py.
So, I prefer to go with B).
|
I am fine with that but as I said incomplete content.opf pieces with incomplete id= make using those ids in general impossible.
Quote:
As for properties, it is allowed to have more than two values, ex.
Code:
<itemref idref="titlepage" properties="page-spread-right rendition:layout-pre-paginated"/>
This is just note. We can store it as a string in a dict.
I have modified to change from spine_pageprops and spine_linear to spine_pageattributes, prepending 'x_' to cover_name and id attribute.
|
It was parsed properly and stored as a string anyway. But I understand your motivations and I am okay with that approach, although I would rather we strip out any id= since they are unusable as I explained above.
Quote:
|
A little bit irregular way though, I have also modified to insert cover page in the case RESC is not exist nor spine is not in the RESC.
|
No, I don't like that approach as it abuses the filleinfo key field. I would rather simply hard code the linear="no" for this case inside the opf itself, and not abuse the key field in filleinfo in that way. Since we are creating the coverpage we can always mark it as auxiliary (the "no") as it truly is not needed to be shown first in the flow.
Thanks,
KevinH