Problems with very huge collection in Arabic - Page 3

BetterRed · 09-26-2013, 11:07 PM

Quote:

Originally Posted by theducks

What, and have the NSA snooping on what I'm doing - they already stole all my mail!!

I should ask Dilma Rousseff if she wants to pony up for a class action against them

BR

kovidgoyal · 09-26-2013, 11:53 PM

It's simple, because some filesystems and OS combinations use system locale dependent encoding for filenames. This means that if you move your files with non-ascii characters between such systems, the filenames change. Or if you use non-unicode aware applications to move the files around, their names get corrupted. This in turn means that calibre will lose track of those files, leading to potential data loss. The only way to prevent that is to use ascii only filenames. Examples of such systems include all linux OSes and all FAT32 filesystems (which are commonly used in removable media and older windows xp installs). And then there is the problem that sometimes the locale dependent encoding is not UTF-8 or UTF-16, which means that not all characters can be represented in it, leading to errors.

When you use save to disk to export files, calibre is creating copies that it no longer keeps track of, therefore it allows non-ascii characters in those filenames, as it can lead to no data loss.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Problems with RTL texts (Arabic, Hebrew)	Doitsu	Kindle Formats	9	07-11-2012 09:26 PM
HUGE problems with USA 505 service	mudfairy	Sony Reader	4	02-14-2010 03:20 AM
Sony PRS 700 - problems with arabic text	firdavs_abc	Sony Reader	1	09-26-2009 07:37 AM
Huge problems converting from odt	superanima	Calibre	9	07-28-2009 01:21 PM

09-26-2013, 11:53 PM	#32
kovidgoyal creator of calibre Posts: 45,374 Karma: 27230406 Join Date: Oct 2006 Location: Mumbai, India Device: Various	It's simple, because some filesystems and OS combinations use system locale dependent encoding for filenames. This means that if you move your files with non-ascii characters between such systems, the filenames change. Or if you use non-unicode aware applications to move the files around, their names get corrupted. This in turn means that calibre will lose track of those files, leading to potential data loss. The only way to prevent that is to use ascii only filenames. Examples of such systems include all linux OSes and all FAT32 filesystems (which are commonly used in removable media and older windows xp installs). And then there is the problem that sometimes the locale dependent encoding is not UTF-8 or UTF-16, which means that not all characters can be represented in it, leading to errors. When you use save to disk to export files, calibre is creating copies that it no longer keeps track of, therefore it allows non-ascii characters in those filenames, as it can lead to no data loss.

Advert