I believe that the cause might be that the language files are not complete yet
Please have a look at this page: https://opentranslators.transifex.com/projects/p/jtracker/ and note that the dutch translation is actually only 35% completed.

If you look close there should be already some dutch words here and there... e.g.:

Could this issue be resolved by completing the language files on Transifex ?

You are correct, the Dutch language files are incomplete. I just assumed if the language was offered it would be complete ;) I have requested to join the translation team. Thanks.

Dutch language files updated, now just waiting to have them reviewed.
You may blame the J!Tracker Application for transmitting this comment.

Thanks Roland! I entusiastically started translating it, but then moved on and left it on my todo-pile, deeper and deeper, sorry. You've translated it very quickly! Don't wait for a review: that is normally not done in Dutch projects on OT (no reviewers). But that doesn't matter: you can still use the files. Thanks for translating!

@Herman - just for information, reviewing isn't just done by reviewers - that's why they are such large teams :) Peer reviews are also very important.

@all Just a note: I believe that you have also received a complete Danish translation today.

Is it now time for OT to advise the translators that the project is ready for translation?

Hils

Thank you, Hils, I know it and I also will review the strings Roland made (especially to make it more consistent with the way Joomla is translated in Dutch), but AFAIK I have no rights to mark the strings as reviewed. In other Transifex-projects I participate in (outside OT) when strings are reviewed by a reviewer or team manager, they cannot be just changed by any translator. It is not as critic on OT, for it works OK: when anybody takes the trouble to go over strings to correct them, then they generally improve it, so it works OK. My remark for Roland not to wait for review was to not wait for the files to be marked as reviewed.

Having my translations reviewed might be good for consistency. There is one area I tried to stick with suggested translations as I am not sure which way to go. This is a good example:
Add issue
Do we translate this as:
Voeg probleem toe
Probleem toevoegen
Toevoegen probleem

Which of the three ways is supposed to be used ? ;)

Thanks Herman! I come in peace and definitely not doing a PR job on ot. It is slightly different in Transifex - yes there are co-ordinators (can be several per project) and reviewers but there is also the crowd translate 'thing' too.

A translator can make a 'suggestion' in a comment like we are doing here but in addition, other translators can vote for the suggestion, or not. Screenshot from a test project not a real one!

Wow @roland-d... or you are a blazing fast translator, or Transifex's UI is awesome - or both

I just updated the language files (and credits) in the repo, let's wait for them to get deployed to the server - awesome job !

@Hils

Is it now time for OT to advise the translators that the project is ready for translation?

I would vote for yes, hope that's OK with @mbabker ?

@Hils yes, peace & love, realy mean it. Thanks. Let's make things better!

@roland-d second option is most consistent with core Joomla translation: hele werkwoord achteraan. Andere regel die in core Joomla steeds consequent toegepast is: beleefdheidsvorm u i.p.v. je/jij. Ook: woorden vaker aan elkaar dan in Engels, Alleen in begin hoofdletter, als verderop in tekststring dan alleen als eigennaam. I'll e-mail you some of those directives for Dutch translations. We used them also for Seblod (on Transifex), in which many of Joomla's core language strings are defined again... We also have a (start of a) dictionary with much used words, but I'll have a look if I can put them in the Dutch OT space too.

Here is a link to some directives (in Dutch) used to translate Joomla's core:
http://taal.joomlacommunity.eu/Hoofdlettergebruik
And here the start of a dictionary with some much used words:
http://taal.joomlacommunity.eu/Categorie:Woordenboek
I find both useful to stay consistent. Will have a look what I can put into OT of it.

@Herman - would it help the Dutch Team if I added you as a Reviewer?

We've been "ready" since the day we listed on Transifex IMO. Just note
that the overall project is still in a beta state, so changes may come
accordingly based on that.

On Sat, Apr 26, 2014 at 8:55 AM, Nikolai Plath notifications@github.comwrote:

Wow @roland-d https://github.com/roland-d... or you are a blazing fast
translator, or Transifexe's UI is awesome - or both [image: ]

I just update the language files (and credits) in the repo, let's wait for
them to get deployed to the server - awesome job !

@Hils https://github.com/Hils

Is it now time for OT to advise the translators that the project is ready
for translation?

I would vote for yes, hope that's OK with @mbabkerhttps://github.com/mbabker?

—
Reply to this email directly or view it on GitHub#341 (comment)
.

Very cool guys to see it all in Dutch now (even though we type in English).

There is one issue I see that may be because it is not in the language files. If you look next to a persons name it says comment, this is a link. This should be translated as well. Is this something that can be translated?
You may blame the J!Tracker Application for transmitting this comment.

Just to add to this, I see more English strings appear in different places, could it be that the English language file is not complete?
You may blame the J!Tracker Application for transmitting this comment.

The templates are generated based on the layouts; if they aren't using the translate method then they don't get picked up by the script that compiles it all. So, there's a chance there's some places where this is the case.

I see, is this something we should check/investigate?

Yes. If you have some time and would like to, each of the layouts in the templates folder should have all displayed text wrapped in a translate call like is done at https://github.com/joomla/jissues/blob/master/templates/tracker/issue.edit.twig#L33.

Just a remark - for consistency we should use not translate but |_:

{{ "Issues List"|_ }}

See an example here

Another remark: After updating the language files, the cache must be cleared (via the admin menu System => Clear Cache or by removing the cached files) !

@roland-d if you encounter any hard coded strings, a screenshot might be useful

I think this "issue" has been resolved, closing.