dir="rtl" in html crashes PDF build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calibre |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
OS: OS X
Version: 2.20.0
If I had dir="rtl" to the html tag during generation of PDF using ebook-convert, it crashes. It's working fine for epub generation.
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
Python function terminated unexpectedly: PDF Output failed, see log for details
Traceback (most recent call last):
File "/Applications/
return run_entry_point()
File "/Applications/
return getattr(pmod, func)()
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
Exception: PDF Output failed, see log for details
1% Converting input to HTML...
InputFormatPlugin: HTML Input running
on /var/folders/
Language not specified
Creator not specified
Building file list...
Normalizing filename cases
Rewriting HTML links
34% Running transforms on ebook...
Merging user specified metadata...
Detecting structure...
Detected chapter: Introduction
Detected chapter: Introduction about the x86 architecture and about
Detected chapter: Setup the development environment
Detected chapter: First boot with GRUB
Detected chapter: Backbone of the OS and C++ runtime
Detected chapter: Base classes for managing x86 architecture
Detected chapter: GDT
Detected chapter: IDT and interrupts
Detected chapter: Memory management: physical and virtual
Auto generated TOC with 9 entries.
Flattening CSS and remapping font sizes...
Source base font size is 12.00000pt
Removing fake margins...
Cleaning up manifest...
Trimming unused files from manifest...
Creating PDF Output...
67% Running PDF Output plugin
70% Rendered SUMMARY.html
73% Rendered index.html
76% Rendered index1.html
80% Rendered index2.html
Rendering failed
Attach a file demonstrating/ reproducing the problem to this bug report. You can do that by clicking the "Add attachment or patch" link at the bottom of the bug's page. If the file you are attaching is copyrighted, mark the bug as private. You can do this by clicking the tiny lock icon next to "This report contains Public information" in the top right area of the bug's page.
status incomplete