silverstripe / silverstripe/developer-docs
Document when translations get picked up from transifex
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 74
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 6
Description
Pages affected
How does my translation get into a Silverstripe CMS release?
Description
As of today, the SilverStripe\Forms\GridField\GridField.Add tag is still undefined in it.yml. On transifex I translated that thing (among many others) about 3 months ago.
It would be nice to document when those translations are picked up, so a developer can decide whether or not is it worth to patch a project. Actually the documentation just states how it is done:
Currently this is a manual process of a core team member downloading approved translations
and committing them into our source tree.
No idea who should approve my translations though.
Validations
- Check that there isn't already an issue that reports the same problem
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
Open the affected “How does my translation get into a Silverstripe CMS release?” page and review its current description of manually downloading approved translations. Confirm the pickup timing and who approves translations, then update that page so contributors can decide whether to patch a project; the revised documentation should answer both questions clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, localization
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100