Kobo Book Description Formatting

[hatuluang]

Originally Posted by jackie_w

Try replacing in its entirety nickel.yaml patch Custom synopsis details line spacing with the following replacement:

Spoiler:

Custom synopsis details line spacing:
  - Enabled: no
  - Description: Sets the line spacing for Book details synopsis & <p> margins/indent
  - FindZlib: "body[qApp_deviceIsTrilogy=true] {\n  line-height: 1.45em;" # qss/BookDetails.qss
  - ReplaceZlibGroup:
      Replacements:
        # m_pluto - add style to reduce inter-paragraph margins for <p> tags
        - Find:    "body {\n  font-family: Georgia;\n  margin: 0px;\n  padding: 0px;\n}"
          Replace: "body {font-family:Georgia; margin:0; padding:0;}\np {margin:0.5em 0 0 0; text-indent:1.5em;}"

        # m_pluto - remove line-height code for oldest Trilogy/Phoenix devices to create space for above code
        - {Find: "body[qApp_deviceIsTrilogy=true] {\n  line-height: 1.45em;\n}\n", Replace: "\n"}
        - {Find: "body[qApp_deviceIsPhoenix=true] {\n  line-height: 1.4em;\n}\n", Replace: "\n"}
          
        # 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.3em;"}

How to make the margin and text indent work on Clara 2E?

[jackie_w]

Originally Posted by hatuluang

How to make the margin and text indent work on Clara 2E?

The same code should work OK on the Clara2E.

[hatuluang]

Originally Posted by jackie_w

The same code should work OK on the Clara2E.

It works, Thank you a lot!

[jackie_w]

Originally Posted by hatuluang

It works, Thank you a lot!

Thanks for confirming it works.

[m_pluto]

Awesome! Thank you so much!

[jackie_w]

Originally Posted by m_pluto

Awesome! Thank you so much!

Is everything done, now?

[hatuluang]

Originally Posted by jackie_w

Is everything done, now?

I'm sorry, forgot to inform you that If I enable the Custom synopsis details line spacing, I can't manage to increase the font on the Custom synopsis font size to 41 px (Clara 2E)

Custom synopsis font size:
  - Enabled: yes
  - Description: Increase synopsis font size
  - FindZlib: "body[qApp_deviceIsTrilogy=true] {\n  font-size: 19px;" # BookDetails.qss
  - ReplaceZlibGroup:
      Replacements:
      - {Find: "font-size: 19px;", Replace: "font-size: 20px;"} # Touch/Mini (Trilogy)
      - {Find: "font-size: 23px;", Replace: "font-size: 25px;"} # Glo/Aura/Aura2E/Nia (Phoenix)
      - {Find: "font-size: 29px;", Replace: "font-size: 32px;"} # AuraHD/AuraH2O/AuraH2O2 (Dragon)
      - {Find: "font-size: 32px;", Replace: "font-size: 41px;"} # GloHD/ClaraHD/Clara2E (Alyssum/Nova) (default: 35px)
      - {Find: "font-size: 34px;", Replace: "font-size: 37px;"} # LibraH2O/Libra2 (Storm)
      - {Find: "font-size: 37px;", Replace: "font-size: 40px;"} # AuraONE/Forma/Sage/Elipsa/Elipsa2E (Daylight)

[jackie_w]

Originally Posted by hatuluang

I'm sorry, forgot to inform you that If I enable the Custom synopsis details line spacing, I can't manage to increase the font on the Custom synopsis font size to 41 px (Clara 2E)

Custom synopsis font size:
  - Enabled: yes
  - Description: Increase synopsis font size
  - FindZlib: "body[qApp_deviceIsTrilogy=true] {\n  font-size: 19px;" # BookDetails.qss
  - ReplaceZlibGroup:
      Replacements:
      - {Find: "font-size: 19px;", Replace: "font-size: 20px;"} # Touch/Mini (Trilogy)
      - {Find: "font-size: 23px;", Replace: "font-size: 25px;"} # Glo/Aura/Aura2E/Nia (Phoenix)
      - {Find: "font-size: 29px;", Replace: "font-size: 32px;"} # AuraHD/AuraH2O/AuraH2O2 (Dragon)
      - {Find: "font-size: 32px;", Replace: "font-size: 41px;"} # GloHD/ClaraHD/Clara2E (Alyssum/Nova) (default: 35px)
      - {Find: "font-size: 34px;", Replace: "font-size: 37px;"} # LibraH2O/Libra2 (Storm)
      - {Find: "font-size: 37px;", Replace: "font-size: 40px;"} # AuraONE/Forma/Sage/Elipsa/Elipsa2E (Daylight)

Can you show me the end of the log.txt file when kobopatch fails to run, please?

[hatuluang]

Originally Posted by jackie_w

Can you show me the end of the log.txt file when kobopatch fails to run, please?

Please find below:

