Use the xliff specify in the messageLocations as source and auto generate the target translation xliff based on the given translationFileNamePattern Įdit directly on the target xliff (based on the messageLocations and the given translationFileNamePattern)Įditor.emptyTranslationHandling: 'delete' | 'keep' | 'fallback-to-source'ĭetermine how to handle empty translation. is the consist parts of LCID editor.mode: 'default' | 'target-file' The locales setting accepts one ore more target locales that your application is going to be translated into. The editor.taskConfig is to control the background task manager, which executes the transunit saving commands. The editor setting is to control the behavior of I18n editor as well as the background task manager. The following is the configuration options: Path Extension SettingsĮxtension setting is a json file that placed in the root directory of the workspace, using the name. ![]() This extension will only be activated when the extension setting file is under your workspace root directory. This feature is on the roadmap but not yet started. Translation memory is to store your tranlation history and will give you suggestion for your transunits. This will help you write better translations. The code context shows the location where the translation will be apply to. Translations that mark as signed-off could not be edit in the editor, unless you unlock them. Save and Lock Your TranslationĪfter you translated one trans unit, you can click ctrl + enter to save and lock ( signed-off) your translation. ![]() This extension provides a friendly to use editor for users to translate their apps. If you're struggling handle the xliff files that generated by AngularCLI, this extension might be helpful for you. This extension provides an editor for Angular generated xliff file. Anglar I18n Editor for VSCode ( vscode-ng-i18n-editor)
0 Comments
Leave a Reply. |