MobileRead Forums - View Single Post

ilovejedd · 05-19-2009, 02:07 PM

Ok, so Windows XP sucks at the whole unicode via command-line thing, but I've noticed that all the command-line conversion utilities support OPF input. My question is, how strict are the command-line utilities with OPF files (particularly html2epub)?

Say, I have:

Code:

<?xml version="1.0"?>
<package version="2.0" xmlns="http://www.idpf.org/2007/opf">
 <metadata xmlns:opf="http://www.idpf.org/2007/opf">
   <title>Title Goes Here</title> 
   <creator>I.M. D’Author</creator>
 </metadata>
 <manifest>
  <item id="story" href="story.xhtml" media-type="application/xhtml+xml" />
 </manifest>
</package>

Will html2epub fix it, divide story.xhtml into chapter/300KB chunks, create the spine/table of contents, etc?

05-19-2009, 02:07 PM	#1
ilovejedd hopeless n00b Posts: 5,110 Karma: 19597086 Join Date: Jan 2009 Location: in the middle of nowhere Device: PW4, PW3, Libra H2O, iPad 10.5, iPad 11, iPad 12.9	html2epub and OPF files Ok, so Windows XP sucks at the whole unicode via command-line thing, but I've noticed that all the command-line conversion utilities support OPF input. My question is, how strict are the command-line utilities with OPF files (particularly html2epub)? Say, I have: Code: <?xml version="1.0"?> <package version="2.0" xmlns="http://www.idpf.org/2007/opf"> <metadata xmlns:opf="http://www.idpf.org/2007/opf"> <title>Title Goes Here</title> <creator>I.M. D’Author</creator> </metadata> <manifest> <item id="story" href="story.xhtml" media-type="application/xhtml+xml" /> </manifest> </package> Will html2epub fix it, divide story.xhtml into chapter/300KB chunks, create the spine/table of contents, etc? Last edited by ilovejedd; 05-19-2009 at 02:10 PM.