You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which rolls us back to the tor.css as a workaround, but doesn't apply lower-roman page number style; it's just numbering the frontmatter with decimal-type nums and restarting at main content.
The text was updated successfully, but these errors were encountered:
MacmillanWorkflows
changed the title
picador CSS frontmatter folios not working
[8] picador CSS frontmatter folios not working
Nov 7, 2017
Turns out the issue is with '@page front:left' & '@page front:right' definitions in the core_tor.css.. the picador css tries to override '@page front' definitions but needs to be more specific (address left & right) to override the 'content:normal' rules from above. I fixed this issue with a oneoff again but maybe we should patch this one permanently sooner rather than later.
This is the file that gave me trouble, but in looking at older runs, it looks like it;'s just not working.:
https://www.dropbox.com/s/5w9zfp3yxiit1ts/9781250170583_MNU.docx?dl=0
When this rule is present:
None of the frontmatter gets a folio in this .docx. To revert / nullify this rule I mocked up a one-off css:
Which rolls us back to the tor.css as a workaround, but doesn't apply lower-roman page number style; it's just numbering the frontmatter with decimal-type nums and restarting at main content.
The text was updated successfully, but these errors were encountered: