How to create the i18n folder structure automatically using vscode-nls-dev about vscode-extension-samples

[JarrettSpiker]

I posted a similar question to StackOverflow, and after figuring it out (using the above comment) added a step-by-step (ish) guide to getting the i18n-sample working.

https://stackoverflow.com/questions/58294569/automatically-create-i18n-directory-for-vscode-extension/

Hopefully if anyone else is stuck with this that helps move them in the right direction.

It would be great if some more of this especially the format of the translated xlf file was spelled out in the readme for i18n-sample

[dbaeumer]

@DonJayamanne

Regarding Q1: none of your tools force to use a special translation platform. So it is up to you to decide how these strings are translated. All the tooling does is to assume that there is a i18n folder with sub folder per language were the folder name uses ISO 639-3 convention. Underneath these folders the directory structures is the same as for the source code. If you are using Transifex to translate the project then vscode-nls-dev provides gulp functions to automatically push and pull to Transifex honoring the directory structure. If you choose to use your own translation platform you need to write your own import / export scripts. See https://github.com/Microsoft/vscode-node-debug2.git for an example that uses Transifex.

Q2.: https://github.com/Microsoft/vscode-node-debug2.git is again a good example.

I am closing the issue. Please ping if there something is still unclear.