Hello team, I'm interested in Japanese localization for this extension. Is it welcomed? If so, I just localized package.nls.json of salesforcedx-vscode-core, and I'm wondering how to determine the size of pull request. Should I localize all the package.nls.json and i18n.ts at once?


This would be amazing! We'd love to have you contribute this. I'd say it's up to you in terms of how you want to do it, but I would think doing everything in one PR is fine.
@ruthemmanuelle, @hbc-bindu - Could you provide some guidance (or existing resources) that could help with the terminology?
I was about to point @shunkosa to https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference.htm to ensure that we are using consistent terminology, but I just realized that was not localized into Japanese.
Thinking out loud: I want to ensure that we provide guidance first before we start localizing to avoid wasted work. There could be some internal effort to localize some of the docs we have (e.g., Migration Guide which would call some of those commands) so it would be good to be consistent.
Some context, when I first did https://github.com/microsoft/vscode-extension-samples/pull/21 it was under the assumption that an external contributor who wanted to help us localize would be able to do so easily, and we (Salesforce) would be able to provide some guidance on terminology for consistency.
Thank you! I'm going to create a single PR. Now I'm referring to Salesforce DX Developer guide, which is translated into Japanese. Release notes and help articles too.
https://developer.salesforce.com/docs/atlas.en-us.218.0.sfdx_dev.meta/sfdx_dev/sfdx_dev_develop.htm
For consistency, I'll review my work enumerating key and value from the all message files by a light script. I think it will become a dictionary, but if there is an existing guidance, it would be really helpful.
Hi @shunkosa we've just translated part of this doc into Japanese https://forcedotcom.github.io/salesforcedx-vscode/articles/getting-started/migrate-from-forcecom-ide. See attached files.
Force.com migration pages_ja.zip
And here is our Japanese Style Guide.
Let me know if you have any questions. I manage product localization, UI and content, and our team can certainly help you.
@rbuschiazzo I wonder if you could review or assign someone for #1551 ? Should I provide an additional explanation of this work? (like a comparison spreadsheet or something like that)
Hi @ntotten, can you help @shunkosa add those Japanese translations to the right repo?
Most helpful comment
Hi @shunkosa we've just translated part of this doc into Japanese https://forcedotcom.github.io/salesforcedx-vscode/articles/getting-started/migrate-from-forcecom-ide. See attached files.
Force.com migration pages_ja.zip
And here is our Japanese Style Guide.
style_guide_ja.pdf
Let me know if you have any questions. I manage product localization, UI and content, and our team can certainly help you.