View Single Post
Old 05-27-2019, 02:29 AM   #101
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.
Is what you are saying that if you have:

Code:
[lower case letter][punctuation][space]endash[space][upper case letter]
That the endash gets converted to a dash?

If so, it is not obvious from the above. And I cannot reproduce it.
davidfor is offline   Reply With Quote