XBMC official translation project for release Frodo is open !

(2012-06-03 01:43)jmarshall Wrote:  Right - we can't yet replace msgctxt with something useful as we're still using the id's, so this is an interim measure.

Yes, it will only be changeable for regular Gettext calls. But I think using the coinsurance and comment fields we can have what we want.
And those fields are showing up nicely in Transifex as well.

(2012-06-03 01:05)alanwww1 Wrote:  

(2012-06-03 00:33)jmarshall Wrote:  @takoi: It wouldn't surprise me if it was that high. What would be a huge help is for the contexts to be done for all the strings you found - once the context clearly indicates where it's used, it's both useful to the translator (as you know where to look to see whether things fit etc) and also useful for developers when removing/replacing old strings as they know they are unused now. You can fill in something like "unused" for the ones that aren't done and I'm sure that Jezz_X will be happy to take a hunt through and confirm that they're unused, thus removing them.

Obviously this is a large job, but if everyone pitches in and just does a few each (just let us know which block you're doing), it won't take long before the whole lot are done.

I am planning to write a parser utility to extract at least the occurence of the string calls. The tricky thing is that we have several ways of passing the string id to the localization function. Sometimes it comes from a direct parameter, but sometimes it comes from an xml file or from other indirect calls.
So whenever I have time for it, I'll try do it.

This is a perfect example of why string keys are so important.

If everything is moved to strings (wrapped with direct calls) you have essentially moved from maintaining a .pot file to generating. Like gettext does. The unused string problem is solved. The extract occurrences problem is solved.

Maybe a temporary solution (before the id to string move is done) could be a simple file storing all the id to string mappings. Then, the English .po template is generated by extracting the IDs from source code and looking up the string in that file (since you're planing to write that parser tool anyway)?

So I made a quick script doing a plain text search with these assumptions (tell me if this isn't correct):
- searching only in xbmc and addons subfolder
- searching only h, cpp and xml files

..which found a whopping 448 unused strings. And this is an absolute minimum as there's probably a lot of false positives because it's just a simple substring search.

(2012-06-04 16:09)takoi Wrote:  So I made a quick script doing a plain text search with these assumptions (tell me if this isn't correct):
- searching only in xbmc and addons subfolder
- searching only h, cpp and xml files

..which found a whopping 448 unused strings. And this is an absolute minimum as there's probably a lot of false positives because it's just a simple substring search.

Thanks for the search.
The only thing which needs filtering from the unused strings AFAIK is the weather tokens which are not directly used. The IDs are from Weather.cpp


I am not sure, but also it is possible I think, that third party addons and/or skins are using some strings in the core file which are not in use by xbmc core itself. I need a team member who is better aware of addons to confirm or deny this.

the plan for a few years ago was to add regularly used add-on strings to core translation in an effort to ease the burden on the translators. there might still be a few one used there.

(2012-06-04 19:40)blittan Wrote:  the plan for a few years ago was to add regularly used add-on strings to core translation in an effort to ease the burden on the translators. there might still be a few one used there.

As we have the translation memory working now, I think it is not so a big issue. So if possible, would be good to make a big clean up :-)

Ultimately it's a good thing because addons shouldn't be using strings that cant be changed by translations anyway. It creates more problems than it solves.

There are problems with touched skin translation (at least for Slovenian translation). All special letters (like č, š, ž) are replaced wih ?. I think this are strings that have already been translated before the import. Could you please look into it.

(2012-06-06 18:52)ntadej Wrote:  There are problems with touched skin translation (at least for Slovenian translation). All special letters (like č, š, ž) are replaced wih ?. I think this are strings that have already been translated before the import. Could you please look into it.

Unfortunatelly it was originally broken in the xml file:

https://github.com/xbmc/skin.touched/blo...trings.xml

Could you please correct it on transifex ?

Thanks

No problem, just wanted to point it out, if there are other problems present.