dsccommunity / dsccommunity/SqlServerDsc
SqlServerDsc: English strings must be added for all localized languages
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
Details of the scenario you tried and the problem that is occurring:
When adding a localized string in English, it's not possible for the user to translate the strings to all localized languages.
To overcome this, with the way localization is built currently, then the strings must be added to all localized languages as English strings so they can be translated by another PR.
The DSC configuration that is using the resource (as detailed as possible):
n/a
**Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:**n
n/a
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev
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.
Research direction
No files, tests, or entry points are named. Start by locating the module's localization resources and the current localization build process; verify how newly added English strings are represented for each localized language. Done means every required localized language contains the new strings as English fallback text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- localization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100