OpenRefine / OpenRefine/openrefine.org
Document backend translation process
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
Related to #256
Currently https://openrefine.org/docs/technical-reference/translating-ui#server--backend-coding says
Currently no back end functions are translated, so things like error messages, undo history, etc may appear in English form.
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
Start with the backend section of the technical reference page at openrefine.org/docs/technical-reference/translating-ui#server--backend-coding and read the related issue #256. Document the backend translation process and replace the current statement that no backend functions are translated with accurate guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100