Help needed - odd characters printing w/custom metadata jacket tags

jecilop · 09-09-2014, 02:25 AM

UPDATE: Solution in Post #5
****************************************
ORIGINAL:
I just added a custom comments column (#printedpages) - straight text style entry column.

The tags in the jacket are: (_printedpages_label}{_printedpages}
There is nothing else around these.

The printed jacket result looks like: Printed Pgs: p304/p

NOTICE the p###/p

Where are the p's and / coming from? The actual text entry is "clean" with no spaces before or after and no "enter" after the 304.

jecilop · 09-13-2014, 12:01 AM

Anyone? (bump)

eschwartz · 09-14-2014, 01:44 AM

What does the template itself look like around that area?

jecilop · 09-14-2014, 06:53 AM

EXACTLY as noted above.

Quote:

The tags in the jacket are: (_printedpages_label}{_printedpages}
There is nothing else around these.

html code is :
<tr class="cbj_tags">
<td class="cbj_comments" colspan="2"><b>{_printedpages_label}</b> {_printedpages} </td>
</tr>

jecilop · 07-11-2017, 01:18 PM

I note for anyone else who runs into this. I only just solved it this year.
Apparently, the column type that I was referencing was a full text style (like comments) rather than "like a title".
It pulls the html coding into it in this case instead of just the text.

My accidentally discovered solution is that I created another custom column (text format like a title). I then used the Bulk Metadata Edit Search/Replace to copy everything over from entries whose existing info was "true". Then I deleted the original column and used the new one instead. I no longer get the " < > " coding language in the jacket.

Perhaps this is something rarely used an thus never noticed that could be adjusted in Calibre for future releases.

BetterRed · 07-11-2017, 06:18 PM

@jecilop - I'm pretty sure the 'Short text like title' option was added since your posts in 2014.

BR

09-09-2014, 02:25 AM	#1
jecilop Addict Posts: 260 Karma: 139980 Join Date: Mar 2014 Device: Android	Help needed - odd characters printing w/custom metadata jacket tags UPDATE: Solution in Post #5 ************************************** ORIGINAL: I just added a custom comments column (#printedpages) - straight text style entry column. The tags in the jacket are: (_printedpages_label}{_printedpages} There is nothing else around these. The printed jacket result looks like: Printed Pgs: p304/p NOTICE the p###/p Where are the p's and / coming from?** The actual text entry is "clean" with no spaces before or after and no "enter" after the 304. Last edited by jecilop; 07-11-2017 at 01:19 PM. Reason: Solution Update

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Polish Book Metadata Jacket Shows Tags Twice.	Penny_Dreadful	Calibre	2	03-17-2014 09:09 AM
How to correct odd, unwanted characters in an epub?	Skydog	Calibre	20	06-12-2013 05:13 PM
tags on metadata jacket	richreads	Calibre	0	02-23-2013 10:54 AM
Odd letters/characters	MSWallack	Conversion	7	12-30-2011 10:25 AM
Odd Characters When Sending .mobi to Kindle 3	mrh882	Calibre	3	07-27-2011 06:39 PM

09-13-2014, 12:01 AM	#2
jecilop Addict Posts: 260 Karma: 139980 Join Date: Mar 2014 Device: Android	Anyone? (bump)

09-14-2014, 01:44 AM	#3
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	What does the template itself look like around that area?

07-11-2017, 01:18 PM	#5
jecilop Addict Posts: 260 Karma: 139980 Join Date: Mar 2014 Device: Android	I note for anyone else who runs into this. I only just solved it this year. Apparently, the column type that I was referencing was a full text style (like comments) rather than "like a title". It pulls the html coding into it in this case instead of just the text. My accidentally discovered solution is that I created another custom column (text format like a title). I then used the Bulk Metadata Edit Search/Replace to copy everything over from entries whose existing info was "true". Then I deleted the original column and used the new one instead. I no longer get the " < > " coding language in the jacket. Perhaps this is something rarely used an thus never noticed that could be adjusted in Calibre for future releases.

07-11-2017, 06:18 PM	#6
BetterRed null operator (he/him) Posts: 21,662 Karma: 29711016 Join Date: Mar 2012 Location: Sydney Australia Device: none	@jecilop - I'm pretty sure the 'Short text like title' option was added since your posts in 2014. BR

Advert

Advert