You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, since #100 we also have a new setting "xliffSync.parseFromDeveloperNoteTrimCharacters" that should be supported by the tTranslations snippets.
Also, something that I have also considered is making a "xliffSync.snippetTargetLanguages": [] setting, which will replace the xliffSync.snippetTargetLanguage after some time, but they should be able to both work, at least for quite some time, i.e., if the first setting is not empty, that will be used, otherwise, the existing setting will be used.
The tTranslations snippets are conditionally generated, respecting the "xliffSync.snippetTargetLanguage"
Example
"xliffSync.snippetTargetLanguage": "nl-BE",
Resuls in
Caption = 'CaptionText', Comment = 'nl-BE=Translation';
However, since #100 we also have a new setting "xliffSync.parseFromDeveloperNoteTrimCharacters" that should be supported by the tTranslations snippets.
Example
"xliffSync.parseFromDeveloperNoteTrimCharacters": "\"",
Resuls in
Caption = 'CaptionText', Comment = 'nl-BE=Translation';
Where the expected result would be (=> adding the extra charachter(s) - e.g. " - from parseFromDeveloperNoteTrimCharacters)
Caption = 'CaptionText', Comment = 'nl-BE="Translation"';
(*)(*) This allows the developer to quickly add translations in code via Google Translate in VS Code
The text was updated successfully, but these errors were encountered: