Quote:
Originally Posted by DuckieTigger
They took that away so they wouldn't need to waste CS training on fixing stupid mistakes. Same as they intentionally broke the font-ramp and custom fonts. The functionality is technically there, at least last time I had a jailbroken Kindle, but the filename it is looking for has a newline character in it (==cannot find custom file).
|
Eh? Both the font_ramp and custom fonts worked with my Oasis 3. The first only with AZW3, true.