View Single Post
Old 10-27-2014, 07:38 AM   #219
Anak
Guru
Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.Anak ought to be getting tired of karma fortunes by now.
 
Posts: 603
Karma: 641742
Join Date: Mar 2012
Location: DE
Device: Kobo Glo
Quote:
Originally Posted by davidfor View Post
Are any of these using the same version of the RMSDK as Kobo? Kobo is now using RMSDK 10, but not the latest build. Up until they upgraded to this earlier in the year they were using a very version that was at least two years old.
I didn't mentioned it as I took this (more or less) for granted that the same version of RMSDK must be used.
I don't argue that Kobo doesn't incorporate every single 'render engine' related bug (issue or improvement/add on) at once. That requires a lot of testing.

Quote:
Originally Posted by norbusan View Post
  • Home screen has overlapping descriptions (see screenshot)
Well, this a good example of bug or error that is very easy to reproduce and therefore can - IMO: should be - avoided and fixed.
A similar issue is the cut off text in the reading stats if the device language is set to Dutch. The text string doesn't fit the allocated space.

The problem here is that the software engineer who is responsible for a specific firmware section must check the outcome for every single language. Double this if it is related to a rendering engine. Then both rendering engines have to be checked for for each language.

Note. There is no language barrier here. The software engineer doesn't have to detect translation errors or such. However he or she can check for text strings or items not being cut off or do not overlap.

If the engineer misses some of these easy to spot/reproduce mistakes/erors/bugs - and in real life it just happens - there should be a internal review process in place that tackles and fixes these kind of issues before the beta firmware is rolled out to a (external) beta testing group existing of knowledgable users. Reported bugs - for the sake of discussion limited here to those easy to spot/reproduce bugs/issues/errors/mistakes - should be fixed before the final release of the firmware version or - if it is more complicated to fix - with the next firmware release.
I could be wrong (actually I hope to be wrong) but I have the impression that the review part I described above is missing in Kobos firmware process or it has some serious flaws.

Last edited by Anak; 10-27-2014 at 08:26 AM.
Anak is offline   Reply With Quote