Quote:
Originally Posted by charleski
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.
|
I suspected that might be the case, and I have a great deal of sympathy for that approach (i.e. no -- or few -- silent modifications without warning). In my case, since I'm in there editing the opf already, I wouldn't be unhappy with either approach. Once I figured out what was going on, that is.
That said, I don't see any harm in making sure the xmlns references are there, even if possibly unneeded; and putting them in the <metadata> tag seems to me to be the most reasonable place in general.
In any event, thank you and John for your hard work on Sigil!
