maemo.org Bugzilla – Full Text Bug Listing
|Summary:||"Already at minimum / maximum font size." not translated|
|Product:||[Maemo Official Applications] Utilities||Reporter:||Tomasz Dominikowski <dominikowski>|
|Component:||X Terminal||Assignee:||unassigned <nobody>|
|Status:||CLOSED FIXED||QA Contact:||osso-xterm-bugs|
SOFTWARE VERSION: (Control Panel > General > About product) 1.2009.41-10 STEPS TO REPRODUCE THE PROBLEM: Open the X Terminal with Polish translation. View the menu, try toggling the font size to its maximum and minimum size using the hardware buttons. EXPECTED OUTCOME: "_Nowy" should be "Nowy" "_Czcionka" should be "Czcionka" "_Zapisz" (in the font choose dialog) should be "Zapisz" "Already at minimum font size." should be translated. "Already at maximum font size." should be translated. ACTUAL OUTCOME: Two untranslated strings and three strings with accelerator keys that should have been removed. REPRODUCIBILITY: (always/sometimes/once) Always. EXTRA SOFTWARE INSTALLED: None that would interfere. OTHER COMMENTS: User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:22.214.171.124) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14
Heja, thanks for reporting! (Please file only only one issue per report) The accelerators thingy is now fixed in week42 (bug 5128) and is not language specific. :) Exact step is to use the hardware zoom button to get these messages. These strings are also untranslated in German hence probably a general issue.
Fixed as of osso-xterm-0.14.mh29: https://garage.maemo.org/svn/osso-xterm/osso-xterm/tags/0.14.mh29
The underscores are a separate issue. The lack of translation for the popup messages is what's fixed.
This has been fixed in package osso-xterm 0.14.mh29+0m5 which is part of the internal build version 2009.44-5 (Note that 2009 is the year and the number after is the week.) Any public update released with or after this build version will include the fix. Please verify that the 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.
The problem reported here should be fixed in the update released today for public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes). Please leave a comment if the problem is not fixed for you in this update version.