-
Notifications
You must be signed in to change notification settings - Fork 500
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
media=prepress fails to be processed by Kindle Publishing #2477
Comments
This looks like a duplicate of #2476.
I'm open to accepting a pull request to add this information to the documentation. |
@mementum you can try this workaround. I used it to get a Credit to @mojavelinux for the idea. |
If we can confirm with local tools that this indeed fixes the validation error, we could consider adding this into the converter when media=prepress. But we have to be able to test it locally. |
I'm using |
* put typeset output files in the same dir (nice and easy, no need to jump around to another folder to find the outputs) * don't use rake, it doesn't add anything (and I'm not familiar with it) * tidy up build output, 'cause I'm neat like that 🧹 * upgrade asciidoctor-epub3 to latest available * move some stuff about building the book from the book itself into a new readme since it feels likely to change * use volumes instead of COPY (simplifies and speeds up the build) * fix a Lulu prepress PDF validation issue -- see: * <asciidoctor/asciidoctor-pdf#2476> * <asciidoctor/asciidoctor-pdf#2477> * <https://asciidoctor.zulipchat.com/#narrow/stream/288690-users.2Fasciidoctor-pdf/topic/syntax.20error.20with.20prepress.20PDF> * </~https://github.com/meonkeys/print-this/>
Working with meonkeys, I've been able to confirm that this is, in fact, a bug. What's happening is that fill and stroke color commands are being issued without first defining the color space. This occurs when running content is added to an otherwise empty page. (The commands try to set the color of something, but the color space is not defined as either DeviceRGB or DeviceCMYK. That's what it means by incorrect number of arguments for scn/SCN. I think it must default to DeviceCMYK, and an RGB color is one less argument than CMYK). Here's the point at which I discovered the issue:
Ultimately a bug in Prawn. However, the workaround to set the color space if otherwise empty before writing any running content is straightforward and future proof, so we'll just go with that. |
… graphic state for stamp - clear graphic state on repeater so that the graphic state of the current page is saved instead - remove obsolete workaround to set color space on pages with images
… graphic state for stamp - clear graphic state on repeater so that the graphic state of the current page is saved instead - remove obsolete workaround to set color space on pages with images
… graphic state for stamp - clear graphic state on repeater so that the graphic state of the current page is saved instead - remove obsolete workaround to set color space on pages with images
… graphic state for stamp - map color_space from graphic state on repeater to color space of current page so color space is set properly - remove obsolete workaround to set color space on pages with images
… graphic state for stamp - map color_space from graphic state on repeater to color space of current page so color space is set properly - remove obsolete workaround to set color space on pages with images
…aphic state for stamp - map color_space from graphic state on repeater to color space of current page so color space is set properly - remove obsolete workaround to set color space on pages with images
* put typeset output files in the same dir (nice and easy, no need to jump around to another folder to find the outputs) * don't use rake, it doesn't add anything (and I'm not familiar with it) * tidy up build output, 'cause I'm neat like that 🧹 * upgrade asciidoctor-epub3 to latest available * move some stuff about building the book from the book itself into a new readme since it feels likely to change * use volumes instead of COPY (simplifies and speeds up the build) * fix a Lulu prepress PDF validation issue -- see: * <asciidoctor/asciidoctor-pdf#2476> * <asciidoctor/asciidoctor-pdf#2477> * <https://asciidoctor.zulipchat.com/#narrow/stream/288690-users.2Fasciidoctor-pdf/topic/syntax.20error.20with.20prepress.20PDF> * </~https://github.com/meonkeys/print-this/>
* put typeset output files in the same dir (nice and easy, no need to jump around to another folder to find the outputs) * don't use rake, it doesn't add anything (and I'm not familiar with it) * tidy up build output, 'cause I'm neat like that 🧹 * upgrade asciidoctor-epub3 to latest available * move some stuff about building the book from the book itself into a new readme since it feels likely to change * use volumes instead of COPY (simplifies and speeds up the build) * fix a Lulu prepress PDF validation issue -- see: * <asciidoctor/asciidoctor-pdf#2476> * <asciidoctor/asciidoctor-pdf#2477> * <https://asciidoctor.zulipchat.com/#narrow/stream/288690-users.2Fasciidoctor-pdf/topic/syntax.20error.20with.20prepress.20PDF> * </~https://github.com/meonkeys/print-this/>
Thanks for the fix. |
Let me add positive feedback now that version |
Thanks for sharing @mementum! This makes me very happy. 🕺 |
Removes the need for ink_running_content override. Yay! See: asciidoctor/asciidoctor-pdf#2477
Removes the need for ink_running_content override. Yay! See: asciidoctor/asciidoctor-pdf#2477
media
values ofscreen
andprint
do upload and are processed with no problem.prepress
will be rejected. After adding an optimization pass withrghost
(and obviouslyghostcript
in the background) it does then upload. I also tried theFoxit PDF Editor
, applying only thecleanup
optimization and it also did something which made the format good for Kindle Publishing.Understanding that finding a very small thing in the PDF generation that could be slightly different could be a huge effort, I would propose that a small hint be added to the documentation, pointing that in case of any problem with the
prepress
media mode, an optimization pass can iron things out.Best regards
The text was updated successfully, but these errors were encountered: