Problem in book details if emoji is first character

Comfy.n · 01-08-2025, 08:27 AM

thanks!

Off-topic: when using the option "Show with comments" on composites, I found that it's necessary to add an invisible space before unicode characters like ✏️ (but it's needed only in the beginning of the field, found this curious, maybe some Qt annoyance)

chaley · 01-08-2025, 09:13 AM

Quote:

Originally Posted by Comfy.n

thanks!

Off-topic: when using the option "Show with comments" on composites, I found that it's necessary to add an invisible space before unicode characters like ✏️ (but it's needed only in the beginning of the field, found this curious, maybe some Qt annoyance)

So if the first character of the composite result is a pencil or other similar character then there is a problem, otherwise not?

Comfy.n · 01-08-2025, 10:01 AM

yes, I'm going to take a screencap later

Comfy.n · 01-08-2025, 10:53 AM

Oh well, now I can't reproduce it in the book details output. Removed the invisible space and it displayed fine.

the other day it was returning this instead: (two question marks in a "diamond" symbol)

Attachment 212928

so I had to use...

📂 {#path2} 🏚️ Published in {pubdate} by {publisher} 📈 {#pp}

instead of

📂 {#path2} 🏚️ Published in {pubdate} by {publisher} 📈 {#pp}

chaley · 01-08-2025, 11:22 AM

I can repeat more-or-less what you saw. It appears to be a problem in Qt's HTML renderer. The HTML generated by calibre is fine.

Example: a composite that produces one character as output:

Code:

program: '✏️'

The resulting HTML

Code:

<div id="_composite" class="comments"><p class="description">✏️</p></div>

An online HTML renderer gives me this:
Attachment 212932

The result in book details is this. Note that I see a pencil, just not the one the character specifies:
Attachment 212930

If I turn on the field header then I get this:
Attachment 212931

Clearly Qt's renderer is misbehaving. I don't know why, but there are now two workarounds:

The one you used, a zero-width space.
Turn on the header.

kovidgoyal · 01-08-2025, 11:46 AM

I reported this to Qt long ago, predictably they did nothing about it:
https://bugreports.qt.io/browse/QTBUG-129836

Comfy.n · 01-09-2025, 01:12 AM

Quote:

Originally Posted by chaley

Clearly Qt's renderer is misbehaving. I don't know why, but there are now two workarounds:

The one you used, a zero-width space.
Turn on the header.

Thank you for confirming.

Quote:

Originally Posted by kovidgoyal

I reported this to Qt long ago, predictably they did nothing about it:
https://bugreports.qt.io/browse/QTBUG-129836

01-08-2025, 10:53 AM	#4
Comfy.n want to learn what I want Posts: 1,611 Karma: 7891011 Join Date: Sep 2020 Device: none	Oh well, now I can't reproduce it in the book details output. Removed the invisible space and it displayed fine. the other day it was returning this instead: (two question marks in a "diamond" symbol) Attachment 212928 so I had to use... 📂 {#path2} 🏚️ Published in {pubdate} by {publisher} 📈 {#pp} instead of 📂 {#path2} 🏚️ Published in {pubdate} by {publisher} 📈 {#pp} Attached Thumbnails

01-08-2025, 11:22 AM	#5
chaley Grand Sorcerer Posts: 12,440 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	I can repeat more-or-less what you saw. It appears to be a problem in Qt's HTML renderer. The HTML generated by calibre is fine. Example: a composite that produces one character as output: Code: program: '✏️' The resulting HTML Code: <div id="_composite" class="comments"><p class="description">✏️</p></div> An online HTML renderer gives me this: Attachment 212932 The result in book details is this. Note that I see a pencil, just not the one the character specifies: Attachment 212930 If I turn on the field header then I get this: Attachment 212931 Clearly Qt's renderer is misbehaving. I don't know why, but there are now two workarounds: The one you used, a zero-width space. Turn on the header. Attached Thumbnails Attached Images

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Book Details vs. Link to show book details in popup Window	msel	Library Management	3	03-19-2024 05:48 PM
Book details->Copy->All book details	BetterRed	Library Management	25	05-10-2023 01:14 AM
Problem with character encoding	thesuker	Calibre	2	11-09-2012 10:11 PM
Book Details Window Problem	Blossom	Calibre	11	11-14-2010 01:45 AM
Character translation problem	James_Wilde	Calibre	1	08-19-2010 02:00 PM

01-08-2025, 08:27 AM	#1
Comfy.n want to learn what I want Posts: 1,611 Karma: 7891011 Join Date: Sep 2020 Device: none	thanks! Off-topic: when using the option "Show with comments" on composites, I found that it's necessary to add an invisible space before unicode characters like ✏️ (but it's needed only in the beginning of the field, found this curious, maybe some Qt annoyance)

01-08-2025, 10:01 AM	#3
Comfy.n want to learn what I want Posts: 1,611 Karma: 7891011 Join Date: Sep 2020 Device: none	yes, I'm going to take a screencap later

01-08-2025, 11:46 AM	#6
kovidgoyal creator of calibre Posts: 45,339 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	I reported this to Qt long ago, predictably they did nothing about it: https://bugreports.qt.io/browse/QTBUG-129836

Advert

Advert