View Single Post
Old 01-07-2022, 01:39 AM   #11
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Some expansion on @Sirtel's reply:

Quote:
Originally Posted by Sirtel View Post
2. Right, no stats with epubs
No in-book stats for epubs. The stats shown on the Activity->Reading Stats page are done for both.
Quote:
3. Yes, settings are saved for each book
It also sets the settings for the next book. Or when reopening a book that does not have stored font settings.
Quote:
4. Also true. To change this with a book sideloaded from Calibre, change the <p> tags to <br> tags in the comments section (the html view). Unfortunately it must be done manually with each book, as the bulk option won't stick
Unlike most places that use HTML syntax to display text, the synopsis shows any carriage returns that are in the code. And the editor that calibre uses for the comments puts them in between p tags. Using br tags does solve it but, it is ugly. Using a metadata plugboard on the comments will remove any extra whitespace and the synopsis should display without the extra line spaces. It should work with just:

Code:
{comments}
The reason for "should" is that there have been changes in template language recently and they affected this. And my metadata plugboard is a lot more complex and explicitly strips the extra whitespace characters.

If that doesn't work, the following should:
Code:
program:
re(field('comments'), '\s+', ' ');
Spoiler:
For anyone who is interested, I use:

Code:
program:
comment=field('comments');
rating_str = test($rating, strcat('<p><b>Rating:</b> ', rating_as_stars($rating), '</p>'),'');
kobo_last_read_str = test($#kobo_last_read,strcat('<p><b>Last Read:</b> ', $#kobo_last_read, '</p>'),'');
word_count = test(field('#words'),strcat('<b>Word count:</b> ', field('#words')),'');
page_count = test(field('#pages'),strcat('<b>Page count:</b> ', field('#pages')),'');
counts = test(strcat(word_count,page_count),'<p>','');
counts = test(word_count,strcat(counts,word_count),counts);
counts = test(word_count,test(page_count,strcat(counts,' '),counts),counts);
counts = test(page_count,strcat(counts,page_count),counts);
counts = test(strcat(word_count,page_count),strcat(counts,'</p>'),'');
extradata = strcat(rating_str,kobo_last_read_str,counts);
comment=strcat(comment,test(extradata,strcat('<hr/>',extradata),""));
re(comment, '\s+', ' ');
Which puts the comments followed by a line, my rating for the book, when I read it, the word count and the page count. The complications are so that if the values do not exist, there are no errors, and nothing is added for that item.
davidfor is offline   Reply With Quote