Quote:
Originally Posted by Steve_Haley
(For example, iOS heavily restricts how a user can browse the files on the device, so some of the controls around file naming templates might not be needed. I'm still looking into this though.)
|
Assuming that the iOS product still uses the lpath as the calibre identifier, you might need the templates to be sure that a book gets the same lpath no matter what connection is used. This helps prevent duplicates. I have no idea if it matters on iOS for reader app-level syncing. It certainly does on Android.
The template stuff is also used for renaming, which may not be very visible to the user but should be quite visible to CC (lpath again).