Bug 447789 - FictionBook fb2: bad paragraph formatting
Summary: FictionBook fb2: bad paragraph formatting
Status: CONFIRMED
Alias: None
Product: okular
Classification: Applications
Component: fictionbook backend (show other bugs)
Version: 21.12.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-01 17:39 UTC by soshial
Modified: 2022-01-13 03:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
correct example of a real book (168.13 KB, image/jpeg)
2022-01-01 17:42 UTC, soshial
Details
correct example of a real book (113.27 KB, image/jpeg)
2022-01-01 17:43 UTC, soshial
Details
shoudl show epigraph, text should be justified (291.66 KB, image/png)
2022-01-01 17:47 UTC, soshial
Details

Note You need to log in before you can comment on or make changes to this bug.
Description soshial 2022-01-01 17:39:22 UTC
SUMMARY
1. The text alignment is to the left.

EXPECTED RESULT:
1. The text should have justified alignment (see examples).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 soshial 2022-01-01 17:42:50 UTC
Created attachment 145016 [details]
correct example of a real book
Comment 2 soshial 2022-01-01 17:43:03 UTC
Created attachment 145017 [details]
correct example of a real book
Comment 3 soshial 2022-01-01 17:47:12 UTC
Created attachment 145018 [details]
shoudl show epigraph, text should be justified
Comment 4 Albert Astals Cid 2022-01-03 22:48:38 UTC
Can you link to the fictionbook spec where it says that text should have justified alignment by default?
Comment 5 Albert Astals Cid 2022-01-04 17:39:14 UTC
Do not change the assignee.
Comment 6 soshial 2022-01-09 07:08:22 UTC
Well, the core idea of the fb2 format is to never decide for the user, which text formatting or styling should be used. fb2 purpose is only to structurize data semantically (closest analogy is bare HTML with no styles).
The task of formatting and styling (CSS in this analogy) customization is shifted to the reader software. User is supposed to set up these styles to their liking once and for all. Also, different countries might have different styling traditions and user is supposed to be able to change that easily. The reading software keeps and applies the same settings for every book.

Summing up, I don't think I can provide any formatting/styling specification for the format, that was designed to avoid specificating styles.

In my opinion, our main task here is to make user experience as close to a real reading book as possible. Otherwise, user would open a fiction book in our reader for the first time, see an "bad" unwonted formatting and close Okular at once. We don't want that.

Just open several fiction book and look at the text. All of them would have justified text. Epigraphs would be mostly italic and aligned to the right. We should just copy that and maybe some day we support customizing these preferences in Settings -> Configure backends...