Bug 237068 - ksudoku: "play" translated as "wiedergabe" instead of "spielen"
Summary: ksudoku: "play" translated as "wiedergabe" instead of "spielen"
Status: RESOLVED DUPLICATE of bug 232918
Alias: None
Product: i18n
Classification: Translations
Component: de (show other bugs)
Version: 4.4
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Thomas Reitelbach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-10 09:22 UTC by S. Burmeister
Modified: 2010-05-10 19:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2010-05-10 09:22:46 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

There is a "play" button in the bottom-right of the window that contains the list of types of games, ie. 9x9 etc. The button displays "Wiedergabe" which should rather read "Spielen".
Comment 1 Frederik Schwarzer 2010-05-10 12:21:29 UTC
Works for me here on 4.4.3 (Debian packages) and trunk (from sources).
But there might be some catalogue being loaded for Sven that isn't loaded here.

Can anyone else reproduce this?

In any case, is it possible to add context to strings from UI files?
Comment 2 markuss 2010-05-10 13:39:17 UTC
Works for me as well (openSUSE with SC 4.4.3).
Comment 3 Burkhard Lück 2010-05-10 13:43:58 UTC
@ Sven:
in branch 4.4? Sicher?
Was sagt ksudoku --version?

(In reply to comment #1)
> Works for me here on 4.4.3 (Debian packages) and trunk (from sources).
> But there might be some catalogue being loaded for Sven that isn't loaded here.
> 
> Can anyone else reproduce this?
> 
In branch selbstkompiliert ist alles korrekt übersetzt:
$ ksudoku --version
Qt: 4.6.2
KDE: 4.4.3 (KDE 4.4.3)
KSudoku: 0.5

In trunk selbstkompiliert fehlen alle Übersetzungen aus ksudoku ("Choose your
Game", "Easy", "Hard", "Start Empty" sind englisch, "Play" zeigt die "falsche"
Übersetzung "Wiedergabe" aus dem Systemkatalog kdelibs4.po:

$ ksudoku --version
xxQt: 4.6.2
KDE Development Platform: 4.4.75 (KDE 4.4.75 (KDE 4.5 >= 20100505))
xxKSudokuxx: 0.5

Sieht bei mir aus wie https://bugs.kde.org/show_bug.cgi?id=232918

> In any case, is it possible to add context to strings from UI files?

Ja, siehe
http://techbase.kde.org/Development/Tutorials/Localization/i18n_Challenges#Translating_UI.2C_RC.2C_and_KCFG_files.

Das ist aber hier nicht nötig, "Play" ist im Katalog ksudoku.po.
Comment 4 S. Burmeister 2010-05-10 16:48:51 UTC
I thought I had chosen "recent svn snapshot". I found the missing translation in the trunk packages from opensuse.
Comment 5 markuss 2010-05-10 18:36:44 UTC
It's also translated in trunk. I guess it's the result of either some buggy lang file importing process (to be expected as trunk packages are entirely unsupported by openSUSE) or you forgot to install all needed "-lang" packages.

Whatever it is, it's nothing we from KDE can do about it.
Comment 6 S. Burmeister 2010-05-10 18:48:55 UTC
Since comment 3 confirms the issue I do not think it's downstream.
Comment 7 markuss 2010-05-10 18:54:28 UTC
It just confirms that you don't have the language pack installed for KSudoku and this could be because of a.) openSUSE or b.) you.

It is translated in the appropriate lang file:

#. i18n: file: src/gui/welcomescreen.ui:62
#. i18n: ectx: property (text), widget (QPushButton, playGameButton)
#: src/gui/ksudoku.cpp:316 rc.cpp:60
msgid "Play"
msgstr "Spielen"
Comment 8 Johannes Obermayr 2010-05-10 19:12:22 UTC
Langsam, Langsam ...

Burkhard stellte fest, dass in 4.4 alles wunderbar funktioniert und in 4.5-devel nicht (was Sven benutzt).
Im Übrigen hat er auch darauf hingewiesen, dass es sich um Fehler #232918 handeln könnte, der genau dieses Problem behandelt. Das nehme ich auch an, da bei mir der gleiche Fehler vorhanden ist.

So wie es aussieht kann aber Albert besagten Fehler nicht nachvollziehen und somit auch nicht weiterhelfen.

Somit kann der Bug niemals "DOWNSTREAM" sein. Vielmehr ist er "DUPLICATE" ...

*** This bug has been marked as a duplicate of bug 232918 ***