New Functions Trans-XliffTranslations #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi Tomáš, Thank you for your pull request! Kind regards, |
|
Thank you again. I have merged the changes which are now shipped in version 1.2.0.0 which has just been released! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Rob,
I created new function Trans-XliffTranslations.
This function uses already translated xlf files as "Translation Base".
This function supports multiple source files and multiple target files.
With this "Translation Base" translates files target files.
Translation from "Translation Base" is used only if it is unique.
This is useful when you need to re-use already translated texts...
Source files = translation base files
Target files = files that need to be translated
BR
zabaq