nextcloud / nextcloud/docker-ci
Making existing code base more translation guideline compliant
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 45
- Forks
- 37
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
Not sure where else to put this. Saw the post on the forum from Anna (@miaulalala?):
Additionally, strings show up all the time with zero context, and a translator can’t tell what they mean without going and reading the code. So the same string ends up getting translated two or three times, which is exactly the kind of effort small language teams don’t have lying around.
We’d rather stop accepting translation requests for new apps for a bit and actually fix this than keep adding projects nobody has the bandwidth to translate. A few language teams have already given up entirely; that’s the thing we’re trying to head off before it happens again.
We’re working on what needs to be in place first: automated checks so obvious problems in source strings get caught before a translator ever lays eyes on them, a review step before anything new goes live, and a structure that doesn’t leave people lost. We’ll post again once requests reopen.
There may be some non-LLM options for the initial obvious check, but for what it's worth I just ran a quick experiment in GHCP to see how good it can be at finding areas of the code base with less-than-ideal translation guideline compliance and to suggest concrete fixes.
It does seem to turn up bits in the code base to iterate on reasonably well. This was the proof of concept prompt:
Analyze the Nextcloud Translation guideliness (https://docs.nextcloud.com/server/latest/developer_manual/basics/translations.html#guidelines) and then pick a random area of code likely to have strings that get translated. Identify several substantive discrepancies versus the documented policy and suggest concrete code changes to make compliant with policy.
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
Read the linked Nextcloud Translation guidelines first, then inspect the codebase areas containing translatable strings and compare them with the documented policy. No specific files, tests, or entry points are identified; done would require selecting concrete discrepancies and applying the agreed compliance fixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- internationalization, localization
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100