Hey Thomas,
1. Yea, I know. The thing was - TX didn't offer any version number and I had to calculate one myself - so I decided to omit it for version 1.

2. This is actually a long term goal! But the component needs to grow a lot for this to happen. First of all I'll need to write a library to enable devs to install the languages right from the backend of their extensions. And at that time the component should have the code necessary for the updateserver to work.

Regards,
Daniel

Hi Daniel

Installing from the component backend would be awesome as well. I'm looking forward for your next releases then :-)

I was thinking a bit about it.
I think it would be sufficient if CTransifex can generate an XML output which we could read from a backend view in our extension. It shouldn't be that hard then to write a view which lists the files from the XML in a form which calls the installer on click.

For the updateserver maybe it would be nice to have an integration for the ARS component from Akeeba. ARS supports automatically creation of the repository and also offers automatic created updatestreams. So it would be sufficient if CTransifex could put the files into the ARS directory and generates subdirectories for each release (version named like 2012.11.26.20.29 which would be compatible with version_compare). Then ARS will pick that up.
Not sure if it would work though, but I would like the idea of not inventing the wheel again