Write translations of strings, extracted from info.xml (name, summary and description) back to info.xml
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- localization
Research direction
Start with the linked docker-ci issue #93 and the referenced appstore comment to understand the intended synchronization flow. Compare the example info.xml in the Money Buster release with the app metadata and inspect cospend-nc's l10n/descriptions/gen_info.xml.sh. Done means translated name, summary, and description values are written into appinfo/info.xml during synchronization.
Written by the indexing model from the issue text.
Description
(logical continuation of https://github.com/nextcloud/docker-ci/issues/93)
It is exactly, as former dev is stating there: https://github.com/nextcloud/appstore/issues/691#issuecomment-624560952
Result should be as can be seen for example in info.xml file from this file:
https://github.com/julien-nc/cospend-nc/releases/download/v1.5.8/cospend-1.5.8.tar.gz
(no link to git repo, because in this case is file created during release trough script https://github.com/julien-nc/cospend-nc/blob/main/l10n/descriptions/gen_info.xml.sh - probably due different translation platform used)
Idea is to mark somehow (some identifier into notes to string perhaps? As is done for .vue files) these strings, found in info.xml, during scrapping from source code for source strings to Transifex and then write their translation during sync from Transifex to app repo not (only) into .js .json files in l10n dir, but instead to (or at least also) into appinfo/info.xml (as in mentioned example).
This way translations of name, summary and description will be used at all in app store and apps.nextcloud.com (as is in mentioned example with app Money Buster). Translations are log time already done, so effect on user experience would be intermediate...
Thanks :-)
- Dominant language
- Perl
- Stars
- 46
- Forks
- 38
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from nextcloud/docker-ci
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
transifex
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
transifex
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in nextcloud/docker-ci
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Perl/perl5#24942 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
PDLPorters/pdl#561 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/eolang.sty#197 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
radiator-software/p5-net-ssleay#577 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
beyondgrep/website#143 ·