Amazon is working on the system integration right now and should be rolled out globally in August. Customers will be able to use Send to Kindle to upload EPUB books directly to their e-reader. I wonder if anyone could point out what I am doing wrong? Alternately could someone suggest another CLI method to produce *.Amazon is going to be supporting the EPUB format later this year. As a last resort I have also completely uninstalled Calibre and then reinstalled without any positive effect. I also have the path to Calibre's executable files properly registered within my larger %PATH% environment variable. I also have the newest release of the 'KFX OUTPUT' plug-in installed (v1.44.0) and it works properly when invoked by the 'Convert books->Convert individually' menu option from the Calibre library.
#Epub metadata editor read only error windows#
Needless to say I am using the latest version of Calibre which will agree to be installed on Windows 7-this is v4.23 and compiled for a 64bit processor. On running the command I receive this following message: No plugin named KFX OUTPUT found Unfortunately I have not been able to get this to work properly. At first I thought I had indeed come upon a CLI solution by using the following documented example (obviously substituting my own input and output filenames for the placeholders given here): calibre-debug -r "KFX Output" - input.epub output.kfx While attempting to find that method I read through the section of the dedicated Calibre support forum which concerns the 'KFX OUTPUT' plug-in (found here). In a-more-ideal world there would be a way to use the 'KFX OUTPUT' plug-in from the commandline, which would provide a fast and transparent workflow from text editor to *.kfx while also allowing the finished file to be named and copied into the end user's folder of choice.
Indeed, according to what I have read from someone who I assume is the software's author that folder structure is 'off limits' and the end user should not be poking around inside nor manually accessing it, instead using the programme's built in methods for saving eBook files to disk (as expressed very clearly here). Also, once you have successfully produced a *.kfx you then must deal with the various ways Calibre renames files for storage inside its own library structure. Calibre must be opened and the source *.epub manually imported into its library before conversion can begin. The general process to make use of the 'KFX OUTPUT' module is a little tedious, not to mention inappropriate for automation.
#Epub metadata editor read only error software#
Still more frustratingly there does not seem to be any Open Software alternative to do so other than the 'KFX OUTPUT' plug-in for Calibre. I am sure everyone who produces eBooks knows that the newest 'Kindle Previewer' will only export *.kpf files which are at best a half-measure towards that end and cannot themselves be read on the Kindle. Sadly, not only has Amazon recently discontinued the excellent, low-footprint CLI application 'Kindlegen' but they provide no official means to produce *.kfx files from either the commandline nor even a more cumbersome windows application. Over the years I have written several perl scripts to automate as much of the task as possible. This can be a very painstaking but also highly repetitive process. I try to make the initial *.epub file as compliant as possible to Amazon's publishing guidelines, using raw XHTML and a plain text editor. I have now deleted my old, difficult to answer question and hopefully replaced it with one that is not only more likely to provide a resolution but may also be useful to other users approaching this general problem.įrom time to time I spend some effort converting texts freely available from Project Guttenberg into a form that is comfortable and easy to read on a device such as the Kindle. My sincere apologies for wasting the forum's time. Unfortunately I then realized I had probably not phrased it in a very helpful way, nor one likely to garner many answers. I asked part of this question a couple of days ago.
0 kommentar(er)
