How do we update languages: Transifex <-> Github?

How does the update process of language files work?

We have to directions:
Transifex -> Github
Github -> Transifex

Language files change in both locations independently ...

@ernst: Can you tell us how you handle this?
Also take a look at this issue: github.com/jemproject/JEM-Project/issues/279

This is not only the problem from translaters. It's the problem from the coders too: They should know, where they create new words.

Most words you can find with joomla language decoder. But you only get those words which are inside of a page.
It doesn't find messages and error notices. How to find them in a quick way? Are there instruments?

Well, we know where the strings are added but it can happen that the strings are not added to the language file. At the moment there are probably some untranslated left-overs.

Also it can happen that something had been changed by a dev, and that the translation was not added as things could change. But forget that and did upload the untranslated code( :whistle: ).

But do think that the file at gihub is the leading one as things can be added/changed quickly over there.

Personally, I always add at least a "rudimentary" text in the language files when I introduce new language variables. I think this should always be done to reduce unnecessary work.

But do think that the file at gihub is the leading one as things can be added/changed quickly over there.

I don't know if it is that easy. In the meantime, some strings might have been rephrased etc. So as a result, the files must be merged in both ways.

well, i do know i'm omitting language strings but will try to add them.

Ok guys, some clarification here:

The leading file is (and will always remain) Github. The language file over there should be kept up-to date. Also, new constants should immediately have a text string connected with it. So Diesl's suggestion is best:

I always add at least a "rudimentary" text in the language files when I introduce new language variables. I think this should always be done to reduce unnecessary work.

On a regular basis (at least every time some strings have been added / altered) I take the language file from Github and upload it to Transifex.

Transifex knows that the en-GB language is the source language, so it will add/change any updates into the en-GB language. From there, all translations are automatically updated with all new strings. That is the beauty of working with Transifex. Also, the language co-ordinatior and translators will get a messgage there are new strings to be translated.

So, long story short: ANY changes and additions should be made at Github.

In the future it's even possible to automate the step from Github to Transifex, so that the source language is automatically updated from Github to the Transifex source language.