Epubs built by PreText yields errors when submitted to Google Books
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css
- Domain
- build-system
Research direction
Start by building an EPUB and inspecting the generated EPUB/css/epub.css around lines 1004-1007 and 1379-1385, where Google Books rejects .code-display, .autopermalink, and a. Trace those rules back to the XSLT/CSS templates that emit the EPUB stylesheet, then reproduce with an EPUB build and compare epubcheck output against Google Books' parser. Done means the generated CSS no longer contains the rejected constructs and Google Books accepts the EPUB.
Written by the indexing model from the issue text.
Description
Despite the build to epub yielding 0 errors, and the output epub passing epubcheck with 0 errors as well, I get these errors when I submit the epub to Google Books:
EPUB/css/epub.css:1004, 20: An error occurred while parsing the CSS: Token ".code-display" not allowed here.
EPUB/css/epub.css:1004, 20: An error occurred while parsing the CSS: Token ".code-display" not allowed here.
EPUB/css/epub.css:1007, 20: An error occurred while parsing the CSS: Token ".code-display" not allowed here.
EPUB/css/epub.css:1007, 20: An error occurred while parsing the CSS: Token ".code-display" not allowed here.
EPUB/css/epub.css:1379, 18: An error occurred while parsing the CSS: Token ".autopermalink" not allowed here.
EPUB/css/epub.css:1379, 18: An error occurred while parsing the CSS: Token ".autopermalink" not allowed here.
EPUB/css/epub.css:1382, 18: An error occurred while parsing the CSS: Token ".autopermalink" not allowed here.
EPUB/css/epub.css:1382, 18: An error occurred while parsing the CSS: Token ".autopermalink" not allowed here.
EPUB/css/epub.css:1385, 20: An error occurred while parsing the CSS: Token "a" not allowed here.
EPUB/css/epub.css:1385, 20: An error occurred while parsing the CSS: Token "a" not allowed here.
May I know why is this so, and how to solve?
(Screenshot attached below also:)
- Dominant language
- XSLT
- Stars
- 466
- Forks
- 251
- Avg merge
- 4m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PreTeXtBook/pretext
-
The print preview leaves writing space short by the margins of hidden headers, footers and solutionsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3329 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
PreTeXtBook/pretext#3305 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3297 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PreTeXtBook/pretext#3285 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3283 ·
Maintainers usually reply within 1 day
All issues in PreTeXtBook/pretext
Similar issues
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
storytold/photocraft#15500 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NativeScript/ios#577 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
phantoslayer21/wronggpu#274 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
DNNCommunity/DNN.Blog#231 ·
-
ready-for-ai
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
umbraco/Umbraco-CMS-MCP-Dev#650 ·
Maintainers usually reply within 1 day