goatcorp / goatcorp/SamplePlugin
Plugin Localization Best Practices
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 165
- Forks
- 150
- PR merge metrics
- No merged PRs in 30d
Description
Are there any best practices for plugin localization?
I want to make my plugin support other languages, but don't know how to do it.
Contributor guide
No contributing guide indexed for this repository
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 in the issue. Start by reviewing the SamplePlugin repository for any existing plugin localization approach, then document the project's recommended best practices and what plugin authors should do to support other languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- localization
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100