State of the translation

alanwww1 Wrote:Hi Viljo !

I made some tests with Transifex. I tried it with fedora 16 and Centos 6.2.

...

Should I send you the VirtualBOX files for testing ?

Cheers, Attila

I don't have virtualbox installed anywhere and the image files are unnecessarily large anyway...

I'll take a look at setting up transifex on my amazon ec2 server.

alanwww1 Wrote:@Viljo

I think we should try Transifex and Pootle in real life situation.

I've just tried Pootle and the interface is a little simpler, but seems more stable and with much less fuss to install. Well actually it was:

Code:

yum install pootle.noarch
PootleServer --port=8000

It makes a demo (Gnome) translation project this way which you can test.

Also if we can not use xml as a native format, I checked that we can you XLIFF instead of POT. It has an ID based structure, similar to xbmc and Context hints can be inserted easily. XLIFF is well supprted by both Transifex and Pootle.

But does pootle have an api? I still think doing the integration directly with transifex api would make many things quite easy and straightforward as opposed to converting both ways...

So guys, lets just take a step back and think about the real issue here. I just need this to being said: The core to all of the problems discussed in this thread remains the same: the poor internationalization support in xbmc. Even if someone were to write the parser/converter/infrastructure and all that you're still stuck with a program where lot of parts aren't even internationalizationable. For this to happen the key/value xml system needs to go in favor of a proper i18n tool. It most definitely isn't going to be an easy task, but it needs to be done sometime.
My point is: if this were to be done, then everything else discussed here will fix itself. All the tools for translating, syncing, deploying are already in place.

ventech Wrote:So guys, lets just take a step back and think about the real issue here. I just need this to being said: The core to all of the problems discussed in this thread remains the same: the poor internationalization support in xbmc. Even if someone were to write the parser/converter/infrastructure and all that you're still stuck with a program where lot of parts aren't even internationalizationable. For this to happen the key/value xml system needs to go in favor of a proper i18n tool. It most definitely isn't going to be an easy task, but it needs to be done sometime.
My point is: if this were to be done, then everything else discussed here will fix itself. All the tools for translating, syncing, deploying are already in place.

I think you are absolutely right.

But if we want results now, as opposed to in 5 years, we're gonna have to go the quick and dirty way, converting.

Anyway when we have the system, switching it to use the proper tool will be very easy.

And I'd be willing to try to go the "native transifex" way, i.e. using directly the api. Actually I'm just gonna try it, cos I like tinkering with apis

@ventech: I don't think that changing the translation system in xbmc would be easy. First there are the strings which are translated token-based with xml query. Also the addons coming in with a python framework. I don't think that developers would agree to this, but I can ask their opinion.

viljoviitanen Wrote:And I'd be willing to try to go the "native transifex" way, i.e. using directly the api. Actually I'm just gonna try it, cos I like tinkering with apis

Please let me know your results with the GUI. I had some glitches with both versions I tried. I am sure we need to tweak the installation and settings, but documentation is not too detailed. I guess because of their not free support service :-) I am sure it can be set up correctly as at transifax.net with the paid service they are using the verison 1.2.1 with no problem: https://www.transifex.net/projects/p/100...l/hu/view/

alanwww1 Wrote:Please let me know your results with the GUI. I had some glitches with both versions I tried. I am sure we need to tweak the installation and settings, but documentation is not too detailed. I guess because of their not free support service :-) I am sure it can be set up correctly as at transifax.net with the paid service they are using the verison 1.2.1 with no problem: https://www.transifex.net/projects/p/100...l/hu/view/

I too have some problems with the installation, there are some missing files. Also I have other problems with it.

I'll email you the details of installation... let's continue private for a while.

Ok, I've been working with the "hosted" transifex at

https://www.transifex.net/projects/p/mytest55/

It's now looking quite good, I could add all translations with the api but I only did a few just to show what's possible.

The translations strings in that test project are not from current git, but from some old version I had on my hard disk.

The tool to convert XBMC strings.xml to "transifex compilant" xliff is at https://github.com/viljoviitanen/Simple-...texliff.py

The "catch" was to realise transifex uses internally a hash of source string and "context". To see how that works, search e.g. for "programs" at any translation.

Updating/uploading a translation can be easily done with curl, here I uploaded swedish core translation:

This could be bound to a github webhook that checks if a translation has been updated there and push the change immediately to transifex. Here we'll need a mapping of all possible xbmc languages to transifex language codes, e.g. Swedish->sv.

Also, a change in transifex can be detected via a webhook and then the updated file could be pushed immediately to git (we'll need a reverse of the previous map).

I still don't know how the translation memory thing in transifex works... and the also should support for a "glossary" where xbmc specific terms can be collected from core translation to benefit addon translations.

http://help.transifex.net/intro/translat...ion-memory

I think you need to "own" the translations. Then you can choose to share, but only among the projects you own. It's seems very limited..

(go to your dashboard->translation memory and you can see it there)

Very promising news. Good work.

I wonder anybody from XBMC developers tried to contact with Transifex devels? Maybe they can offer help, write a code for us or even they can offer to XBMC free project space? Good things happen between one open source community to other