Incomplete French (fr) translation: RequiredOptionWasNotProvided not translated
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- csharp
- Domain
- cli, localization
Research direction
Start by locating the French resource source that produces fr/System.CommandLine.resources.dll, then inspect the RequiredOptionWasNotProvided and other listed untranslated keys. Translate the missing entries, including the suggested RequiredOptionWasNotProvided and HelpOptionsRequiredLabel values, and rebuild the French satellite assembly. Verify the required-option message under fr-FR and check the other listed keys.
Written by the indexing model from the issue text.
Description
Description
The French satellite assembly (fr/System.CommandLine.resources.dll) shipped with System.CommandLine 2.0.9 contains untranslated strings.
Current behavior
When CultureInfo.DefaultThreadCurrentUICulture is set to fr-FR and a required option is missing:
Option '--input' is required.
Expected behavior
The message should be in French:
L'option '--input' est obligatoire.
Analysis
Inspecting the fr/System.CommandLine.resources.dll satellite assembly shows that RequiredOptionWasNotProvided still holds the English text, along with several other untranslated keys (ArgumentConversionCannotParse, HelpOptionDescription, HelpOptionsRequiredLabel, SuggestionsTokenNotMatched, etc.).
Environment
- System.CommandLine version: 2.0.9
- .NET version: net10.0
Suggested fix
Update the French resource file to translate all missing keys, at minimum:
- RequiredOptionWasNotProvided = L'option '{0}' est obligatoire.
- HelpOptionsRequiredLabel = (OBLIGATOIRE)
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 428
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/command-line-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dotnet/command-line-api#2792 · 2 comments · 14 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dotnet/command-line-api#2704 ·
-
Area-Completions bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dotnet/command-line-api#2137 · 1 comment · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
dotnet/command-line-api#2841 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
dotnet/command-line-api#2840 ·
All issues in dotnet/command-line-api
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·