Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test localization Support #2228

Closed
3 tasks done
dbaeumer opened this issue Jan 25, 2016 · 3 comments
Closed
3 tasks done

Test localization Support #2228

dbaeumer opened this issue Jan 25, 2016 · 3 comments

Comments

@dbaeumer
Copy link
Member

The January drop ships with localization support for the main, the renderer, the service (search app, shared service, ...) and the extension host processes. Also pseudo localization is supported. Test the following:

Pseudo localization

  • start VSCode from a command line with the argument --locale=pseudo
  • verify that all strings in the UI are enclose in [ ] and that vowels are doubled. The UI should look something like this:

capture

Localization Tools

Import new strings into the translation database

  • build VSCode locally (e.g. execute gulp vscode-win32). Assume that VSCode got built into p:\mseng\vscode\VSCode-win32
  • clone the VSO git repository mshttps://monacotools.visualstudio.com/DefaultCollection/Monaco/_git/MonacoLocalization
  • cd to the MonacoLocalization directory and run npm install
  • cd to lib, run npm install and cd to parent
  • make sure you have gulp install globally
  • run gulp import --component vscode/src --locData ${vscode-build}\resources\app\out\nls.metadata.json where ${vscode-build} is the folder vscode got built into (e.g. p:\mseng\vscode\VSCode-win32)
  • ensure that some lcg and lci files got modified and added. Compare some of them. Modified files should contain new strings introduced lately, new files correspond to new files introduced lately.

Export bundles from the translation database

  • from the MonacoLocalization directory execute gulp export --component vscode/src --locData ${vscode-build}\resources\app\out\nls.metadata.json --dest ${vscode-build}\resources\app\out
  • ensure that ${vscode-build}\resources\app\out\vs\workbench contains files like workbench.main.nls.de.js

Translated Version

  • start the VSCode version you have built above with --locale=de
  • ensure that parts of the UI is in German (parts of the UI is still English because we are mssing the corresponding translations from the translation team)
  • switch your OS locale to German and start VSCode without the --locale command line parameter. Ensure that the UI is partly German
  • start VSCode with --locale=de-DE. Ensure that the UI is German as well.

capture

@egamma egamma mentioned this issue Jan 25, 2016
59 tasks
@bpasero bpasero added this to the Jan 2016 milestone Jan 26, 2016
@isidorn
Copy link
Contributor

isidorn commented Jan 26, 2016

Could not change my win locale no matter what I tried - i believe my win10 internal version might not support it.
Eveything else looks good, and Dirk tested the win10 in german so checking off.

@aeschli
Copy link
Contributor

aeschli commented Jan 26, 2016

Alle Schritte auf Linux getestet. Läuft wie geschmiert!

@bpasero
Copy link
Member

bpasero commented Jan 28, 2016

Works, but found #2495

@bpasero bpasero closed this as completed Jan 28, 2016
@egamma egamma mentioned this issue Feb 1, 2016
97 tasks
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants