0.4.0

Changes

• New setting xliffSync.syncCrossWorkspaceFolders which can be used to set that the extension should synchronize from one single base file (xliffSync.baseFile) to the translation files in all workspace folders (Default: false) (GitHub issue #48).
• Now, if there are multiple matches for xliffSync.baseFile, then the user is prompted to select the base file to use.

0.3.8

Changes

• New setting xliffSync.parseFromDeveloperNoteOverwrite which when enabled will overwrite existing translations with the translations parsed from the Developer Note.
• New setting xliffSync.copyFromSourceOverwrite which when enabled will overwrite existing translations with the source text.
• The "Parse from Developer Note" feature will now also update translations if xliffSync.missingTranslation is configured to something other than the default value (which is missing translation = no translation).
• XLIFF Sync snippets for the "Parse from Developer Note" feature.
  • You can configure for which programming languages the snippets should be available with setting xliffSync.enableSnippetsForLanguages. Currently only the "AL Language" is supported with snippets: tcaptionwithtranslation, tcommentwithtranslation, toptioncaptionwithtranslation, tpromotedactioncategorieswithtranslation, tlabelwithtranslation and ttooltipwithtranslation snippets.
  • You can configure a default target language that should be used by the snippets with setting xliffSync.snippetTargetLanguage.

0.3.7

Changes

• New setting xliffSync.detectSourceTextChanges (see README)
• New setting xliffSync.ignoreLineEndingTypeChanges (GitHub issue #41)
• New setting xliffSync.copyFromSourceForLanguages (GitHub issue #44)

0.3.6

Changes

• Only apply decorations in XLIFF files (not in every editor) (GitHub issue #39)
• Reload settings (i.e., "xliffSync.decoration", "xliffSync.decorationEnabled", "xliffSync.decorationTargetTextOnly", "xliffSync.missingTranslation") when switching active editor
• Add new setting "xliffSync.decorationTargetTextOnly" to have decorations only be applied to the target node's text, if enabled.
• Change highlight-update interval from 1 to 500 (ms)

0.3.5: Parse from Developer Note (#38)

Changes

• Added new setting xliffSync.parseFromDeveloperNote (default: false) to have translations parsed from the Developer note if no matching trans-units or translations can be found. Translations can be retrieved from a Developer note in the following format: en-US=My translation|nl-NL=Mijn vertaling (GitHub issue #37).
• Added new setting xliffSync.parseFromDeveloperNoteSeparator (default: |) accompanying setting xliffSync.parseFromDeveloperNote to change the separator for translations.

0.3.4: Default value for basefile setting to .g.xlf (#36)

Changes

• Changed default value for setting xliffSync.baseFile to .g.xlf (GitHub issue #34)

0.3.3: Notification/Toast to show Sync in Progress (#32)

Changes

• Added notification that shows that an XLIFF Sync is in progress. This notification includes the name of the target file for which a sync is in progress.
• Added new setting xliffSync.decorationEnabled that can be used to disable decoration/highlight of missing translations and translations that need work in XLIFF files.

0.3.2: Merge pull request #30 from rvanbekkum/feature/29-placeholder-dev-note

Changes

• Added the following new technical check (disabled by default):

  • PlaceholdersDevNote - Checks that the meaning of placeholders are explained in the Developer note.

• Added new setting xliffSync.needWorkTranslationRulesEnableAll to enable all available technical validation rules. If you want to use all rules including those that will be added in the future, you can use this setting. (Default: false)

• Fix: The XLIFF Sync note would only be removed for the first trans-unit where a problem is resolved. From now on, the XLIFF Sync note will be removed directly from all trans-units where the problems are detected to be resolved.

0.3.1: Merge pull request #28 from rvanbekkum/feature/25-consecutive-spaces

Changes

• Fix remove duplicate language tag entry ja-JP which shows up calling XLIFF: Create New Target File(s).

• Changed XLIFF: Create New Target File(s) command adding two options Select multiple.. (to select multiple target languages to create a file) and Enter custom... (to enter a custom target language tag).

• Added the following new technical checks (disabled by default):

  • ConsecutiveSpacesConsistent - Checks that the 'consecutive space'-occurrences match in source and translation.
  • ConsecutiveSpacesExist - Checks whether consecutive spaces exist in the source or translation text.

0.3.0

Changes

• Added support for multi-root workspaces. You can configure settings per workspace folder. The commands of the extension will run for all workspace folders by default, but if you have a file opened in the editor from a workspace folder, then the commands will only run for the XLIFF files in that workspace folder.
• Added new command XLIFF: Create New Target File(s) which can be used to create new target files. If you run this command then you will get a list of language tags for the XLIFF file type that is used in the workspace folder. You can choose one or more language tags from this list, and the command will create new files for the selected languages accordingly.
• Small fix in the file-type quick pick list.
• When command XLIFF: Synchronize to Single File is run, the check for missing translations and problems will only be run for the single target file when xliffSync.autoCheckMissingTranslations and/or xliffSync.autoCheckNeedWorkTranslations are enabled. Also, these checks won't be run for newly created target files (as they won't have any translations).