|   Patch("Custom synopsis details line spacing - Jp") enabled=true
          |     ResetBaseAddress()
          |     applying
          |     looping over instructions
          |       kobopatch.FindZlib index=3 line=18
          |         FindZlib("body[qApp_deviceIsTrilogy=true] {\n  line-height: 1.45em;") | hex:626f64795b714170705f64657669636549735472696c6f67793d747275655d207b0a20206c696e652d6865696768743a20312e3435656d3b
          |       kobopatch.ReplaceZlibGroup index=4 line=20
          |         ReplaceZlibGroup(0, []struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"body {\n  font-family: Georgia;\n  margin: 0px;\n  padding: 0px;\n}", Replace:"body {font-family:Georgia; margin:0; padding:0;}\np {margin:0 0 0 0; text-indent:0.5em;}"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"body[qApp_deviceIsTrilogy=true] {\n  line-height: 1.45em;\n}\n", Replace:"\n"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"body[qApp_deviceIsPhoenix=true] {\n  line-height: 1.4em;\n}\n", Replace:"\n"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"line-height: 1.35em;", Replace:"line-height: 1.3em;"}})
          |   Patch("Custom synopsis font size - Jp") enabled=true
          |     ResetBaseAddress()
          |     applying
          |     looping over instructions
          |       kobopatch.FindZlib index=3 line=37
          |         FindZlib("body[qApp_deviceIsTrilogy=true] {\n  font-size: 19px;") | hex:626f64795b714170705f64657669636549735472696c6f67793d747275655d207b0a2020666f6e742d73697a653a20313970783b
          |       kobopatch.ReplaceZlibGroup index=4 line=39
          |         ReplaceZlibGroup(0, []struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"font-size: 19px;", Replace:"font-size: 20px;"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"font-size: 23px;", Replace:"font-size: 25px;"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"font-size: 29px;", Replace:"font-size: 32px;"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"font-size: 32px;", Replace:"font-size: 41px;"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"font-size: 34px;", Replace:"font-size: 37px;"}, struct { Find string "yaml:\"Find\""; Replace string "yaml:\"Replace\"" }{Find:"font-size: 37px;", Replace:"font-size: 40px;"}})
          |         could not apply patch "Custom synopsis font size - Jp": line 39: inst 4: ReplaceZlib: new compressed data is 1 bytes longer than old data (try removing whitespace or unnecessary css)
        --> could not apply patch "Custom synopsis font size - Jp": line 39: inst 4: ReplaceZlib: new compressed data is 1 bytes longer than old data (try removing whitespace or unnecessary css)

[jackie_w]

Originally Posted by hatuluang

Please find below: <snip>

Yes, I suspected that this could possibly happen. It didn't on my testing but if it did on yours then we need to find something a little more robust.

The basic problem is that the 2 patches:

• Custom synopsis details line spacing
• Custom synopsis font size

are not really independent of each other because they are both trying to patch the same CSS resource (BookDetails.qss). Once we start making the Replace code longer than the Find code there is a possibility that kobopatch auto-removes what it considers "excess spaces" when the first patch runs. This results in the Find string from the patch which runs second failing because some spaces have been removed.

If you understood all that, well done! If not, never mind

The solution is to combine both patches into one. IMO this is what should have been done in the first place, but here we are many years later...

Leave this with me for a while. I think I can create a more robust patch which combines the 2 together. I'd like to test it myself before posting so check back here later.

[hatuluang]

Originally Posted by jackie_w

Yes, I suspected that this could possibly happen. It didn't on my testing but if it did on yours then we need to find something a little more robust.

The basic problem is that the 2 patches:

• Custom synopsis details line spacing
• Custom synopsis font size

are not really independent of each other because they are both trying to patch the same CSS resource (BookDetails.qss). Once we start making the Replace code longer than the Find code there is a possibility that kobopatch auto-removes what it considers "excess spaces" when the first patch runs. This results in the Find string from the patch which runs second failing because some spaces have been removed.

If you understood all that, well done! If not, never mind

The solution is to combine both patches into one. IMO this is what should have been done in the first place, but here we are many years later...

Leave this with me for a while. I think I can create a more robust patch which combines the 2 together. I'd like to test it myself before posting so check back here later.

ok, thank you...

[jackie_w]

@hatuluang,

Try the attached new beta patch instead. Put it in nickel.yaml or wherever you keep all your other customised nickel.yaml patches.

You'll need to disable both the old patches:
Custom synopsis details line spacing
Custom synopsis font size

and enable this new one:
Custom synopsis details all-in-one

Spoiler:

