silverstripe / silverstripe/developer-docs
i18n and translation doc needs updated to account for namespace
Open
Nobody has claimed this yet.
affects/v4
complexity/low
impact/low
type/docs
- Dominant language
- No language data
- Stars
- 7
- Forks
- 74
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 6
Description
A lot of the examples on these two articles need to be updated to account for the fact that our classes are namespaced now.
https://docs.silverstripe.org/en/4/developer_guides/i18n/
https://docs.silverstripe.org/en/4/developer_guides/templates/translations/
Example of lies we are telling
<%t Member.WELCOME 'Welcome {name} to {site}' name=$Member.Name site="Foobar.com" %>
_t('LeftAndMain.FILESIMAGES','Files & Images');
en:
ImageUploader:
Attach: 'Attach {title}'
UploadField:
NOTEADDFILES: 'You can add files once you have saved for the first time.'
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 the two linked articles, i18n and templates/translations, and compare their examples with the current namespaced class conventions. Update the affected template, PHP, and YAML examples so they consistently show namespaces, then verify that both articles no longer contain the described non-namespaced examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation, internationalization
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100