View Single Post
Old 12-02-2020, 09:40 PM   #21
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
Quote:
Originally Posted by chaley View Post
It looks like parsing the template passed by the kobo driver is failing, perhaps because of line endings or character set issues. One possible solution is to simplify that template. You can do that by making the original template into a "stored template" then calling that template from one in the kobo driver.
For the record, the driver uses the subtitle template with:

Code:
                    pb = [(self.subtitle_template, 'subtitle')]
                    book.template_to_attribute(book, pb)
                    new_subtitle = book.subtitle
That is devices/kobo/driver.py line 3243. And the KoboTouchExtended driver subclasses the KoboTouch driver and doesn't override anything related to this.

The "book" is basically a Metadata object with some Kobo specific attributes. It will be the Book defined in from devices/kobo/books.py.

@ownedbycats: The subtitle should have been updated after fixing the template. It has been when I have used it. And I think that was one of my tests when I did this. I don't use the subtitle myself, but, I'll test it sometime soon.
davidfor is offline   Reply With Quote