View Single Post
Old 04-08-2014, 02:35 AM   #2554
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
So I was right to be paranoid

As a rule, the current Kobo ereaders use the same firmware. There are differences in the UI but they are running the same code. I am running a different firmware version but I would not have expected this to be something that has changed. Having said that, it wouldn't surprise me if the "<br>" caused a problem but the "<br />" was OK.

And I just realised why I didn't see the problem. I have "replace_br_with_p: true" in my personal.ini. The "<br>" was disappearing completely. When I removed the option, the test cases broke on my Glo. And stories created with the updated version of the plugin work with no problems.
davidfor is offline