Joomla has started using Crowdin for its translation projects - https://crowdin.com/projects/Joomla
Granted, this happened only very recently while we've been using Transifex for years, there have been a couple recommendations for moving to Crowdin.
From my own perspective getting things set up for the patch tester and evaluating tools, things I see as advantages are:
Migrating basically means:
get transifex
and update transifex
CLI commands to work with CrowdinThoughts?
Labels |
Added:
language
question
|
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-06-19 16:37:00 |
Closed_By | ⇒ | mbabker |
Status | Closed | ⇒ | New |
Closed_Date | 2016-06-19 16:37:00 | ⇒ | |
Closed_By | mbabker | ⇒ |
Copying in relevant comments from @elkuku on the import/export stuff:
The "percentage completed" values are different on Transifex and Crowdin. I did a quick check on some language files and it seems that Crowdin calculates the "completed" value based on the untranslated words while Transifex uses strings.
Anyway, I believe that all translations should be checked carefully for every language by the respective translators, just to ensure that we do not loose some precious work.
Crowdin does not seem to support po file header informational comments which are supported (and updated) by Transifex. See:
This information is used by our script to generate a list of translators which is included in the credits file. So this wont work anymore.
I've imported all existing translations into the Crowdin project at https://crowdin.com/project/joomla-official-sites so at this point it should be a matter of validating everything transferred over correctly.
We also should try to ping Crowdin to see if there's a way they can expose some of the translator data (at a minimum the headers perhaps or maybe attach some info to an API call) so that all does not get completely lost.
So good news is I was given info that allows us to pull a report from the API to get contributor info. Bad news is that API serves an Excel spreadsheet like this one right here.
What the *
I wonder who paid for that feature...
Not sure if its worth the effort bringing one of those php excel readers in :(
It's not as hard as you might think. I did it which is proof of that
Happy to see a PR
If this was Joomla and not far!work I would give it a go :)
Actually it is Joomla! (~5.0), so no excuse here
In your dreams perhaps
@elkuku
not a single Free Open Source project is paying for using Crowdin and from the point of view of translators (those who are using the more the platform), Crowdin is far ahead (with the Twitter client system) than the 20 platforms I have to deal with every day.
Not perfect, each ones have + and -, but far, far ahead believe me.
About this list, that I still don't know exactly the interest and as I already said: except the "challenge" part for a dev that it must be... I can create a .md, maybe faster than the API to run
No offence please (anyone) I just wondered about that "strange" file format (I'd suspect that's because of a client request but this is not more than speculation of course).....
I think we "solved" this.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-08-04 15:08:01 |
Closed_By | ⇒ | elkuku |
Should I add a + ?
Not being a dev myself, I am unable to, and I don't want to talk about the pros and cons of a tool rather than another from a developer point of view.
However, working everyday on many different t9n platforms and managing different l10n projects, I can certify that today (things changes quickly in this matter), Crowdin is far ahead the other tools from a translator point of view.
The translators' work is easier with also features that improves the quality of the translations. For example, the Crowdin voting system (also used on Twitter Translation Center) allows a genuine exchanges and collaborative work following the Joomla! spirit. In addition, the features offered for project managers allow a better QA/QC than other platforms do today.
Finally, and this may be of interesting for devs, Crowdin is a company that wants to work with J! and move forward with accessible and highly responsive support.