Thread: Aura H2O Error in interface language. Support donīt fix it.
View Single Post
Old 11-30-2017, 06:11 PM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by koboH2O View Post
Hello to all the community.
I bought a kobo H2O Aura edition 2 (Firmware 4.6.9995) a few days ago, and in one of the texts on the index page, a translation error appears in Spanish.
Attachment 160304

Appears LIBRI and the correct traslation is LIBROS
I restore the kobo, change to other languages, etc... but in support donīt fix the problem, only they ask me more and more data of the firmware version, where is locate the error, etc.

I have read in the forum how to modify the kobo software, and although I have knowledge in Linux Computers I do not understand how to access the interface language to fix it.

It is a great e-reader, but I do not understand these errors and they do not solve it.
Sorry, but what else are they supposed to do? They need details of what the problem is to get it fixed. Those details will then be supplied to the developers to check and fix. Then when the fix has been made, the fix will be tested internally, tested with beta testers and then released to the public for use. And they will ask for the firmware version because maybe it has been fixed. Or to see if it is a new problem.

For a translation problem, a factory reset is probably overkill. But, changing languages to check what happens isn't unreasonable. I've seen plenty of problems over the years because loading a new language was handled badly and exactly what you saw after changing depended on the two languages involved.
davidfor is offline   Reply With Quote