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
{{ message }}
This repository was archived by the owner on Apr 19, 2024. It is now read-only.
We use createXlfFiles to generate ENU xlf file from 'package.nls.json', 'nls.metadata.header.json', and 'nls.metadata.json' files. Our loc team uses this ENU xlf file to produce translated xlfs.
The issue is that we have to have <note> elements in the trans units in our ENU xlf to pass instructions to the loc team, and createXlfFiles() just overwrites the ENU xlf, losing all the notes.
We had to work it around by getting the notes from the existing ENU xlf file first, and then applying them in our copy of createXlfFiles() as in this PR
I think this is a common scenario to be enabled in vscode-nls-dev
We use
createXlfFilesto generate ENU xlf file from 'package.nls.json', 'nls.metadata.header.json', and 'nls.metadata.json' files. Our loc team uses this ENU xlf file to produce translated xlfs.The issue is that we have to have
<note>elements in the trans units in our ENU xlf to pass instructions to the loc team, andcreateXlfFiles()just overwrites the ENU xlf, losing all the notes.We had to work it around by getting the notes from the existing ENU xlf file first, and then applying them in our copy of
createXlfFiles()as in this PRI think this is a common scenario to be enabled in
vscode-nls-dev