microsoft / microsoft/AzureStorageExplorer

The string 'AzCopy Command Shell Language' is not localized on Settings panel

Open
#8,035 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:globe_with_meridians: localization :test_tube: testing
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version: 1.35.0-dev (98)
Build Number: 20240701.1
Branch: main
Platform/OS: Windows11/Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.5(Apple M1 Pro)
Architecture: arm64/x64/x64/arm64
Reproduce Languages: German/Spanish
How Found: From running test cases
Regression From: Not a regression

Steps to Reproduce

  1. Launch Storage Explorer -> Open 'Settings' -> 'Application -> Regional Settings'.
  2. Select 'español' -> Restart Storage Explorer.
  3. Open Settings panel -> Go to 'AzCopy Command Shell Language' part.
  4. Check whether all strings are localized.

Expected Experience

All strings are localized.

Actual Experience

The string 'AzCopy Command Shell Language' is not localized.
image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in Settings → Application → Regional Settings and inspect the AzCopy Command Shell Language section shown in the issue. Verify the Spanish localization resources for this label and confirm that the label is localized after restarting Storage Explorer with español selected.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
localization
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.