3 ms·
Have the DeDRM devs figured out a perfect crack for Amazon's latest DRM (KFX)? Last time I checked the best option was to force Amazon to give you the book in a
by criddell 6y ago
Have the DeDRM devs figured out a perfect crack for Amazon's latest DRM (KFX)? Last time I checked the best option was to force Amazon to give you the book in an older format but then you lose all the typography improvements in KFX.
- kingbirdy 6y agoHow does their DRM improve typography?
- frosted-flakes 6y agoThe DRM doesn't improve typography, the newer format does.
- Tijdreiziger 6y agoThe KFX format is undocumented and has changed over time. Books containing new or unknown features may fail to convert or result in incorrect content or formatting. KFX is more highly processed than Amazon's KF8 (azw3) format, causing some details in the markup of the original e-book provided by the publisher to be lost during conversion. The exact HTML tags and styles originally used in the book are not retained in KFX format. However, all of the text and most of the formatting should be preserved. Images may have been reduced in resolution or converted to black and white to match the capabilities of the device to which they were delivered. PDF resources in KFX print replica books may have been split into multiple files. Links between pages across files will be broken if the PDF content is extracted. These limitations make KFX less suitable for archival and conversion when compared with KF8. [1] [1] KFX Input - https://www.mobileread.com/forums/showthread.php?t=291290 https://www.mobileread.com/forums/showthread.php?t=291290
- ratherbefuddled 6y agoI find for me the most usable experience is to convert to epub, strip all the CSS and fonts, and let my device sort out the typography according to my preference. I never really understand why people think the publisher is best placed to decide the style I choose to read in.
- efreak 6y agoWhy bother stripping them? Any decent reader should have settings to either override individual styles or ignore the stylesheet (FBReader has both, iirc it should be available for ios as well as Android) > I never really understand why people think the publisher is best placed to decide the style I choose to read in. Because that's how books have _always_ worked. My problem is more the huge number of images used in section breaks (and worse, occasionally used in chapter titles). Instead of using an image for a flourish or a section break, _please_ either find a character in your currently used font, or add a subset symbol font; using black images on a white background grabs my attention every time I change pages in dark mode, and even in light mode I can clearly see the difference in background color. Then there's the fact that a good number of them are low resolution, which, depending on reader and styling, causes them to be either pixelated, blurry, or too small to be useful in light mode.
- ratherbefuddled 6y ago> Why bother stripping them? Any decent reader should have settings to either override individual styles or ignore the stylesheet (FBReader has both, iirc it should be available for ios as well as Android) Fonts are usually the biggest culprit in making epub sizes huge which on typical e-ink devices seems to affect load and page turn times. > Because that's how books have _always_ worked. Not really a reason to perpetuate it now we have digital media. > My problem is more the huge number of images used in section breaks (and worse, occasionally used in chapter titles). Instead of using an image for a flourish or a section break, _please_ either find a character in your currently used font, or add a subset symbol font; using black images on a white background grabs my attention every time I change pages in dark mode, and even in light mode I can clearly see the difference in background color. Then there's the fact that a good number of them are low resolution, which, depending on reader and styling, causes them to be either pixelated, blurry, or too small to be useful in light mode. In my experience stripping the CSS (and the fonts and images that are no longer referenced) fixes all of this.
- criddell 6y agoAFAIK, it's the only format on Kindle that will use the newest layout engine which fixes justification issues (ie ragged right), kerning, hyphenation, drop caps, and some of the weird spacing issues that earlier layout engine produced. What you are describing might be fine for novels, but for works where the typography is part of the creative result, it's not a great solution.