View Single Post
Old 12-28-2020, 05:46 PM   #6
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 rashkae View Post
It would be interesting to know whether the Kobo is ignoring the line break, or if the conversion to kepub is removing the line breaks. Can you tell us how you are converting to kepub? (are you using the Kepub output plugin and explicitely converting, or are you sending to device with the Kobo Touch Extended Driver) ?
It is the driver. And the conversion should do the same. Somewhere along the way the line break is being lost. I haven't gotten around to looking at when.

The kepub renderer will correctly treat a line break as a space. But, if you highlight text that includes one, it will show when you look at the annotations list.
davidfor is offline   Reply With Quote