View Single Post
Old 03-07-2011, 08:38 PM   #14
ldolse
Wizard
ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.
 
Posts: 1,337
Karma: 123455
Join Date: Apr 2009
Location: Malaysia
Device: PRS-650, iPhone
You're mostly correct except for one part of your solution:

Quote:
Originally Posted by getajob View Post
If you have to use Unicode, then set Input character encoding to UTF-16

UTF-8 is unicode, so there is no need to use UTF-16 ever. UTF-8 is basically the web and ebook standard for Unicode and is always the best file encoding to use. Just make sure your original file is saved as UTF-8.

Regarding your statement on ANSI, 'ANSI' shouldn't even really be called an encoding - ANSI really means 'encode this based on what country I live in, but make sure only people from the same country as me can read it'. Why Microsoft persists in defaulting all their products to ANSI I'll never understand, but it's the root cause of most people's encoding problems.


It probably wouldn't be terribly difficult to add support for reading the Unicode BOM at the beginning of the file so that Calibre can figure out UTF-8/16/32/LE/BE on it's own....

Last edited by ldolse; 03-07-2011 at 11:03 PM.
ldolse is offline   Reply With Quote