View Single Post
Old 04-23-2011, 04:48 AM   #5
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,733
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
Has the encoding detection been changed relatively recently? As I noticed yesterday when I converted a txt document that it failed to detect and I lost my quotes. For the first time ever in using calibre I had to set the encoding manually to cp1252.

Note that I haven't done a conversion of txt for weeks before this. Unfortunately I no longer have the txt to attach to a bug report.

Perhaps it is just normal expected behaviour but having never seen this before I was surprised and I am sure I have converted documents with angled quotes before.

Edit: sorry I maybe should have given this post it's own thread but when you mentioned some additions to encoding detection I thought it might be vaguely relevant.

Last edited by kiwidude; 04-23-2011 at 04:57 AM.
kiwidude is offline   Reply With Quote