[KevinH]

Hi,

My vote goes to separate writeOPF routines with as many common functions and methods pulled out to be shared to make it easier to maintain the pair.

A command line switch to enable epub3 features sounds good as well.

I would stick with what we have now for epub2, and going with official epub3.

If the need arises we can add a strict flag to the command line to rule out any hybrid approach.

My 2 cents ...

KevinH

Originally Posted by tkeo

Hi,



I have been thinking this matter.

I briefly summarize differences from epub2 to eupb3 related closely to KindleUnack. Please correct if it is wrong.

• In opf:
  • package version.
  • metadata tag and allowed attributes in its component.
  • allowed attributes in item tag in manifest.
  • allowed attributes in spine tag and item tag in the spine.
  • tours tag is removed.
• toc.ncx to toc in nav.xhtml.
• guide tag in opf is move to landmark in nav.xhtml.
  
• javascript and other contents support.

So, most chages to need is 'mobi_opf.py' and 'kindleunpack.py', and addition of nav.xhtml creation parser.
I think addition of parameter to indicate taget epub version to functions are necessary. And throgh consideration, questions are come into my mind.

How many target versions are necessary?

strict epub2, epub2+alpha(current version), epub3?

or

epub2+alpha(current version) and epub3 is enough?

Regarding to modify 'mobi_opf.py', which is better,

switching internal process in WriteOPF()

or

separeting WriteOPF() for each version?
The switching internal process is possible but it will decrease readability and may cause bugs to all versions...

I would like to hear opinions.
Thanks,