this post was submitted on 22 Oct 2023
270 points (88.1% liked)
Technology
59403 readers
2521 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why are kfx files often larger and sometimes double the size?
Lacks compression?
Don't know if it really matters, though. 8GB of storage holds a lot of books, even if they're illustrated, and that's what base-model e-readers are coming with.
It matters to me, since I find the differences in sizes to be stark when I compare them. I already find page turns on my Paperwhite a tad slow (even with page refresh off). So converting all of my books to kfx (which was my initial plan) seems like a bad idea.
KFX is actually faster at page turning, as it doesn't need to calculate how to spread words to fill the most lines per page.
That makes sense to me. Access speed and disc space are often inversely related. It's like pre-optimizing the file for faster consumptionater by adding more information at "compile time" vs "run time".
A source to read more about this and how exactly kfx works and it's enhanced typesetting would be cool.
Do you know of alternative methods of producing kfx files other than the official Amazon app and Calibre's plugins for it?
And how would I go about editing a kfx file?