it-ony / grunt-merge-locales Goto Github PK

Hi,

In a living project it might happen that you have to change the meaning of an (already translated) item in the source. So you do the change in the source file (typically english). But the change does not propagate to already translated items.

It would be great if I could somehow "force" a retranslation, by marking some items (e.g. by prefixing the value with '???'). The so marked lines should then propagate to the target files:

• Replace the already translated stuff
• or prefix the new stuff

By doing so, the translating persons have a marker (e.g. '???') to search for items that need a review. And the developer has a method to trigger a review by the translators.

Example:

en

{
"key1": "foo switches off something"
}

was already translated to

de {
"key1": "foo schaltet etwas aus"
}

Now the developer detected, that there was a mistake in the documentation and changes the meaning of the english text.

en

{
"key1": "foo switches ON something"
}

But this will not propagate to the translators as the text was already translated. The already translated meaning will not update -> Bad. If merge-locales detects the change in the english version, it could update the translated file.

de 
{
"key1": "???(foo switches ON something)???foo schaltet etwas aus"
}

The guy translating the file searches for ??? and can identify the items to review.

By the way: You could also prefixing "untranslated" or "new" items with '???' - this will also help translators to identify lines that need translation easily (so they don't need to scan big file from the beginning and look for a different language in all the text manually - which is error prone and annoying)

kind regards

Andreas