Custom synopsis details all-in-one:
  - Enabled: no
  - Description: |
      Customise synopsis body style in Book details,
        including font-size, line-height
      Add style(s) for p tags
  - FindZlib: "body[qApp_deviceIsTrilogy=true] {\n  line-height: 1.45em;" # qss/BookDetails.qss
  - ReplaceZlibGroup:
      Replacements:
        # modify <body> style, customise line-height here
        # Add style(s) for <p> tags
        - Find:    "body {\n  font-family: Georgia;\n  margin: 0px;\n  padding: 0px;\n}"
          Replace: "body {font-family:Georgia; margin:0; padding:0; line-height:1.3em;}\np {margin:0.5em 0 0 0; text-indent:1.5em;}"
        
        # customise font-size by model
        - {Find: "font-size: 19px;", Replace: "font-size:20px;"} # Touch/Mini (Trilogy)
        - {Find: "font-size: 23px;", Replace: "font-size:25px;"} # Glo/Aura/Aura2E/Nia (Phoenix)
        - {Find: "font-size: 29px;", Replace: "font-size:32px;"} # AuraHD/AuraH2O/AuraH2O2 (Dragon)
        - {Find: "font-size: 32px;", Replace: "font-size:35px;"} # GloHD/ClaraHD/Clara2E (Alyssum/Nova)
        - {Find: "font-size: 34px;", Replace: "font-size:37px;"} # LibraH2O/Libra2 (Storm)
        - {Find: "font-size: 37px;", Replace: "font-size:40px;"} # AuraONE/Forma/Sage/Elipsa/Elipsa2E (Daylight)

        # remove all per-model line-heights to create space for above code
        # line-height customisation is now done in the 1st Find/Replace
        ### DO NOT CHANGE OR REMOVE THESE LINES ###
        - {Find: "body[qApp_deviceIsTrilogy=true] {\n  line-height: 1.45em;\n}\n", Replace: "\n"}
        - {Find: "body[qApp_deviceIsPhoenix=true] {\n  line-height: 1.4em;\n}\n", Replace: "\n"}
        - {Find: "body[qApp_deviceIsDragon=true] {\n  line-height: 1.35em;\n}\n", Replace: "\n"}
        - {Find: "body[qApp_deviceIsStorm=true] {\n  line-height: 1.35em;\n}\n", Replace: "\n"}
        - {Find: "body[qApp_deviceIsDaylight=true] {\n  line-height: 1.35em;\n}\n", Replace: "\n"}
        
        # create even more space. 
        # If you set your Kobo to one of the following 4 Japanese/Chinese locales,
        # then comment out the line corresponding to this locale
        - {Find: "body[localeName=\"ja\"] {\n  font-family: Sans-SerifJP, sans-serif;\n  font-style: normal;\n}\n",   Replace: "\n"}
        - {Find: "body[localeName=\"zh\"] {\n  font-family: Sans-SerifZH-Simplified, sans-serif;\n  font-style: normal;\n}\n",   Replace: "\n"}
        - {Find: "body[localeName=\"zh-HK\"] {\n  font-family: Sans-SerifZH-Traditional, sans-serif;\n  font-style: normal;\n}\n",   Replace: "\n"}
        - {Find: "body[localeName=\"zh-TW\"] {\n  font-family: Sans-SerifZH-Traditional, sans-serif;\n  font-style: normal;\n}\n",   Replace: "\n"}

• line-height is now customised in the 1st Find/Replace. This value is no longer model-specific.
• font-size is still model-specific and is customised in the relevant line in the second block of Find/Replaces.
• the rest of the patch code exists to clear enough space so that kobopatch.bat (or kobopatch.sh) doesn't fail. If you never set your Kobo to use any of the Japanese or Chinese locales then you don't need to change anything in this code.

[graycyn]

Originally Posted by Sirtel

Yes, the problem is some of us don't want that line between paragraphs. I don't, for example. That's why I use <br> instead of <p>.

My bad. The OP was talking about extra space showing up, and I didn't realize he was objecting to having the normal one line space between paragraphs.

[hatuluang]

Originally Posted by jackie_w

@hatuluang,

Try the attached new beta patch instead. Put it in nickel.yaml or wherever you keep all your other customised nickel.yaml patches.

You'll need to disable both the old patches:
Custom synopsis details line spacing
Custom synopsis font size

and enable this new one:
Custom synopsis details all-in-one

@jackie_w,
Thank you very much, the patch works very well.

My setup: line-height: 1.25em; margin: 0.5em 0 0 0; text-indent: 1em; and font-size: 41px

[jackie_w]

Originally Posted by hatuluang

@jackie_w,
Thank you very much, the patch works very well.

My setup: line-height: 1.25em; margin: 0.5em 0 0 0; text-indent: 1em; and font-size: 41px

Those gaps between paragraphs are still very large. Are you happy with it like that?

If not, and you use calibre to transfer your books, this could easily be fixed with a calibre Metadata plugboard. I've attached a screenshot of what my Book Details synopsis looks like when using both patch Custom synopsis details all-in-one (no text-indent used in mine) and a Metadata plugboard for calibre comments.

If you want to pursue the plugboard option let me know.