XBMC official translation project for release Frodo is open !

Great Today I'll update any new string for Polish language.

@allanwww1
I can remember we could review the current translations however I can't find that option anymore.

Any idea when we can add other add-ons?

(2012-05-31 13:20)Martijn Wrote:  @allanwww1
I can remember we could review the current translations however I can't find that option anymore.

Any idea when we can add other add-ons?

You can review all strings next to the entry on the right. There is also an option of bulk review the strings on the same page.
This functionality is really useful for coordinators. What I did for example (as a Hungarian team coordinator) is to mark ALL previous (imported from xml) strings reviewed. So from now on I can always see the newly added translations by team members and approve it or revert it. There is a history kept for ALL strings where you can choose to revert to any previous revision for the string.

About other addons, I still have some tools to code. To extract, assemble addon description, summary disclaimer for example (Well the sxtract part is ready) So I am hard working on it but I have only got free time after work mostly at nights :-) So I'd like to ask everyone to be patient with this a little. I'd estimate a 2-4 weeks from now.

Edit:

User Mad-max is preparing a really great Wiki page on Transifex usage. It will be really helpful for all translators.

(2012-05-31 13:32)alanwww1 Wrote:  

(2012-05-31 13:20)Martijn Wrote:  @allanwww1
I can remember we could review the current translations however I can't find that option anymore.

Any idea when we can add other add-ons?

You can review all strings next to the entry on the right. There is also an option of bulk review the strings on the same page.
This functionality is really useful for coordinators. What I did for example (as a Hungarian team coordinator) is to mark ALL previous (imported from xml) strings reviewed. So from now on I can always see the newly added translations by team members and approve it or revert it. There is a history kept for ALL strings where you can choose to revert to any previous revision for the string.

About other addons, I still have some tools to code. To extract, assemble addon description, summary disclaimer for example (Well the sxtract part is ready) So I am hard working on it but I have only got free time after work mostly at nights :-) So I'd like to ask everyone to be patient with this a little. I'd estimate a 2-4 weeks from now.

Edit:

User Mad-max is preparing a really great Wiki page on Transifex usage. It will be really helpful for all translators.

ah dam i found it. Clicked on view strings instead of translate now.

Sure we will have patience. I was just curious

The occurences field seems to empty for almost everything. You know about this alan or is it an error? Actually, I can only find a single string that has it: the one shown on the wiki page..

(2012-06-01 15:10)takoi Wrote:  The occurences field seems to empty for almost everything. You know about this alan or is it an error? Actually, I can only find a single string that has it: the one shown on the wiki page..

This and the commenting is a brand new "feature" which comes from the new PO format we use. We try to fill out these helper strings for future strings and also make some comments for older strings which are hard to understand without a comment.

Also plural forms are coming to the translations soon (my next gig task to do :-) )

(2012-06-01 19:18)alanwww1 Wrote:  

(2012-06-01 15:10)takoi Wrote:  The occurences field seems to empty for almost everything. You know about this alan or is it an error? Actually, I can only find a single string that has it: the one shown on the wiki page..

This and the commenting is a brand new "feature" which comes from the new PO format we use. We try to fill out these helper strings for future strings and also make some comments for older strings which are hard to understand without a comment.

Also plural forms are coming to the translations soon (my next gig task to do :-) )

So the paths are manually typed? I imagine those will quickly get unmaintained. This could be generated. like gettext does..

(2012-06-01 20:13)takoi Wrote:  

(2012-06-01 19:18)alanwww1 Wrote:  

(2012-06-01 15:10)takoi Wrote:  The occurences field seems to empty for almost everything. You know about this alan or is it an error? Actually, I can only find a single string that has it: the one shown on the wiki page..

This and the commenting is a brand new "feature" which comes from the new PO format we use. We try to fill out these helper strings for future strings and also make some comments for older strings which are hard to understand without a comment.

Also plural forms are coming to the translations soon (my next gig task to do :-) )

So the paths are manually typed? I imagine those will quickly get unmaintained. This could be generated. like gettext does..

A tool for this is welcome !
I might write one later, if I have time, but I still have a lot other stuff to finish.

(2012-06-01 20:50)alanwww1 Wrote:  

(2012-06-01 20:13)takoi Wrote:  

(2012-06-01 19:18)alanwww1 Wrote:  This and the commenting is a brand new "feature" which comes from the new PO format we use. We try to fill out these helper strings for future strings and also make some comments for older strings which are hard to understand without a comment.

Also plural forms are coming to the translations soon (my next gig task to do :-) )

So the paths are manually typed? I imagine those will quickly get unmaintained. This could be generated. like gettext does..

A tool for this is welcome !
I might write one later, if I have time, but I still have a lot other stuff to finish.

Could probably make something that does the most common cases, but this would be a lot easier if string keys were done first. Then its just a simple search..

Since you mentioned plural and special plural support is the next step there's a couple of things I find, as a translator, will make it a lot easier to work with the translations, perhaps more than the occupational lack of plural. A basic context, like a path to the file it occurs, is on top of my wishlist, because the english language have so many different meanings it's almost always impossible to make a proper translation without searching the source code or opening up xbmc trying to find it. If you don't, it's just a wild guess. It leads to bad translations not knowing the context. To sum up:

- All strings should have a context description. A path to the file is fine
- There's string reuse a lot of places it shouldn't. It's causing bad translations and breaks geometry.
- String tokenization. It should never be done. No exceptions. Xbmc has a lot of these, and I've even seen it being added new one recently. Perhaps this haven't been communicated..
- A lot of unused strings (string keys will fix this)
- The whole weather thing