Quote:
Originally Posted by pdurrant
Oh, of course! Perhaps we could just store all metadata as a list, rather than a single object in the map.
Anyone better than me at Python like to give it a go?
|
I've started to implement storing metadata as lists, and while it's not pretty it seems to work, though I haven't yet tested a file which actually contains duplicate metadata tags.
But I've noticed that several tags are currently not handled by mobiunpack (e.g. 202-209, 300).
I'm would like to get some input about how mobiunpack should handle them. I doubt that mobigen/kindlegen supports all these tags (if any), but there are already tags that will be exported to the opf file despite they are ignored by mobigen/kindlegen (e.g. the ASIN).
Are there other tools which actually support these tags and use the values or are they just for information?
In the latter case I would like to mark them as such (for example by putting them into a comment section) to make clear that their value won't affect the generated mobi.
Another solution would be to define a new list of ignored tags, so it's clear that we are aware of those tags but deliberately don't include them in the opf file.
Ciao,
Steffen