Skip to content

Conversation

@MichaelFenwick
Copy link

After writing an epub, the manifest would end up with a #nav item which lacked a properties attribute. That is, the manifest item

<item href="nav.xhtml" id="nav" media-type="application/xhtml+xml" properties="nav"/>

would be written as

<item id="nav" href="nav.xhtml" media-type="application/xhtml+xml"/>

This is problematic as the manifest reader uses that attribute to identify the nav item, preventing a written book from being read again (an exception would be thrown if reading was attempted). This change ensures that the properties attribute is written to each manifest element if it has a value, resolving this problem.

After writing an epub, the manifest would end up with a `#nav` item which lacked a `properties` attribute. That is, the manifest item

`<item href="nav.xhtml" id="nav" media-type="application/xhtml+xml" properties="nav"/>`

would be written as

`<item id="nav" href="nav.xhtml" media-type="application/xhtml+xml"/>`

This is problematic as the manifest reader uses that attribute to identify the nav item, preventing a written book from being read again (an exception would be thrown if reading was attempted). This change ensures that the `properties` attribute is written to each manifest element if it has a value, resolving this problem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant