Missa Version names (new try) & ePUB conformity with macOS #4099
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
... now rendering on macOS as well
FAJ-Munich
force-pushed
the
display-sep-626
branch
from
20487e9
to
0e87453
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
horastoDivinumOfficiumfolderScriptFuncfunctionalities in a separate filehorasscripts.plEmissa.pl-- ePUBs generated on macOS finally render properlyhorasandmissaversion names, safeguarding the legacy ones inRunTimeOptions.pmand adjustingepubgen2.shaccordingly to avoid re-occurrence of issue Error in epubgen2 #3937(@rl1234567890 please let me know, if you are running into an issue like in July with the adjusted epubgen2. It does work on macOS finally but who knows what happens on different architecture given that iBook has been super picky regarding the xhtml conformity as mentioned above.)