-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the rules for parsing subjects #125
Conversation
This should be reviewed by @JayPanoz since he wrote the initial document. |
Thanks for the improvements JayPanoz. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, fine-tuned the “case of conflict” paragraph as it makes the logic for the mapping tables more explicit, and more feature-proof – on top of covering cases we might have forgotten.
Also removed <dc:publisher>
from this paragraph for EPUB conformance.
I think we’ll then be good to go. Thanks for the PR!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Thanks for the improvements!
Co-Authored-By: Jiminy Panoz <[email protected]>
Co-Authored-By: Jiminy Panoz <[email protected]>
Co-Authored-By: Jiminy Panoz <[email protected]>
Co-Authored-By: Jiminy Panoz <[email protected]>
Co-Authored-By: Jiminy Panoz <[email protected]>
Close readium#126 Co-Authored-By: Jiminy Panoz <[email protected]>
…n role is not applicable
I guess this PR + #135 can be merged now. Next step for these EPUB parsing docs will be, as discussed a month ago during the engineering call, re-organising the EPUB doc a little bit based on nav doc (landmarks), opf, etc. |
I'll merge it this Friday, unless someone vetoes it first. |
sortAs
,code
andscheme
propertiesmeta
elementFix #111.