Has anyone considered that this is not a bug? That Kobo has designed this font to work exactly this way? And that the older behaviour people want back is actually the bug they have fixed?
This is probably not the case, but, there is plenty of behaviour in various software products that one person calls a bug, but another sees as exactly what is wanted.
For anyone waiting for Kobo Nickel to be "fixed", I suggest you stop waiting. Kobo don't think it's a problem, or don't think it's an important enough problem to fix, or fixing it breaks something else, or maybe they don't know how to fix it. But, it is unlikely to be fixed, so it's probably time to accept it and find another font.
|