Quote:
Originally Posted by imnnrv
Why not make it optional? For example, via tweaks. It will be nice of you.
I know about non-ascii problem with some devices, but even my Sony PRS-505 in 2007 didn’t have this problem.
For now, I have 812 English books, 701 Russian, 34 Turkish and some (less than 10) in other languages. Transliteration is unusable for me, and I suppose for other users with non-Latin alphabets. Every time I must "save to disk" on my PC, then connect device and overwrite everything. And I cannot just add new books because structure could have been changed between “syncs”. It's a really long process (40 minutes+ on Kobo).
Moon+ Reader Pro on modern android devices, AlreaderX on android e-ink device and KOReader on Kobo (it's not only me, but also family members). For now, I have 3 classes of books (Fiction, Non-Fiction, and Languages learning) and hierarchical categories system in each of them, so I don't know how metadata will save me on mobile devices.
Perhaps metadata would be enough for fiction (even for fiction, series and multiple authors are pain) but for non-fiction, filesystem is the only way  |
Sorry but I have over 2000 non-fiction ebubs. They handle as well as fiction using search and metadata. Yes, it is a different paradigm from sticking with files/directories as if the year 2000 was still a couple of decades in the future but once I started using search/sort, I could not go back to a directory tree which is just too limiting.
As for transliteration, that only applies to the file names. The metadata can carry a full unicode book title, series, etc. which are visible on my Kobo using Nickel.
On Android, you could use the PocketBook renderer. Does a much better job of rendering than Moon+ reader even if you dig into the menu to allow Moon+ to stop disregarding the ebook's CSS.