Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for other eBook formats #10

Open
athieriot opened this issue Aug 10, 2014 · 6 comments
Open

Support for other eBook formats #10

athieriot opened this issue Aug 10, 2014 · 6 comments

Comments

@athieriot
Copy link

Hi,

This project is incredibly useful and very easy to use.

I was gonna try to wrap the Calibre command line tool ebook-meta but having a pure Node.js implementation is way better.

In your opinion, how hard would it be to support other ebooks format?
I am particularly interested in the metadata and not so much in the content itself.

Thanks

@julien-c
Copy link
Owner

Which ebook formats are you thinking about? Would probably not be hard to do.

@athieriot
Copy link
Author

I noticed that Calibre is supporting a crap load of different format:

http://manual.calibre-ebook.com/cli/ebook-meta.html

But to be honest there must be about 3 or 4 majors ones: epub, azw (3, 4?) and mobi.
I think I was able to download chm from Google Book but it's probably a glitch or a minor alternative.

mobi is probably equivalent to epub (Some variant of HTML), but It's possible that azw involve working with Adobe eBook DRM which would increase the complexity. (Maybe ok for the metadata though)

@julien-c
Copy link
Owner

AFAIK usually the whole zip file is encrypted so you wouldn't be able to access metadata either. mobi as well is encrypted. Wrapping ebook-meta actually sounds like a good idea to me. What are the downsides?

@athieriot
Copy link
Author

The main downside is the dependency to a native command line tool. The native Node.js implementation is more appealing surely :)

However I was sort of hoping for the meta data reading to be more straightforward.

Thanks for your insight :)

@julien-c
Copy link
Owner

It might be, not 100% sure :)

On Monday, August 11, 2014, Aurélien Thieriot [email protected]
wrote:

The main downside is the dependency to a native command line tool. The
native Node.js implementation is more appealing surely :)

However I was sort of hoping for the meta data reading to be more
straightforward.

Thanks for your insight :)


Reply to this email directly or view it on GitHub
#10 (comment).

@athieriot
Copy link
Author

I might look into it then. (No promise so)

But if I do, I'll definitely propose a Pull Request !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants