Centralize localization strings about vscode-nls

[dbaeumer]

For extensions there is a vscode-nls-dev package that helps with managing the files. This has support as well to bundle all strings into one file. See https://github.com/microsoft/vscode-nls/blob/main/src/common/common.ts#L8.

The vscode-nls-dev package also generates a single meta data file containing all English strings and their corresponding keys. The file is called nls.metadata.json.

[HuihuiWu-Microsoft]

@dbaeumer Thanks for your response. I think vscode-nls-dev is to transform all files under i18n folder to meta data file under 'out' file. So according to my understanding, the meta data file is only for running the extension after building the extension. But the strings under i18n folder which is like the source to manage is still distributed in different files. For example, when you add a new string in code, you need to add it to i18n folder and when bug exist, you need to find in all these files under the locale folder.

Same to the English strings, the meta data file contains all English strings but it's generated by vscode-nls-dev, the original English word is somehow hardcoded in code instead of referenced from a single file.

[dbaeumer]

@HuihuiWu-Microsoft as I said in my previous post you can either have single files or one bundle (https://github.com/microsoft/vscode-nls/blob/main/src/common/common.ts#L8.)

vscode-nls-dev extracts strings from the source and generates English files to be translated. vscode-nls allows to use different languages during runtime.

[dbaeumer]

Without the additional information we can't work on this issue. Please ping when the information is available and we will reopen the issue.

Happy Coding