Problem

Some TMX files of users may have combinations of languages for tuv.

We already have a pre-processor that checks for such nodes and removes them from TMX.

But in reality user may not care about sub-languages as example.

So if language resource set to de -> en pair user may want to "merge" values for de-de -> en, de -> en-gb, de -> en-us etc.

Solution

To achieve that we have to introduce new pre-processor that will check sub-languages and major languages and instead of deleting nodes change language in them to fit Language resource pair.

In frontend we will add checkbox to import TMX window to let user decide on import what he wants to do.