Support / samples on 'equivalent' languages (2-step process)

[fvet]

Related to #74

Hi @rvanbekkum,

Looking for some guidelines on how to achieve the following:

• Our main development language is English.
• After packaging, the g.xliff is created with English captions (this file is never touched)

English (en-US)

• We don't ship a separate en-US.xliff file (which would be a copy of the g.xliff files), since BC falls back on the captions included in the AL source files.

French (fr-BE / fr-FR)

• NOTE: We make no distinction between fr-BE and fr-FR
• Part of the release process is synching any new transunits from g.xliff to the fr-FR xliff files and maintain / review this fr-FR file
• fr-BE uses the caption of its primary language (fr-FR)

Dutch (nl-BE / nl-NL)

• NOTE: We do make a distinction between nl-BE and nl-NL
• Part of the release process is synching any new transunits from g.xliff to the nl-BE xliff files.
• Once the nl-BE xliff files have been updated / reviewed, we would like to sync these new / updated transunits to the nl-NL files, so we can benefit from the nl-BE effort and review/update the new / update translations coming from nl-BE

How can we adopt the settings below to achieve a similar proces?