Thread: Kepub format questions
View Single Post
Old 05-26-2019, 07:43 AM   #95
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 Gorcsev View Post
Hi,

I am using KTE sending books to kobo in kepub format. I found a strange behavior handling the "endash". The following happens by sending to the device (a=Lowercase, A=Uppercase):

a – a not converted
a – A not converted
a. – a not converted
a. - A endash => minus sign
a! – a not converted
a! - A endash => minus sign
a? – a not converted
a? - A endash => minus sign
a: – a not converted
a: - A endash => minus sign
a… – a not converted
a… - A endash => minus sign

I have checked the container.py but I didn't find if that is happening there.
I have checked the kepubify it doesn't do it.
I would like to keep en-dashes wherever they exist in my original epub.
Any chance of telling us exactly what you are doing? And where you are seeing this? And it would probably be better to post actual HTML source to show what the starting point is.

Also, if you are reporting a bug against the KoboTouchExtended driver, there is a dedicated thread for discussion it in the calibre Plugin forum. It is better to report bugs there.
davidfor is offline   Reply With Quote