View Single Post
Old 08-27-2011, 02:23 PM   #32
charleski
Wizard
charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.
 
Posts: 1,196
Karma: 1281258
Join Date: Sep 2009
Device: PRS-505
Quote:
Originally Posted by st_albert View Post
But there's a difference between 0.3.4 and 0.4 in that 0.3.4 will add the xml namespace references for opf and dc to the <metadata> tag if they aren't already there. Thus,

Code:
<metadata>
becomes
Code:
<metadata xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:opf="http://www.idpf.org/2007/opf">
version 0.4.0+ does not do this.
It does if you're creating a new ePub and importing the html.

When editing ePubs, though, the 0.4 behaviour was to try to avoid changing the opf unless it needs to, because that's what people asked for. When you add elements that require a particular prefix, it adds the prefix where it's needed. This is really more of an issue with assumptions made in the workflow, but I see John has changed it back to the old method.
charleski is offline   Reply With Quote