Quote:
Originally Posted by davidfor
The most likely reason they don't fix it is that they are busy fixing other problems.
Bugs are usually fixed in order of importance. If something is completely broken, it gets fixed immediately. If it prevents the thing being used, causes loss of data, it will get fixed very quickly. If it is purely cosmetic, then it will be low importance. This also depends on how long the bug will take to fix. The less time, the more likely. How easily a bug is to reproduce also affects how quickly it is fixed. If it takes seconds to reproduce and it happens all the time, it makes it easier to find the bug and fix it. If it takes days or weeks to reproduce, then fixing it takes longer because it takes much longer to work out what is wrong.
To me the hyphenation bug is low priority. It seems to happen in a relatively small number of cases. If 50% of the hyphenation is wrong, then fixing it will affect a lot of users. But, if only 1% is wrong, then it drops down the priorities as it probably isn't being seen by a lot of people.
And of course, the biggest reason a bug isn't fixed: The developers don't know about it. If you see a bug, report it to the Kobo. If nobody tells them, they can't fix it. If they see it themselves and nobody outside tells them, then it becomes a low priority bug to fix as it obviously isn't important to the users.
|
I was under the impression that the ACCESS renderer used by Kobo is not developed by Kobo. If that is the case, then Kobo may not be able to directly fix rendering issues in the first place.