i18n: Splitted strings is invalid at Transifex
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
See guidelines at https://docs.nextcloud.com/server/latest/developer_manual/basics/translations.html#step-1-string-split
Translators are lost as they do not see the first part.
@marcoambrosini git blame brought me to you. And please respect the string freeze.
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 at src/teams/views/HomeView.vue around line 40 and read the linked Nextcloud translation guideline on string splitting. Replace the split translation string with a form Transifex can present to translators, while respecting the stated string freeze. Done means the affected text is exposed as a complete translatable string.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, internationalization
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 86/100