PowerShell / PowerShell/platyPS
Local languages not supported
Open
Nobody has claimed this yet.
Area-Localization
Issue-Enhancement
- Dominant language
- C#
- Stars
- 871
- Forks
- 166
- Avg merge
- 21h 17m
- Merged PRs (30d)
- 1
Description
Steps to reproduce
Create a script with a function and a .EXAMPLE comment.
Run New-MarkdownHelp
Expected behavior
A generated markdown file with
## EXAMPLES
### EXAMPLE 1
Actual behavior
A generated markdown file with
## EXAMPLES
### BEISPIEL 1
Environment data
Windows 10
platyPs v0.12.0
PSVersion 5.1.17134.407
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
Start by reproducing the behavior with a PowerShell function containing a localized .EXAMPLE comment and running New-MarkdownHelp under the reported platyPS and PowerShell versions. Trace how the command determines the examples heading and compare the generated output with the expected English headings. Done means local-language help still generates correctly while using the expected example structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- documentation, internationalization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100