2010-08-15, 01:16
Hi Devs !
I as a translator am running into different untranlatable strings in xbmc or in addons. So far i found the following categories of possible localizations:
1. In main c++ code: the g_localizeStrings.Get function
2. In addons Python code with a form of __language__(x)
3. In skins xml files in a form of $LOCALIZE[SCRIPTx]
4. In internal addons i found they call a class called dllSetting
I have two questions so far:
1.
I ran into trouble with the default weather addon's wind direction and speed tranlation. There is a ticket (http://trac.xbmc.org/ticket/9802) with a working solution. In the patch the solution now looks like this:
With this form in strings.xml
Can this be replaced with a solution where the tranlators can exchange the speed unit with the speed number ? I mean currently it expects parameters in %s %i %s order, so there is no way to exchange the parametric parts.
2. With ProjectM addon there is a problem with the quality settings part. There with the spin selection line the localization is not working. In fact it shows the string xml numbers (30001-30004) instead of the actual strings. See ticket http://trac.xbmc.org/ticket/9845
I found out that this addon (unlike others) using a class called DllSetting in xbmc_addon_cpp_dll.h in thw following way:
Somehow the "quality" strings gets translated with the 30000 string, but the spin setting entries they show up as numbers not the actual strings.
I need a little help, where to look for the problems and solutions.
Thanks,
Cheers, Alan
I as a translator am running into different untranlatable strings in xbmc or in addons. So far i found the following categories of possible localizations:
1. In main c++ code: the g_localizeStrings.Get function
2. In addons Python code with a form of __language__(x)
3. In skins xml files in a form of $LOCALIZE[SCRIPTx]
4. In internal addons i found they call a class called dllSetting
I have two questions so far:
1.
I ran into trouble with the default weather addon's wind direction and speed tranlation. There is a ticket (http://trac.xbmc.org/ticket/9802) with a working solution. In the patch the solution now looks like this:
Code:
LocalizeOverviewToken(iTmpStr);
m_info.currentWind.Format(g_localizeStrings.Get(434).c_str(),
iTmpStr, iTmpInt, g_langInfo.GetSpeedUnitString().c_str());
With this form in strings.xml
Code:
<string id="434">From %s at %i %s</string> <!--From <wind dir.> at <speed> <unit>-->
Can this be replaced with a solution where the tranlators can exchange the speed unit with the speed number ? I mean currently it expects parameters in %s %i %s order, so there is no way to exchange the parametric parts.
2. With ProjectM addon there is a problem with the quality settings part. There with the spin selection line the localization is not working. In fact it shows the string xml numbers (30001-30004) instead of the actual strings. See ticket http://trac.xbmc.org/ticket/9845
I found out that this addon (unlike others) using a class called DllSetting in xbmc_addon_cpp_dll.h in thw following way:
Code:
DllSetting quality(DllSetting::SPIN, "quality", "30000");
quality.AddEntry("30001");
quality.AddEntry("30002");
quality.AddEntry("30003");
quality.AddEntry("30004");
Somehow the "quality" strings gets translated with the 30000 string, but the spin setting entries they show up as numbers not the actual strings.
I need a little help, where to look for the problems and solutions.
Thanks,
Cheers, Alan