eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
[nls] many plugin.xml strings not extracted to properties file.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
Leaving this just to track for now.
I already am working on the pull request, but I am still setting up to test the results; need to gen an nl pack to confirm fixed.
org.eclipse.wildwebdeveloper/plugin.xml
org.eclipse.wildwebdeveloper/plugin.properties
org.eclipse.wildwebdeveloper.xml/plugin.xml
org.eclipse.wildwebdeveloper.xml/plugin.properties
Schema Associations as a Preference page name, for example, needs to be extracted to the properties file so it can be translated.
names/labels like XML or JSON probably are fine as-is, but to be thorough I will extract those as well.
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 reviewing org.eclipse.wildwebdeveloper/plugin.xml, org.eclipse.wildwebdeveloper/plugin.properties, org.eclipse.wildwebdeveloper.xml/plugin.xml, and org.eclipse.wildwebdeveloper.xml/plugin.properties. Check the Schema Associations preference page name and other plugin.xml labels, then generate an nl pack to confirm the extracted strings are available for translation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- internationalization, localization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100