action #11354
closedaction #11334: decomission svn.opensuse.org
packages/patterns/RPM_groups translations
Added by lnussel about 8 years ago. Updated over 7 years ago.
100%
Description
needs a separate github project to host it
tools are required to extract the translations for patterns somehow
Checklist
- create github project
- develop tool
- connect with weblate
- verify translations delivery path for Tumbleweed
- move github repo to openSUSE namespace
Updated by lnussel about 8 years ago
- Checklist item changed from to [ ] create github project, [ ] develop tool, [ ] connect with weblate
Updated by lnussel about 8 years ago
- Subject changed from patterns.pot to patterns.pot / package translations
Updated by lnussel over 7 years ago
Current tools are here:
https://svn.opensuse.org/viewvc/opensuse-i18n/trunk/packages/50-tools/
Updated by lnussel over 7 years ago
- Has duplicate action #11364: package translations added
Updated by lnussel over 7 years ago
- Due date set to 2016-09-30
- Status changed from New to In Progress
- Assignee set to Minton
- % Done changed from 0 to 10
Updated by Minton over 7 years ago
- Checklist item changed from [ ] create github project, [ ] develop tool, [ ] connect with weblate to [x] create github project, [x] develop tool, [ ] connect with weblate, [ ] verify translations delivery path for Tumbleweed, [ ] move github repo to openSUSE namespace
- % Done changed from 10 to 20
Updated templates with translations can be now found at https://github.com/alexminton/packages-i18n, please move accordingly =)
Generated templates are in 50-pot
Tools to generate templates and merge the translations are in 50-tools
The package-translations package is waiting for your review at https://build.opensuse.org/request/show/424294
It still points to SVN instead of git, but includes fresh translations (which were not updated for several years) cause the most important part is to test the translations delivery to user. So it makes sense for me to see if Tumbleweed will include the updated translations and switch to git after the repo is moved under openSUSE namespace and delivery is tested.
Updated by lnussel over 7 years ago
Thanks! I've created
https://github.com/openSUSE/packages-i18n
Updated by lnussel over 7 years ago
- Checklist item changed from to [x] move github repo to openSUSE namespace
Updated by lnussel over 7 years ago
the yast repo has rpm-groups.pot. I guess it should be created as part of the package translations:
https://github.com/yast/yast-translations/tree/master/po/rpm-groups
Updated by Minton over 7 years ago
lnussel wrote:
the yast repo has rpm-groups.pot. I guess it should be created as part of the package translations:
Why? It is created in yast tree and used by yast package manager, so no benefit for moving to package translations.
Updated by lnussel over 7 years ago
it's not created by YaST at all. The current version is really old and of unknown origin. We could extract the group list from actually existing packages. Or, we create it based on https://en.opensuse.org/openSUSE:Package_group_guidelines and accept that some packages don't fit. I don't think we actually enforce groups.
Updated by Minton over 7 years ago
- Subject changed from patterns.pot / package translations to packages/patterns/RPM_groups translations
Well, I can easily generate the required pot file from packages data. However, it is not obvious for me what to do with this file after creation. Should it be pushed to yast rpm_groups or vice versa the translations should be merged to packages-i18n project?
Updated by Minton over 7 years ago
- Checklist item changed from [x] create github project, [x] develop tool, [ ] connect with weblate, [ ] verify translations delivery path for Tumbleweed, [x] move github repo to openSUSE namespace to [x] create github project, [x] develop tool, [ ] connect with weblate, [x] verify translations delivery path for Tumbleweed, [x] move github repo to openSUSE namespace
I've changed the translations source to github, please accept https://build.opensuse.org/request/show/432471
Updated by lnussel over 7 years ago
Minton wrote:
Well, I can easily generate the required pot file from packages data. However, it is not obvious for me what to do with this file after creation. Should it be pushed to yast rpm_groups or vice versa the translations should be merged to packages-i18n project?
Atm we'd need to put it into YaST git, yes.
Updated by lnussel over 7 years ago
- Checklist item changed from to [x] connect with weblate
Updated by lnussel over 7 years ago
- Checklist item changed from to [ ] connect with weblate
Updated by lnussel over 7 years ago
- Assignee changed from Minton to sbrabec
- % Done changed from 20 to 80
Stanislav, could you take a look at https://github.com/openSUSE/packages-i18n to check what needs to be done to connect with weblate?
Updated by sbrabec over 7 years ago
- Checklist item changed from [x] create github project, [x] develop tool, [ ] connect with weblate, [x] verify translations delivery path for Tumbleweed, [x] move github repo to openSUSE namespace to [x] create github project, [x] develop tool, [x] connect with weblate, [x] verify translations delivery path for Tumbleweed, [x] move github repo to openSUSE namespace
lnussel wrote:
Stanislav?
It looks ready for connecting.
I wrote a script for the initialization.
I decided to use a single project with many components, as splitting to domains is just artificial. Translated string will be shared across letters.
https://l10n.opensuse.org/projects/packages-i18n/
Were there any other community translations of other languages? I see only 16 languages.
Updated by sbrabec over 7 years ago
User opensuse-i18n has not push permission. I do not have permissions as well.
Please fix and allow push and add Weblate hook.
Note: The project is unbelievably huge. Just only parsing of https://l10n.opensuse.org/projects/packages-i18n/texlive-specs-master/ takes several hours. Full parsing of the whole repository requires half day of the current Weblate server machine time.
Updated by lnussel over 7 years ago
sbrabec wrote:
User opensuse-i18n has not push permission. I do not have permissions as well.
Please fix and allow push and add Weblate hook.
Done
Note: The project is unbelievably huge. Just only parsing of
https://l10n.opensuse.org/projects/packages-i18n/texlive-specs-master/ takes
several hours. Full parsing of the whole repository requires half day of the
current Weblate server machine time.
Yes. Suggestions to improve welcome :-)
Btw, are you sure the import worked correctly? German patterns
claims no translations but it is translated.
Updated by sbrabec over 7 years ago
- % Done changed from 80 to 100
I have no ideas to improve. I am just thinking about amount of effort needed to translate 8.9MB of text. 1,283,118 words!
The import was finished just now. Please check again.
Updated by sbrabec over 7 years ago
Scripts that were used to create initial Weblate import:
https://github.com/openSUSE/packages-i18n/commit/a86a28bc43797d38e454a2b4b937eb2e2fab7623
(More general version of those in yast-translations.)
They will be needed for a future SLE import.
Updated by lnussel over 7 years ago
- Assignee changed from sbrabec to Minton
- % Done changed from 100 to 90
Alex, https://svn.opensuse.org/svn/opensuse-i18n/trunk/lcn also has patterns.*.po file. They are more complete than what could be found in the packages svn. What do you think about merging those po files, overriding the package version?
Updated by Minton over 7 years ago
Ludwig, I see absolutely no problem in doing so, but also I don't see any sense in doing so.
patterns in SVN were created in 2013 and are terribly outdated, even though contain 133 unique (Novell/KDE4/SLE/proprietary related) messages
However, most current pattrens extarcted from Tumbleweed and Leap 42.2 have 47 unique messages (mostly KDE5/Qt5 related).
Also, number of languages in LCN and Git differ drastically, I don't have a solution for this currently.
Updated by lnussel over 7 years ago
For the languages where patterns.$LANG.po exists we could try a merge though, right? At least for German there are quite some strings translated that are still valid also for the git version of patterns.de.po
Updated by Minton over 7 years ago
OK, then I will just merge valid translations from SVN to current git version as one-shot action — no changes to source strings. This should solve the short term issue of some SVN translations missing in Git.
Longer term issues like getting other patterns for translation (like, SLE-related if needed) and preserving SVN translations for currently missing strings and languages still require some solution.
Updated by Minton over 7 years ago
- Due date changed from 2016-09-30 to 2016-12-07
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Done as planned yesterday.