MobileRead Forums - View Single Post

Philosopher · 02-06-2015, 07:13 PM

Yes - I recognize the case sensitive issue - although as far as I have experienced it - this does not seem to create the problem that I encounter with file length. It seems my windows can "read" the file - regardless of case (but I understand if CHANGING the case were being done - this would likely cause problems). But it is only when the file name length is too long - and you get that very annoying issue in windows where you can "see" the file (Calibre cannot even see it - i.e. the file size and format data are blank when viewing a library created in unix/osx in a windows install.). But windows cannot (and so Calbre - even if it saw the file - like the Windows file manager does - cannot open it either (or copy it, or alter it, etc.) So you can't in any way open the file (with Calibre or in windows generally - i.e. a PDF with a too long file name) - but worse - you cannot even get windows, directly, to even EDIT the filename down to a proper size. (That gets very frustrating).

That was why I was hoping that a few preference tweaks might be able to DELIMIT the default (I would do it manually in each install - but would suggest it be considered a starting default (alterable by user) for the base install of all platform versions/ BUt in effect forcing my calibre installs on unix/osx machines to use windows "friendly" file names.

It seems like it would be a simple task - if one knew the places it would need to be tweaked in calibre and what the formatting language needed would be. BUt again - there may be something writting into each of the calibre platforms that, at the moment, is "stuck" or fixed so it can't be done. I am HOPING that there may be a work around - but perhaps not.

If not - I do indeed think it is an important topic for this with more detailed knowledge and expertise of the filewriting code for Calibre may wish to discuss. Again - the ideal for Calibre - so far as I understand it (as it is an ideal for any program I believe) would be that its "standard" setup would be the most "friendly" and "usable" to those with NO programming or platform knowledge - while being configurable for those advanced users, knowing what they are changing, to fully utilize the file naming conventions in unix based systems that are not compatible with windows.

Thanks again for you comments and feedback. Let me know if I am clear in what I am suggesting and asking - as I think this is a useful topic for investigation/discussion.

02-06-2015, 07:13 PM	#6
Philosopher Connoisseur Posts: 77 Karma: 12 Join Date: Jun 2010 Device: Kindle	Yes - I recognize the case sensitive issue - although as far as I have experienced it - this does not seem to create the problem that I encounter with file length. It seems my windows can "read" the file - regardless of case (but I understand if CHANGING the case were being done - this would likely cause problems). But it is only when the file name length is too long - and you get that very annoying issue in windows where you can "see" the file (Calibre cannot even see it - i.e. the file size and format data are blank when viewing a library created in unix/osx in a windows install.). But windows cannot (and so Calbre - even if it saw the file - like the Windows file manager does - cannot open it either (or copy it, or alter it, etc.) So you can't in any way open the file (with Calibre or in windows generally - i.e. a PDF with a too long file name) - but worse - you cannot even get windows, directly, to even EDIT the filename down to a proper size. (That gets very frustrating). That was why I was hoping that a few preference tweaks might be able to DELIMIT the default (I would do it manually in each install - but would suggest it be considered a starting default (alterable by user) for the base install of all platform versions/ BUt in effect forcing my calibre installs on unix/osx machines to use windows "friendly" file names. It seems like it would be a simple task - if one knew the places it would need to be tweaked in calibre and what the formatting language needed would be. BUt again - there may be something writting into each of the calibre platforms that, at the moment, is "stuck" or fixed so it can't be done. I am HOPING that there may be a work around - but perhaps not. If not - I do indeed think it is an important topic for this with more detailed knowledge and expertise of the filewriting code for Calibre may wish to discuss. Again - the ideal for Calibre - so far as I understand it (as it is an ideal for any program I believe) would be that its "standard" setup would be the most "friendly" and "usable" to those with NO programming or platform knowledge - while being configurable for those advanced users, knowing what they are changing, to fully utilize the file naming conventions in unix based systems that are not compatible with windows. Thanks again for you comments and feedback. Let me know if I am clear in what I am suggesting and asking - as I think this is a useful topic for investigation/discussion.