Archive for the ‘Uncategorized’ Category

Case sensitivity in file/folder names in calibre library

16/04/2018 6 comments

In a perfect world the case of file and folder names inside a Calibre library will match the values stored in the Calibre metadata database. However if Calibre is running on a system with a case insensitive file system (e.g Windows) if a case mismatch between the Calibre database and the underlying file system actually happens it is ignored and as a result the user is unaware of such mismatches.  If the Calibre library and/or the calibre2opds generated catalog are then run on a case sensitive system (e.g. Linux) then this case mismatch matters.   A visible symptom of such a  case mismatch in a calibre2opds generated catalog is that the catalog cannot find the underlying eBook files for those books that are affected.

Calibre2opds has now been upgraded to detect such mismatches in case between the Calibre metadata database and the underlying file system. This is handled at two levels:

  • The first level is to write warning messages to the calibre2opds log.   The user can then peruse the log and use the Calibre program to correct such mismatches.  The simplest way to do this in Calibre is to edit the Author by adding an extra character at the end and press OK. Having done this  rename the author back to the correct value and press OK again.  This double rename strategy will result in the underlying files matching the case set in the calibre metadata database.
  • The second level is a new option in calibre2opds (on the Main tab) to get Calibre2opds to automatically rename files to match the case stored in the Calibre database.  A secondary benefit of using this approach is that the resulting Calibre library can now be migrated to a system (e.g. Linux) without calibre losing track of the books in the library.  One word of caution is that since this option actually changes (slightly) the names of the files in the Calibre library it is advisable to make a backup of your library the first time you use it in case something goes wrong.  It is not believed that this is likely as extensive testing has been done to try and avoid it becoming an issue but until feedback is obtained on real-world usage such a precaution is just common sense.

Which of the above approaches is used is up to the user.   Feedback on how effective/useful  the two options are in real world usage would be appreciated.

To help make it more obvious to end-users that there is information of potential interest in the Calibre2opds log file the dialog displayed at the end of a generation run now also displays the counts (if any) of error or warning messages written to the current log.   The user can then select the option on the Tools menu to view the current log file to see what messages were logged.

Categories: Uncategorized

Issue register now being done via gitHub

27/11/2017 Leave a comment

Calibre2opds has in the past used the JetBrains YouTrack product for handling issues and feature requests.   Unfortunately JetBrains has decided the calibre2opds project no longer meets their requirements for providing a free license for Open Source projects and have thus not renewed the projects license for YouTrack.   The project could not justify the cost of a paid-for license so as a result we will now use GitHub for handling both Source and Issues going forward.

A list of issues previously handled via YouTrack are included in the Release Notes that are included with each Calibre2opds release.   We will not transfer all previous issues to gitHub unless work is being done on them but for those that we do the reference numbers of the form #c2o-nnn that are listed there will be included in any issues that are repeated on GitHub.

The gitHub Issues system does not provide the same level of capability for categorising issues but hopefully will be sufficient to meet our needs.  We will continue to treat Feature Requests for enhancements as ‘Issues’. For such requests please include the word ‘Feature Request’ in the title of the issue so it is easier to tell which issues are about bugs and which ones are about new features.


Categories: Uncategorized

GetSatisfaction forum discontinued

14/05/2017 Leave a comment

We used to have a dedicated Calibre2opds forum on This has been discontinued as GetSatisfaction now want an annual fee to keep the forum and the level of traffic does not justify the cost. You can continue to use the Related Tools sub-forum within the Calibre forum on for queries about Calibre2opds.

Categories: Uncategorized

Use to continue using Dropbox!

29/03/2017 10 comments

As a number of people have noticed, Dropbox has discontinued supporting the ‘Public Folder’ feature that many Calibre2opds users have made use of to host a Calibre2otds generated catalog that can then be used when away from home.

It is now possible to still use Dropbox to host a Calibre2opds generated catalog by fronting it with the service offered by  Details on how to go about getting the combination of Updog+Dropbox to host your calibre library are covered in the Calibre2opds Online User Guide.

Categories: Uncategorized

Calibre2opds 3.5 final

