Quote:
Originally Posted by salamanderjuice
Debatable that RMSDK gives better typography. Personally I preferred the Webkit renderer. Last time I checked Kobo's RMSDK version lacked support for things like RTL and vertical writing and MathML which limits utility. It's also just really annoying and confusing frankly to have this dual system based on file extension. They really need to rethink how it's done as naive sideloading can lead to unusable results.
|
The WebKit based renderer does not do well with ligatures, kerning and other common bits of typography and word spacing when justifying text can get odd especially on smaller screens. You can play with OptimizeSpeed, OptimizeLegibility and GeometricPrecision but they all seem to have tradeoffs that I prefer to avoid. I'm not certain what Auto does since it seemed to have little effects in my testing.
This was testing by adding one of the following lines under the [Reading] heading in the Kobo eReader.conf file and seeing what if any changes it made in the visual appearance of my test file:
Code:
webkitTextRendering=auto
webkitTextRendering=geometricprecision
webkitTextRendering=optimizelegibility
webkitTextRendering=optimizespeed