maemo.org Bugzilla – Bug 6982
Spanish: "Tipo de fuente cambiado a %s" when switching input languages
Last modified: 2010-05-27 00:47:42 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: 1.2009.42-11 EXACT STEPS LEADING TO PROBLEM: 1. Set es_ES locale. 2. Press Ctrl+Space while a text box is focused. EXPECTED OUTCOME: A HildonBanner with something roughly equivalent to "Input language switched" in spanish, like "Idioma de entrada cambiado". The input language is switched succesfully. ACTUAL OUTCOME: "Tipo de fuente cambiado", which literally means "Font face changed". Input language is switched succesfully. REPRODUCIBILITY: always
Repro with SOFTWARE VERSION: 1.2009.42-11 with es_ES ( Español - España ) at input text box ( as example a url input box in a browser ) say "Tipo de fuente cambiado" ( Font type changed/switched ) with es_MX ( Español - Latino America ) at input text box ( as example a url input box in a browser ) say "Idioma de entrada cambiado" ( Input Languague changed/switched )
Actually one step was missing here: Have a "Second language" defined in "Settings > Text input". :-) Confirming as per last comment.
This has been fixed in package hildon-input-method-l10n(-public) 6.0+r7520+0m5 which is part of the internal build version 2010.03-8 (Note: 2009/2010 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).