Change:
update from This is happening because our built-in extension vscode-references-view has never supported translated string. The fix for this is having vscode-references-view adopt vscode-nls. original issue text Issue Type: <bBug</bOpen a Json file, right click: a part of menu is in English VS Code version: Code 1.64.0 (, 2022-02-03T04:22:04.495Z) OS version: WindowsNT ia32 10.0. Restricted Mode: No <details<summarySystem Info</summary </details<details<summaryExtensions (15)</summaryExtensionVersion ------ turbo-console-log2.1.7 gitlens11.7.0 json-tools1.0.2 git-graph1.30.0 prettify-json0.0.3 vscode-language-pack-fr1.64.6 anaconda-extension-pack1.0.1 python2022.0. vscode-pylance2022.2.0 jupyter2022.1. jupyter-keymap1.0.0 jupyter-renderers1.0.6 vscode-json-editor0.3.0 vscode-yaml1.4.0 json2.0.2 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
<img width="509" alt="bugvscode04022022" src="https://user-"
I am seeing the translations now, they might have taken a little bit of time to apply. Can you check again? If it still doesn't show can you restart VS Code?
Hi, it is partially ok now. I restarted VS code. It remains the same. I attach a screenshot with the part of commands that remain in English. [image: ] Le sam. 5 févr. 2022 à 02:12, Tyler James Leonhardt < écrit :
can you upload the screenshot via the website? It doesn't work when you upload from email. are you also seeing this?
On Insiders, it is only the "Commit Changes" option and submenu that doesn't seem to be translated yet. It is from an extension, but I'm not sure which one. !
<img width="254" alt="bugvscodetrad" src="https://user-"
I published a new version of the language pack yesterday. Can you check once more?
I don't have any updates available yet. I restarted VS. The lack of translated commands is still there. Le jeu. 17 févr. 2022 à 23:46, Tyler James Leonhardt < écrit :
That section still hasn't been translated. Tested on the latest Insiders with today's update.
Thank you both for the info! We have tracked down why these are not translated. It's because the extension that contributes these actions has not adopted localization. We'll use this issue to track that extension supporting it.
With v1.68.1, published 6 days ago ! has the translations, so I guess now we are waiting for a updated German pack to be published
French version is still not present !
Yes this doesn't appear to be fixed. I verified that the strings do in fact get translated and shipped in the language pack: What's odd to me is that the references extension keeps asking for reload: ! Is this the expected version ! I get the weird feeling that maybe the "correct" version of the extension isn't loading...
Yes, is the expected version - I used that once the extension was moved into the main-repo. The references viewlet is now a built-in extension, like TypeScript or JSON. I don't really know why nls wouldn't work... Is there anything else that needs to be done?
I think this is because we assume all built-in extensions have the same extension author where your extension is ... gets around this by having its own extra step for localization: But I think the easiest thing to do is just change the author of Reference Search View to ... I see you've intentionally kept the old author: Any reason why?
Yeah, I kept the old author to ensure that it still matches how it is in the marketplace. Otherwise users might have it installed twice - e.g those that install it manually.
Would it be OK to unpublish the extension? There wasn't ever a need to install it - it was always built-in anyways but before we used the marketplace for that.
It should be OK.
extension is unpublished, PR for the name change is out
Changing the publisher caused a regression (showing the extension twice). Re-opening and revert the change
enables the next try ;-)
Want to check if it worked?
Working well... <img width="759" alt="Screenshot 2022-06-17 at 17 31 55" src="https://user-"

Discussion:
"description": "%description%", "icon": "media/icon.png", "version": "1.0.0", <del> "publisher": "ms-vscode", </del> <ins> "publisher": "vscode", </ins> "license": "MIT", "engines": { "vscode": "^1.67.0"