search

daniel-sc / ng-extract-i18n-merge

Extract and merge i18n xliff translation files for angular projects.
MIT License
170 stars 18 forks source link

Option to never remove existing translations #105

Open timvandesteeg opened 6 months ago

timvandesteeg commented 6 months ago

First of all, thank you for creating this very handy library!

I'm using a monorepo with NRWL with multiple angular apps. Currently I'm using one translation file per application, but since there is a lot of overlap, I'd like to merge all translation files into one targetFile having all translations for all apps.

Currently, if I extract-i18n for application 1, the unique translations for application 2 are removed. For example, say that application 1 has a trans-unit for 'Text A' and application 2 has a trans-unit for 'Text B', i'd like to have a combined targetFile with both 'Text A' and 'Text B'. Now it's either one or the other due to the merge logic.

Is there a workaround to support this use case? Or is it possible to add a configuration option to never remove existing nodes in the targetFiles?

daniel-sc commented 6 months ago

@timvandesteeg I understand your intention, but in case an option "neverRemoveExisting" would exist - how would you handle acutally removed translations in your intendet setup? (For me, the cleanup of removed text is almost as important as the merging of existing translations :D )