View Single Post
Old 03-11-2025, 12:51 AM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,708
Karma: 169712392
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
<delete earlier reply>

You can try the custom synopsis details line spacing patch to reduce the spacing. The times I've tried it, some of the results have been a bit strange.

Code:
Custom synopsis details line spacing:
  - Enabled: no
  - Description: Sets the line spacing for Book details synopsis.
  - FindZlib: "body[qApp_deviceIsTrilogy=true] {\n  line-height: 1.45em;" # qss/BookDetails.qss
  - ReplaceZlibGroup:
      Replacements:
        # Touch/Mini (Trilogy)
      - {Find: "line-height: 1.45em;", Replace: "line-height: 1.3em;"}
        # Glo/Aura/Aura2E (Phoenix)
      - {Find: "line-height: 1.4em;",  Replace: "line-height: 1.3em;"}
        # AuraHD/AuraH2O/AuraH2O2/GloHD/ClaraHD/Clara2E (Dragon) and
        # LibraH2O/Libra2 (Storm) and
        # AuraOne/Forma/Sage/Elipsa/Elipsa2E (Daylight) 
      - {Find: "line-height: 1.35em;", Replace: "line-height: 1.1em;"}

Last edited by DNSB; 03-11-2025 at 12:56 AM.
DNSB is offline   Reply With Quote