20/10/2015 2 comments

I have decided that it is time to move the 3.5 release into a ‘final’ state.   Giving it a ‘final’ label may encourage those who do not like to run software labelled as ‘beta’ the confidence to move to this release. The 3.5 release has had lots of bug fixes since the 3.4 release as well as ton of new features.  There are also some under-the-covers performance related changes that should significantly reduce the time taken to generate a large catalog if you are generating both the XML and the HTML versions of the catalog.

Categories: Uncategorized Tags:

Calibre2opds source code now on gitHub

01/04/2015 Leave a comment

The Calibre2opds source code has been migrated to gitHub as the Google Code site which has served us well for some time is going to be closed down later this year.  As we are just about to start development for the 3.5 release now seems an appropriate time to do this migration rather then perhaps being forced to do it in the middle of the development for the 35 release.

This means that the 3.4 release is the last one hosted on Google Code.   It will be available in read-mode for some time, but if you want to get the latest code you will have to go to the new gitHub repository.

There will be a short period where the online documentation has not been updated to reflect this change.  It will be updated appropriately as experience is gained in working with gitHub.

EDIT:  The changes to use gitHub seem to be less than anticipated, so the changes to the online documentation were minimal and should now be complete.

It is possible that it might also be appropriate to migrate the handling of issues and feature requests to gitHub to keep things in one place and to provide integration between versioning and issue resolution.   However no decision has yet been made on this area.

Categories: Uncategorized

Calibre2opds 3.5 development cycle starting

27/03/2015 Leave a comment

The development cycle for Calibre2opds 3.5 is starting up.

Initial ideas for inclusion are:

  • Enhance the generation process to make it more intelligent so that it only attempts to generate catalog pages that have actually changed since the last run.  This would provide significant run time performance gains of the current approach of generating all possible pages to a temporary area and then after the generation only copying changed files to the final catalog location.
  • Allow for the use of Calibre Custom Column field types to be used in search and filter expressions.

If you have some other feature that you would like to be considered for inclusion then please raise it as a feature request on the Calibre2opds Issue register.

One other change that will also be happening as part of the development of this release is moving the source and version control to an alternative service (probably gitHub). Google have announced that the GoogleCode service we currently use will be closing down later this year and so projects need to migrate off it.

Categories: Uncategorized

Calibre2opds 3.4 final

27/03/2015 Leave a comment

It has been decided that it is time to move the 3.4 release into a ‘final’ state.   There have been no significant bug reports for a while now, so giving it a ‘final’ label may encourage those who do not like to run software labelled as ‘beta’ the confidence to move to this release. The 3.4 release has had lots of bug fixes since the 3.3 release as well as ton of new features.

Categories: Uncategorized

Calibre2opds search feature now deprecated

26/06/2014 1 comment

For some time Calibre2opds has had a browser based search feature that has been labelled as experimental.    It has been decided to change the status of this feature to ‘deprecated’ (although we have not yet removed it from the Calibre2opds program).

The reason for this is that the Calibre2opds search feature was based on the draft HTML 5 database feature (commonly known as WebSQL) that was going through the standardisation process.   However this specification has since been withdrawn and is deprecated by the W3C standardisation process.   A consequence is that major browser such as Internet Explorer and Firefox have decided not to support this feature.   Browsers that DO appear to support it are Safari, Chrome and Opera but since this feature is no longer up to be standardised support could well be removed in future versions.

If you decide that you DO want to generate a Calibre2opds catalog to support this feature, then if you use a browser that is not compatible with the current implementation then you will now get an error message stating this when you try and use search.

If anyone can point out any open-source libraries that implement browser side databases in a manner compatible with all major browsers then we would be happy to look at changing the Calibre2opds search feature to utilise such a library.

Categories: Uncategorized

Calibre2opds3.3 final arrives

01/04/2014 1 comment

We have made the Calibre2opds 3.3 (rev 274) into final release as there have not been nay bug reports for a little while now.

The 3.4 release beta program will therefore be starting for any bug reports received against the 3.3 final release, and also for development of new features.

Categories: Uncategorized