Page MenuHomePhabricator

Ebook Exports: Formatting issues caused by the turning on of an option in calibre
Open, Needs TriagePublic

Assigned To
None
Authored By
ifried
Jan 5 2021, 5:15 PM
Referenced Files
F33986020: nice.png
Jan 5 2021, 5:18 PM
F33986018: headlines.png
Jan 5 2021, 5:18 PM
F33986016: linebreaks.png
Jan 5 2021, 5:18 PM

Description

Background: There are some changes to the display of ebooks I believe caused by the turning on of an option in calibre (https://github.com/wsexport/tool/pull/297). Only affects formats which are produced by Calibre, like PDF, Mobi. Does not affect epubs. I believe the change was in order to improve performance of pdf generation.

Examples include:

Event Timeline

@dmaza Looks like this didn't get estimated yet. Any suggestion for the points it should be assigned? Thanks in advance.

@dmaza Looks like this didn't get estimated yet. Any suggestion for the points it should be assigned? Thanks in advance.

I would say 2 points ?

ifried set the point value for this task to 2.Jan 19 2021, 6:45 PM

I've managed to get the same visual results with and without --enable-heuristics by setting the following options --disable-delete-blank-paragraphs --disable-format-scene-breaks --disable-markup-chapter-headings --disable-unwrap-lines but I didn't get any gains in terms of performance. I tried multiple combinations and it seems that --disable-delete-blank-paragraphs is what slows things down but without it the PDF doesn't look right.
Anyhow, I've hit a wall and at this point this requires further exploration and maybe even look into calibre source to figure out what's going on and why generating the book goes from 10s to 60s in the presence of fonts.

To add more context, when adding the --enable-heuristics option to ebook-convert, the following book (Kapitanov_ključ) was exported to pdf in ~10s compared to ~60s without that option. And this is only an improvement when you are including fonts in the ebook, if no fonts are present the pdf is generated in ~10s with or without the option.

@ifried I don't really know where to go from here other than what I suggested above. Maybe we should move this into our backlog and possibly take a second look after we are done with our more pressing tasks

I'm removing the Community-Tech tag from this ticket. As a team, we have recently discussed this and determined that we will not be moving forward with this ticket. The only remaining work we do could do would be large & out of scope for our project (which will be closing soon), and there are no guarantees that it would result in us identifying the problem or what we can do about it. However, I will leave the ticket open, in case anyone else wants to investigate or dig into it in the future.

ifried removed the point value for this task.Mar 17 2021, 11:23 PM
ifried removed a project: Community-Tech.
Aklapper added a subscriber: dmaza.

@dmaza: Removing task assignee as this open task has been assigned for more than two years - See the email sent to task assignee on Feburary 22nd, 2023.
Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome! :)
If this task has been resolved in the meantime, or should not be worked on by anybody ("declined"), please update its task status via "Add Action… 🡒 Change Status".
Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator. Thanks!