|
Bugzilla – Full Text Bug Listing |
| Summary: | Help button still English | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Kalman Kemenczy <kkemenczy> |
| Component: | Installation | Assignee: | Stefan Hundhammer <shundhammer> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | coolo, elchevive68, forgotten_XG9X5w8kVa, ke |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Here we go...
Yast2 installer on beta3 (first install) spanish locale Yast2 (first install) on beta3 spanish locale Yast2 installer on beta3 spanish locale |
||
|
Description
Kalman Kemenczy
2008-05-03 21:16:51 UTC
yeah? Created attachment 212167 [details]
Here we go...
We encountered a similar(?) issue in the past. And it was a very persistent issue... Stefan, this seems to be a fallout of the modui. At least it's checking in /usr/share/locale and not in /usr/share/Yast2/locale and the call to bindtextdomain is in libycp: ./libycp/src/YCode.cc: bindtextdomain (domain.c_str (), LOCALEDIR); I guess this needs to be in libyui too or in all frontends? I don't know - fortunately there are only little strings from qt.pot that are visible that prominently. *** Bug 386691 has been marked as a duplicate of this bug. *** still issue in beta3 I'd appreciate if you could fix the bug for 11.0 because it is highly visible. if you want a hotfix: symlink /usr/share/locale/$LANG/LC_MESSAGES/qt.mo to the one in Yast2/locale Hi, I don't know if I had to open a new bug, but the Help button is not tranlated in any YaST module in Beta2 (factory in fact) regards, *** Bug 389579 has been marked as a duplicate of this bug. *** The LOCALEDIR symbol was set to the wrong path: It pointed to /usr/share/locale, not to /usr/share/YaST2/locale. Fixed. Still present in beta 3. The help button and yast2 installer are untranslated. See screeshots (selected locale is spanish) Created attachment 216114 [details]
Yast2 installer on beta3 (first install) spanish locale
Created attachment 216115 [details]
Yast2 (first install) on beta3 spanish locale
Created attachment 216116 [details]
Yast2 installer on beta3 spanish locale
Miguel Angel Alvarez> Still present in beta 3. Stefan Hundhammer wrote “Fixed” on 2008-05-14 (see comment #11). This Fix cannot be in Beta3 yet. Beta3 was released on 2008-05-15 but the submission deadline is always several days before. (In reply to comment #16 from Mike Fabian) > Miguel Angel Alvarez> Still present in beta 3. > > Stefan Hundhammer wrote “Fixed” on 2008-05-14 (see comment #11). > This Fix cannot be in Beta3 yet. Beta3 was released on 2008-05-15 > but the submission deadline is always several days before. Right. I wish people would be less eager to reopen stuff and thus create addtional work for us. The bug is not fixed properly, tested within Beta3+. The Help button in installation screens is localized, but when you click on it, it opens a dialogue box with untranslated title "Help" and the button "Close" is also still in English. (In reply to comment #18 from Ladislav Michnovic) > The bug is not fixed properly, tested within Beta3+. > The Help button in installation screens is localized, This is what this bug report was all about. And this is fixed. > but when you click on it, it opens a dialogue box with untranslated > title "Help" and the button "Close" is also still in English. This is a NEW bug report. Please don't hijack existing bug reports for other issues. (In reply to comment #19 from Stefan Hundhammer) > (In reply to comment #18 from Ladislav Michnovic) > > The bug is not fixed properly, tested within Beta3+. > > The Help button in installation screens is localized, > > This is what this bug report was all about. And this is fixed. My view is different then yours. It is the same issue that you fixed only in one place and not in other places. I can file another bug, but I'll have to explain again what the problem is about and write again details and context. Everything is already here. I'm sparing my and also your time. Here is mine: https://bugzilla.novell.com/show_bug.cgi?id=393848 Original issue is fixed |