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

AZW3 support #671

Closed
FritzHeiden opened this issue Jan 29, 2024 · 7 comments
Closed

AZW3 support #671

FritzHeiden opened this issue Jan 29, 2024 · 7 comments

Comments

@FritzHeiden
Copy link

FritzHeiden commented Jan 29, 2024

Thanks for kcc I use it to convert cbz to mobi for my kindle. Lately I wanted to organize them a little better by improving the quality of the metadata so it looks nice on the device. However, I noticed that the mobi format has immutable metadata and that azw3 format should be used instead. Converting ebooks with calibre, however, introduces a white border which I just can't get rid of. I tried multiple settings but none seem to work for me.

I think its not really a good option to tag cbz with the metadata that I want to have in the mobi file and convert everthing again, this should be simpler imho. Besides, some tags are not copied to the output file, e.g. the language (although not that important).

Have you considered support for azw3 as output format (not just mobi)? If this is not an option for this project, do you have any recommendations for my problem?

Thanks

@AcidWeb
Copy link
Collaborator

AcidWeb commented Jan 29, 2024

For technical reasons KCC output hybrid MOBI7+KF8 file. It already have headers like AZW3.
Calibre just never got support to edit such files correctly. And in general, it doesn't need this support - it's a pretty exotic case.

And even if KCC would output "pure" AZW3 reconverting file in Calibre would still break the file.

@FritzHeiden
Copy link
Author

For technical reasons KCC output hybrid MOBI7+KF8 file.

What do you mean? The generated mobi file is hybrid MOBI7+KF8?

It already have headers like AZW3. Calibre just never got support to edit such files correctly. And in general, it doesn't need this support - it's a pretty exotic case.

The CLI tool ebook-meta specifically exists to just edit the metadata of ebook files, including mobi, it just doesn't work.

And even if KCC would output "pure" AZW3 reconverting file in Calibre would still break the file.

Again, I would like for KCC to generate the proper AZW3 file and just edit the metadata with calibre, no reconversion necessary.

@AcidWeb
Copy link
Collaborator

AcidWeb commented Jan 29, 2024

Yes. Generated file is both MOBI and AZW3 file. It just have .mobi extension.
ebook-meta don't know how to edit both sets of headers in such file.

Last time I checked (and that was years ago) tools that edited "only" metadata also deleted comic related header data. Maybe that was improved.

@AcidWeb
Copy link
Collaborator

AcidWeb commented Jan 29, 2024

Also to answer your original question - this application would require major rewrite to output pure AZW3 files. It is caused by limitations of application that is used to generate the output files - kindlegen.

@FritzHeiden
Copy link
Author

Alright, thank you. I'll keep looking for a solution then.

@quantumicrowave
Copy link

Alright, thank you. I'll keep looking for a solution then.

did you find a solution?

@FritzHeiden
Copy link
Author

did you find a solution?

I modified kcc to accept the tag data as CLI parameter. You can find it in the PR I opened for this: #675

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

3 participants