[opensuse-translation] How to translate patterns in YaST software manager?
Hi, How to translate patterns in YaST software manager? See image in https://bugzilla.opensuse.org/attachment.cgi?id=652120 -- Regards Mindaugas -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Lørdag den 24. oktober 2015 08:59:28 skrev opensuse.lietuviu.kalba:
How to translate patterns in YaST software manager? See image in https://bugzilla.opensuse.org/attachment.cgi?id=652120
Translate the file "Patterns.[lang].po" in the LCN section of translations. E.g. for DA: http://svn.opensuse.org/viewvc/opensuse-i18n/trunk/lcn/da/po/patterns.da.po -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am 24.10.2015 um 17:04 schrieb Martin Schlander:
Lørdag den 24. oktober 2015 08:59:28 skrev opensuse.lietuviu.kalba:
How to translate patterns in YaST software manager? See image in https://bugzilla.opensuse.org/attachment.cgi?id=652120
Translate the file "Patterns.[lang].po" in the LCN section of translations.
E.g. for DA: http://svn.opensuse.org/viewvc/opensuse-i18n/trunk/lcn/da/po/patterns.da.po
That's incorrect - patterns are packages since 13.2 and should be translated in the packages branch. I created a leap branch just for them Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Thanks for information. Can someone help to propertly initialize "lt" directory with *.po files? 2015.10.25 18:24, Stephan Kulow rašė:
Am 24.10.2015 um 17:04 schrieb Martin Schlander:
Lørdag den 24. oktober 2015 08:59:28 skrev opensuse.lietuviu.kalba:
How to translate patterns in YaST software manager? See image in https://bugzilla.opensuse.org/attachment.cgi?id=652120 Translate the file "Patterns.[lang].po" in the LCN section of translations.
E.g. for DA: http://svn.opensuse.org/viewvc/opensuse-i18n/trunk/lcn/da/po/patterns.da.po
That's incorrect - patterns are packages since 13.2 and should be translated in the packages branch. I created a leap branch just for them
Greetings, Stephan
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-10-26 09:03, opensuse.lietuviu.kalba wrote:
Thanks for information. Can someone help to propertly initialize "lt" directory with *.po files?
Something like this: #!/bin/bash F=`basename $1 .po` FF=`basename $F .es` POFILE=$FF.es.po POTFILE=../../50-pot/$FF.pot echo "$POFILE and $POTFILE" if test -f $POFILE -a -f $POTFILE; then echo Applying msgmerge to $POFILE #msgmerge --previous --no-wrap --force-po -U $POFILE -C ../../50-memory/memory.es.po $POTFILE msgmerge --previous --no-wrap --force-po -U $POFILE $POTFILE msgfmt --check --stat $POFILE rm messages.mo else echo "Not found: " $POFILE or $POTFILE fi || { echo "msgmerge --no-wrap --force-po for \"$POTFILE\" failed" ; } exit This is what I use on the lcn directory, for Spanish. You will have to edit and adapt for your locale and for that new branch and directory. Hum. No. There is a problem with the script: it does not initialize, but update. I have to think more about it. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYuNkMACgkQtTMYHG2NR9VAmACdGXvzUt9VceHQ/J7C0pzUI17L XeoAnA+zCkFG9XoiJdGLa5XhOfL6p5sI =5Ygv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Thanks for information. Can someone help to propertly initialize "lt" directory with *.po files? I can do it for you later today if needed. Or do you want just a
2015-10-26 11:03 GMT+03:00 opensuse.lietuviu.kalba <opensuse.lietuviu.kalba@gmail.com>: proper script/instructions? -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
It would be nice, if you could do this job ! 2015.10.26 17:02, Alexander Melentev rašė:
I can do it for you later today if needed. Or do you want just a proper script/instructions?
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-10-26 18:04 GMT+03:00 opensuse.lietuviu.kalba <opensuse.lietuviu.kalba@gmail.com>:
It would be nice, if you could do this job !
2015.10.26 17:02, Alexander Melentev rašė:
I can do it for you later today if needed. Or do you want just a proper script/instructions?
Enjoy those newly created files. (note a beatiful revision number =) ) minton@samsunglaptop:~/Translations/opensuse-i18n/branches/openSUSE-Leap-42_1-Branch> svn ci -m "lt language initialized" Adding packages/lt Adding packages/lt/po Adding packages/lt/po/base1.lt.po Adding packages/lt/po/base2.lt.po Adding packages/lt/po/dvd1.lt.po Adding packages/lt/po/dvd2.lt.po Adding packages/lt/po/dvd3.lt.po Adding packages/lt/po/dvd4.lt.po Adding packages/lt/po/dvd5.lt.po Adding packages/lt/po/dvd6.lt.po Adding packages/lt/po/dvd7.lt.po Adding packages/lt/po/dvd8.lt.po Adding packages/lt/po/factory1.lt.po Adding packages/lt/po/factory2.lt.po Adding packages/lt/po/factory3.lt.po Adding packages/lt/po/factory4.lt.po Adding packages/lt/po/factory5.lt.po Adding packages/lt/po/factory6.lt.po Adding packages/lt/po/factory7.lt.po Adding packages/lt/po/factory8.lt.po Adding packages/lt/po/factory9.lt.po Adding packages/lt/po/gnome.lt.po Adding packages/lt/po/kde.lt.po Transmitting file data .....................done Committing transaction... Committed revision 94000.
The same was done for trunk, just in case you'll want some sync. P.S. Translation of packages in trunk branch can also be done in Transifex: https://www.transifex.com/minton/openSUSE-packages/ -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Thank you very much! 2015.10.26 18:12, Alexander Melentev rašė:
2015-10-26 18:04 GMT+03:00 opensuse.lietuviu.kalba <opensuse.lietuviu.kalba@gmail.com>:
It would be nice, if you could do this job !
2015.10.26 17:02, Alexander Melentev rašė:
I can do it for you later today if needed. Or do you want just a proper script/instructions?
Enjoy those newly created files. (note a beatiful revision number =) ) minton@samsunglaptop:~/Translations/opensuse-i18n/branches/openSUSE-Leap-42_1-Branch> svn ci -m "lt language initialized" Adding packages/lt Adding packages/lt/po Adding packages/lt/po/base1.lt.po Adding packages/lt/po/base2.lt.po Adding packages/lt/po/dvd1.lt.po Adding packages/lt/po/dvd2.lt.po Adding packages/lt/po/dvd3.lt.po Adding packages/lt/po/dvd4.lt.po Adding packages/lt/po/dvd5.lt.po Adding packages/lt/po/dvd6.lt.po Adding packages/lt/po/dvd7.lt.po Adding packages/lt/po/dvd8.lt.po Adding packages/lt/po/factory1.lt.po Adding packages/lt/po/factory2.lt.po Adding packages/lt/po/factory3.lt.po Adding packages/lt/po/factory4.lt.po Adding packages/lt/po/factory5.lt.po Adding packages/lt/po/factory6.lt.po Adding packages/lt/po/factory7.lt.po Adding packages/lt/po/factory8.lt.po Adding packages/lt/po/factory9.lt.po Adding packages/lt/po/gnome.lt.po Adding packages/lt/po/kde.lt.po Transmitting file data .....................done Committing transaction... Committed revision 94000.
The same was done for trunk, just in case you'll want some sync. P.S. Translation of packages in trunk branch can also be done in Transifex: https://www.transifex.com/minton/openSUSE-packages/
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am 24.10.2015 um 17:04 schrieb Martin Schlander:
Lørdag den 24. oktober 2015 08:59:28 skrev opensuse.lietuviu.kalba:
How to translate patterns in YaST software manager? See image in https://bugzilla.opensuse.org/attachment.cgi?id=652120
Translate the file "Patterns.[lang].po" in the LCN section of translations.
E.g. for DA: http://svn.opensuse.org/viewvc/opensuse-i18n/trunk/lcn/da/po/patterns.da.po
That's incorrect - patterns are packages since 13.2 and should be translated in the packages branch. I created a leap branch just for them
Greetings, Stephan Dear Stephan, did I get you right that lcn/50-pot/patterns.pot and corresponding *.po files are useless at least for trunk and 13.2? If yes, why are
2015-10-25 19:24 GMT+03:00 Stephan Kulow <coolo@suse.de>: they still there? Does it make sense to drop them? Are we (community translators) expected to translate also this leap branch? -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
did I get you right that lcn/50-pot/patterns.pot and corresponding *.po files are useless at least for trunk and 13.2? If yes, why are they still there? Does it make sense to drop them? They are not useless as they contain valid translations - to be moved to
On 26.10.2015 15:59, Alexander Melentev wrote: the packages PO files.
Are we (community translators) expected to translate also this leap branch?
Only if you want translated package summary and descriptions (including patterns). Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-10-27 11:08 GMT+03:00 Stephan Kulow <coolo@suse.de>:
On 26.10.2015 15:59, Alexander Melentev wrote:
did I get you right that lcn/50-pot/patterns.pot and corresponding *.po files are useless at least for trunk and 13.2? If yes, why are they still there? Does it make sense to drop them? They are not useless as they contain valid translations - to be moved to the packages PO files. OK, but that raises much bigger question: what should be done with non-existent languages? I can push the translations from patterns.*.po to corresponding files in packages branch, but there are around 60 languages in lcn, while only a dozen is available in packages. What is the current policy about adding languages to the packages branch?
Are we (community translators) expected to translate also this leap branch?
Only if you want translated package summary and descriptions (including patterns). Actually, that's the very basic reason we translate something at all: we want to see it localized =) Do the packages lists in Leap and Tumbleweed differ that much to create a separate branch? I expect a reasonably small list of unique messages, so maybe it could make more sense to add a separate file of those differences to trunk rather than creating a separate almost identical branch just for Leap packages (cause it will require the manual messages syncing from translators). Knowing the correct way of getting the fresh sources and pushing translations back for actual usage in repos would really help to justify the options and even estimate the automation of this process.
-- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 27.10.2015 11:38, Alexander Melentev wrote:
2015-10-27 11:08 GMT+03:00 Stephan Kulow <coolo@suse.de>:
On 26.10.2015 15:59, Alexander Melentev wrote:
did I get you right that lcn/50-pot/patterns.pot and corresponding *.po files are useless at least for trunk and 13.2? If yes, why are they still there? Does it make sense to drop them? They are not useless as they contain valid translations - to be moved to the packages PO files. OK, but that raises much bigger question: what should be done with non-existent languages? I can push the translations from patterns.*.po to corresponding files in packages branch, but there are around 60 languages in lcn, while only a dozen is available in packages. What is the current policy about adding languages to the packages branch?
Are we (community translators) expected to translate also this leap branch?
Only if you want translated package summary and descriptions (including patterns). Actually, that's the very basic reason we translate something at all: we want to see it localized =) Do the packages lists in Leap and Tumbleweed differ that much to create a separate branch? I expect a reasonably small list of unique messages, so maybe it could make more sense to add a separate file of those differences to trunk rather than creating a separate almost identical branch just for Leap packages (cause it will require the manual messages syncing from translators).
That would be cool, but I lack the time to do that properly - so I created a branch Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-10-27 12:30, Stephan Kulow wrote:
That would be cool, but I lack the time to do that properly - so I created a branch
It is unmanageable. I see 86028 messages, with 14814 fuzzy and 60813 untranslated, for "es". With this size, we can't keep translated all branches by hand. We would need something to translate a single branch and automatically do the rest. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYvlAoACgkQtTMYHG2NR9Va5wCfebvGQ+Ykp/9eVTK6Sj3NdbWD soUAn3T9FuClBLWbKq8qerLNvP5kcrKZ =s9In -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-10-27 13:11 GMT-02:00 Carlos E. R. <carlos.e.r@opensuse.org>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2015-10-27 12:30, Stephan Kulow wrote:
That would be cool, but I lack the time to do that properly - so I created a branch
It is unmanageable. I see 86028 messages, with 14814 fuzzy and 60813 untranslated, for "es". With this size, we can't keep translated all branches by hand.
We would need something to translate a single branch and automatically do the rest.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Hi, If I didn't understand wrong, this is one of the benefits of weblate. Regards, Luiz -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-10-27 17:16, Luiz Fernando Ranghetti wrote:
Hi,
If I didn't understand wrong, this is one of the benefits of weblate.
Yes, could be. On the other hand... when we started translating (Spanish), I remember doing about the entire packages files, a few people. But on the next round almost all our translations had disappeared! We had to start again from scratch, and most of us refused, discouraged. I think there is a conflict with upstream translations, I don't remember for sure. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYwHWQACgkQja8UbcUWM1y76gD/dH8mjod2FvCqNiHvDvjuNmbW 8mrt4idjWGH9yJD0kqcA/jhOVSFv5fFEhH/UVWraFxng+/CzZRuQ+AAb/aeO1xvh =wJQY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-10-28 3:57 GMT+03:00 Carlos E. R. <carlos.e.r@opensuse.org>:
On the other hand... when we started translating (Spanish), I remember doing about the entire packages files, a few people. But on the next round almost all our translations had disappeared! We had to start again from scratch, and most of us refused, discouraged.
I think there is a conflict with upstream translations, I don't remember for sure. Carlos, can you please remember when this has happened? I mean, when have you committed fully translated files. I'm not asking for revision number, but at least a rough estimation of date to narrow my search. Then I'll try to resurrect them and also push to Leap.
-- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-10-28 10:51, Alexander Melentev wrote:
2015-10-28 3:57 GMT+03:00 Carlos E. R. <>:
I think there is a conflict with upstream translations, I don't remember for sure. Carlos, can you please remember when this has happened? I mean, when have you committed fully translated files. I'm not asking for revision number, but at least a rough estimation of date to narrow my search. Then I'll try to resurrect them and also push to Leap.
Several years ago. From my local copy of the translation svn tree, I think it is earlier than 10.3, in year 2008. I think the file was then named "update-desktop-files.es.po", in lcn. I see that in 2007 it was fully translated, but had "only" 6838 messages, although big, 1.2 MB. It was the largest file at the time. In my mail history I see it was done on 2007-11. Now it is about 10 times larger! If it is the same thing. I do not see a packages branch at the time (10.2 did not have it, 10.3 had - at least in my local copy). Too long ago... I don't remember if packages is the successor of update-*-files. Confused. I found other interesting references to this branch. Cut and pasting: +++----start cut---------------------- Date: Fri, 22 Aug 2008 08:14:15 +0300 From: Nick Shaforostoff <> To: opensuse-translation@opensuse.org Subject: [opensuse-translation] package descriptions translaton hi. debian doesn't want to install properly on my aspire one, but opensuse do, so i guess i'm switching. Debian has a web-interface for package description translation: http://ddtp.debian.net/ http://ddtp.debian.net/ddtss/index.cgi/xx I wonder if opensuse has something similar. - ----end cut----------------------++- - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYwrxIACgkQtTMYHG2NR9VV1QCdG4CHbBikKQOrco2hwtpD+RIS mxQAnA5smxcxckESAaKuPgpy2c8IP56K =mr8v -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 28.10.2015 12:18, Carlos E. R. wrote:
On 2015-10-28 10:51, Alexander Melentev wrote:
2015-10-28 3:57 GMT+03:00 Carlos E. R. <>:
I think there is a conflict with upstream translations, I don't remember for sure. Carlos, can you please remember when this has happened? I mean, when have you committed fully translated files. I'm not asking for revision number, but at least a rough estimation of date to narrow my search. Then I'll try to resurrect them and also push to Leap.
Several years ago. From my local copy of the translation svn tree, I think it is earlier than 10.3, in year 2008.
I think the file was then named "update-desktop-files.es.po", in lcn. I see that in 2007 it was fully translated, but had "only" 6838
If your aim is to generate useless mailing list traffic: great job! If not: what have the desktop-files to do with the topic? Care to explain? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-10-28 15:16 GMT-02:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2015-10-28 16:25, Stephan Kulow wrote:
On 28.10.2015 12:18, Carlos E. R. wrote:
If not: what have the desktop-files to do with the topic? Care to explain?
I don't know. As I said, I'm confused.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Hi, update-desktop-files-* referes to, as the name says, the .desktop files presents in programs (its name and the description), many of them translated upstream (like the u-d-f-kde for example) The package info are the info show for a package in YaST software or zypper info, usually not translated (as its very huge). Would be nice to see if we can use the translations that debian does in the link you pointed so we (translators) don't to the job twice Regards, Luiz -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-10-28 19:03, Luiz Fernando Ranghetti wrote:
2015-10-28 15:16 GMT-02:00 Carlos E. R. <>:
Hi,
update-desktop-files-* referes to, as the name says, the .desktop files presents in programs (its name and the description), many of them translated upstream (like the u-d-f-kde for example)
The package info are the info show for a package in YaST software or zypper info, usually not translated (as its very huge).
So, I got confused between two different group of files. Sigh :-( I was correct though, in remembering that some teams, like mine, decided not to even try to translate "packages", unless bored ;-)
Would be nice to see if we can use the translations that debian does in the link you pointed so we (translators) don't to the job twice
Indeed. Or do it somewhere upstream and share between all distributions. It is a huge translation job for amateurs and volunteers. I can do about a hundred strings per day, two at most: after that, I get very tired. It would take me 600 days! - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYxEh0ACgkQtTMYHG2NR9Us0wCbBkZTgaNv3Ieqx/oBXFUH91C2 dtQAnjyCa69Y40HD8VJDhlCJO19/WyoU =xtQ7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Hi. El Miércoles, 28 de octubre de 2015 19:21:21 Carlos E. R. escribió:
On 2015-10-28 19:03, Luiz Fernando Ranghetti wrote:
2015-10-28 15:16 GMT-02:00 Carlos E. R. <>:
Hi,
update-desktop-files-* referes to, as the name says, the .desktop files presents in programs (its name and the description), many of them translated upstream (like the u-d-f-kde for example)
The package info are the info show for a package in YaST software or zypper info, usually not translated (as its very huge).
So, I got confused between two different group of files. Sigh :-(
I was correct though, in remembering that some teams, like mine, decided not to even try to translate "packages", unless bored ;-)
Would be nice to see if we can use the translations that debian does in the link you pointed so we (translators) don't to the job twice
Indeed.
Or do it somewhere upstream and share between all distributions. It is a huge translation job for amateurs and volunteers. I can do about a hundred strings per day, two at most: after that, I get very tired. It would take me 600 days!
I think that most of the packages descriptions are very seldom modified (if ever). If they aren't wiped on every new openSUSE version, it could be done. Yes, it would take some time to get it finished but it's indeed quite feasible. Of course, it would be much better if we could use the already done translations or find somewhere to share it with the community as pointed by Carlos E. R. Greetings. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Den 27. okt. 2015 16:11, Carlos E. R. skreiv:
On 2015-10-27 12:30, Stephan Kulow wrote:
That would be cool, but I lack the time to do that properly - so I created a branch It is unmanageable. I see 86028 messages, with 14814 fuzzy and 60813 untranslated, for "es". With this size, we can't keep translated all branches by hand.
We would need something to translate a single branch and automatically do the rest.
Then let me offer you the summit workflow, as I’ve talked about before: http://lists.opensuse.org/opensuse-translation/2015-07/msg00004.html I currently use it for translating openSUSE, and it works *very well*. Whenever a new branch is added, it’s only a single line to add to a config file to handle it. Strings are automatically collected from, and scattered to, the various branches. Regarding the package description files, I also plan to do some changes to make my life (and that of other translators that wish to use the summit workflow) easier. Currently, strings are split over several files, e.g. dvd1.po, dvd2.po, …, dvd8.po. I’m not sure what system is used, but it looks the strings are sorted by application name and then split. If so, this means that strings may move between files between updates/releases/branches (e.g. the strings for application foo may be in dvd1.po today and in dvd2.po tomorrow, and perhaps in dvd3.po in a different branch). This obviously makes the translators’ works harder, so in the summit I’ll merge all the files that belong together into larger files (e.g. dvd.po, base.po, factory.po, gnome.po and kde.po). Also, for some strange reason the strings are sorted alphabetically by content *within* files. That means that the name for package ‘foo’ can be in the beginning of the file, while its description will be at the end of the file, and strings for subpackages (foo-devel, foo-lib, foo-bar, foo-baz etc.) that belong together are scattered *all over the* file. This obviously makes it much harder both to translate the strings (you have no context!) and to ensure consistency and high quality translations. My plan here is to add ‘fake’ file name reference comments to each string, based on the package name (which luckily *is* included in the files, as comments) and the type of string (package name, description, …), and then to run ‘msgcat --sort-by-file’ on the resulting files. These comments will of course only be visible in the ‘summit’ folder, not in any of the branch folders. -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-10-27 17:26, Karl Ove Hufthammer wrote:
I currently use it for translating openSUSE, and it works *very well*. Whenever a new branch is added, it’s only a single line to add to a config file to handle it. Strings are automatically collected from, and scattered to, the various branches.
Interesting.
Regarding the package description files, I also plan to do some changes to make my life (and that of other translators that wish to use the summit workflow) easier. Currently, strings are split over several files, e.g. dvd1.po, dvd2.po, …, dvd8.po. I’m not sure what system is used, but it looks the strings are sorted by application name and then split. If so, this means that strings may move between files between updates/releases/branches (e.g. the strings for application foo may be in dvd1.po today and in dvd2.po tomorrow, and perhaps in dvd3.po in a different branch). This obviously makes the translators’ works harder, so in the summit I’ll merge all the files that belong together into larger files (e.g. dvd.po, base.po, factory.po, gnome.po and kde.po).
I think that initially it was a few but huge files, that had to be broken in pieces to divide the work for several people to work at the same time, then joined again for submission.
Also, for some strange reason the strings are sorted alphabetically by content *within* files. That means that the name for package ‘foo’ can be in the beginning of the file, while its description will be at the end of the file, and strings for subpackages (foo-devel, foo-lib, foo-bar, foo-baz etc.) that belong together are scattered *all over the* file. This obviously makes it much harder both to translate the strings (you have no context!)
Indeed! But I think this should better be done upstream. I don't know how the files are generated, but there has to be a source for them, common to all distributions. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYwH+YACgkQja8UbcUWM1z0JQD+NhiyxqKHMbMeSnjdUBWq919J bVWtwiznSNz8oI+b/n0A/R+AjXsV02r+w7FTq7VeqDJ/rmitOxqOr0PCgpuuDwqP =UPtJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Are we (community translators) expected to translate also this leap branch?
Only if you want translated package summary and descriptions (including patterns). Actually, that's the very basic reason we translate something at all: we want to see it localized =) Do the packages lists in Leap and Tumbleweed differ that much to create a separate branch? I expect a reasonably small list of unique messages, so maybe it could make more sense to add a separate file of those differences to trunk rather than creating a separate almost identical branch just for Leap packages (cause it will require the manual messages syncing from translators).
That would be cool, but I lack the time to do that properly - so I created a branch Sure, that's understandable. But as a matter of fact we can do it for you, cause we mess with translation files all the time and you have other things to do. If you wish we will handle the translation files in a way which is more comfortable for translators. The only thing we miss in this case is actual knowledge about
2015-10-27 14:30 GMT+03:00 Stephan Kulow <coolo@suse.de>: procedures of getting the latest package descriptions and pushing translations for actual usage. Does it require access to some internal resources or it can be established for community translators also? I know it should be technically possible after I got an account on i18n.opensuse.org instance. With some guidance from your side we could make each other's lifes easier :) -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 2015-10-28 11:17, Alexander Melentev wrote:
2015-10-27 14:30 GMT+03:00 Stephan Kulow <>:
That would be cool, but I lack the time to do that properly - so I created a branch Sure, that's understandable. But as a matter of fact we can do it for you, cause we mess with translation files all the time and you have other things to do. If you wish we will handle the translation files in a way which is more comfortable for translators. The only thing we miss in this case is actual knowledge about procedures of getting the latest package descriptions and pushing translations for actual usage. Does it require access to some internal resources or it can be established for community translators also? I know it should be technically possible after I got an account on i18n.opensuse.org instance. With some guidance from your side we could make each other's lifes easier :)
That would *very* nice! 80Kmsg is about untranslatable, and doing it several times is unthinkable. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 28.10.2015 11:17, Alexander Melentev wrote:
Are we (community translators) expected to translate also this leap branch?
Only if you want translated package summary and descriptions (including patterns). Actually, that's the very basic reason we translate something at all: we want to see it localized =) Do the packages lists in Leap and Tumbleweed differ that much to create a separate branch? I expect a reasonably small list of unique messages, so maybe it could make more sense to add a separate file of those differences to trunk rather than creating a separate almost identical branch just for Leap packages (cause it will require the manual messages syncing from translators).
That would be cool, but I lack the time to do that properly - so I created a branch Sure, that's understandable. But as a matter of fact we can do it for you, cause we mess with translation files all the time and you have other things to do. If you wish we will handle the translation files in a way which is more comfortable for translators. The only thing we miss in this case is actual knowledge about
2015-10-27 14:30 GMT+03:00 Stephan Kulow <coolo@suse.de>: procedures of getting the latest package descriptions and pushing translations for actual usage. Does it require access to some internal resources or it can be established for community translators also? I know it should be technically possible after I got an account on i18n.opensuse.org instance. With some guidance from your side we could make each other's lifes easier :)
No, it's all in 50-tools - and Marguerite touched it before, so it's possible ,) These scripts fetch the package data from download.opensuse.org and split the extracted strings. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-10-28 18:20 GMT+03:00 Stephan Kulow <coolo@suse.de>:
On 28.10.2015 11:17, Alexander Melentev wrote:
Are we (community translators) expected to translate also this leap branch?
Only if you want translated package summary and descriptions (including patterns). Actually, that's the very basic reason we translate something at all: we want to see it localized =) Do the packages lists in Leap and Tumbleweed differ that much to create a separate branch? I expect a reasonably small list of unique messages, so maybe it could make more sense to add a separate file of those differences to trunk rather than creating a separate almost identical branch just for Leap packages (cause it will require the manual messages syncing from translators).
That would be cool, but I lack the time to do that properly - so I created a branch Sure, that's understandable. But as a matter of fact we can do it for you, cause we mess with translation files all the time and you have other things to do. If you wish we will handle the translation files in a way which is more comfortable for translators. The only thing we miss in this case is actual knowledge about
2015-10-27 14:30 GMT+03:00 Stephan Kulow <coolo@suse.de>: procedures of getting the latest package descriptions and pushing translations for actual usage. Does it require access to some internal resources or it can be established for community translators also? I know it should be technically possible after I got an account on i18n.opensuse.org instance. With some guidance from your side we could make each other's lifes easier :)
No, it's all in 50-tools - and Marguerite touched it before, so it's possible ,)
These scripts fetch the package data from download.opensuse.org and split the extracted strings.
Greetings, Stephan
OK, so I messed with the scripts you mentioned and got some interesting results. I found only two patterns which differ between Leap and Tumbleweed. TW has: #. description(patterns-openSUSE:patterns-openSUSE-mate) msgid "The MATE desktop environment is a desktop environment using traditional metaphors." #. description(patterns-openSUSE:patterns-openSUSE-mate_internet) msgid "MATE Internet Applications." And Leap has: #. description(patterns-openSUSE:patterns-openSUSE-mate) msgid "The MATE desktop environment is a desktop environment using traditional metaphors" #. description(patterns-openSUSE:patterns-openSUSE-mate_internet) msgid "MATE Internet Applications" The only difference I see is trailing dots in TW. So if either of the sources will be fixed to match another one, then all patterns will be identical between TW and Leap. So there is not much practical sense in creating a separate branch to translate identical content. However, there are still 3K Leap specific messages. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am 07.11.2015 um 11:37 schrieb Alexander Melentev:
The only difference I see is trailing dots in TW. So if either of the sources will be fixed to match another one, then all patterns will be identical between TW and Leap. So there is not much practical sense in creating a separate branch to translate identical content. However, there are still 3K Leap specific messages.
Hi Alexander, OK, how about you fix the scripts to a) fetch both repos and b) split out a patterns.pot c) add the info if this is leap or TW in the message comment Then we can kill the branch. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am 07.11.2015 um 11:37 schrieb Alexander Melentev:
The only difference I see is trailing dots in TW. So if either of the sources will be fixed to match another one, then all patterns will be identical between TW and Leap. So there is not much practical sense in creating a separate branch to translate identical content. However, there are still 3K Leap specific messages.
Hi Alexander,
OK, how about you fix the scripts to a) fetch both repos and b) split out a patterns.pot c) add the info if this is leap or TW in the message comment
Then we can kill the branch. Sure, this is doable. I'm not sure if I will have enough time to finish it during this weekend, but anyway the plan is for the nearest
2015-11-07 13:41 GMT+03:00 Stephan Kulow <coolo@suse.de>: possible future. Right now both splitting scripts pull package lists for Factory, while github repo has a couple of separate lists in package-lists/output/opensuse/Leap:42.1 Should they be also taken in account or they are there for some special purpose and I should stay with Factory lists for both distributions? -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am 07.11.2015 um 16:38 schrieb Alexander Melentev:
Right now both splitting scripts pull package lists for Factory, while github repo has a couple of separate lists in package-lists/output/opensuse/Leap:42.1 Should they be also taken in account or they are there for some special purpose and I should stay with Factory lists for both distributions?
The factory ones are good enough - it's trying to signal importance to the packages. And Factory's importance is good enough - it will never be 100% anyway. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Hi, Stephan and all. As of now I have finished merging the new templates and translations, which include both tumbleweed and leap packages descriptions with patterns split out to separate pot file. New comments now include distribution (full line is <distro>/<source package name>/<package name (if different from source package name)>/<package attribute (summary or description)>): #. tumbleweed/patterns-openSUSE/patterns-openSUSE-32bit/summary #. leap/patterns-openSUSE/patterns-openSUSE-32bit/summary msgid "32-Bit Runtime Environment" msgstr "" Due to a fixed bug in package lists creation, the number of messages has raised noticably, cause some completely new messages are now extracted correctly. Also po files are not sorted by content anymore. Old script is now prepare_split_tw.sh and my new one is prepare_split_tw_leap.sh -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
15. nov. 2015 19:18, Alexander Melentev wrote:
Due to a fixed bug in package lists creation, the number of messages has raised noticably, cause some completely new messages are now extracted correctly. Also po files are not sorted by content anymore.
Thanks for fixing the sorting issue. It makes the translators’ job much easier (and will probably increase quality). But is it really necessary to have the strings into *different* .pot files? Related strings appear in very different files. For example, anjuta/summary is in dvd1.pot anjuta/libanjuta-3-0/summary is in dvd4.pot anjuta/anjuta-devel/summary is in factory1.pot anjuta/glade-catalog-anjuta/summary is in factory2.pot anjuta/typelib-1_0-Anjuta-3_0/summary is in factory9.pot -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-11-15 23:14 GMT+03:00 Karl Ove Hufthammer <karl@huftis.org>:
15. nov. 2015 19:18, Alexander Melentev wrote:
Due to a fixed bug in package lists creation, the number of messages has raised noticably, cause some completely new messages are now extracted correctly. Also po files are not sorted by content anymore.
Thanks for fixing the sorting issue. It makes the translators’ job much easier (and will probably increase quality).
But is it really necessary to have the strings into *different* .pot files? Related strings appear in very different files. For example,
anjuta/summary is in dvd1.pot anjuta/libanjuta-3-0/summary is in dvd4.pot anjuta/anjuta-devel/summary is in factory1.pot anjuta/glade-catalog-anjuta/summary is in factory2.pot anjuta/typelib-1_0-Anjuta-3_0/summary is in factory9.pot
Well, there is not much sense in such splitting for me either, but I was trying to stay compatible with existing realisation, which was generating package lists based on media (kde cd, gnome cd, dvd, repo) and then splitting them into parts by package name. I couldn't break this by doing splitting in a different fashion cause we are still not aware of the way these translations get used on real media (and breaking another people's workflow without preliminary agreement is definitely not the way to have a lot of fun). The initial data for each pot file is a package list sorted by name, the name of src package is extracted later in the process by converting perl script (I used it as ready-made software since I don't even read in perl). The only way to have the resulting messages sorted by src package name instead of now-used package name is to have initial package list sorted by src package name. This will get your example lines split in two files instead of five, but somebody has to write this additional sorter. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 15.11.2015 23:40, Alexander Melentev wrote:
Well, there is not much sense in such splitting for me either, but I was trying to stay compatible with existing realisation, which was generating package lists based on media (kde cd, gnome cd, dvd, repo) and then splitting them into parts by package name. I couldn't break this by doing splitting in a different fashion cause we are still not aware of the way these translations get used on real media (and breaking another people's workflow without preliminary agreement is definitely not the way to have a lot of fun). The split is just there to help translators - the translations are merged into one big thing before usage anyway.
So fix the splitting to be as useful as needed by translators.
The initial data for each pot file is a package list sorted by name, the name of src package is extracted later in the process by converting perl script (I used it as ready-made software since I don't even read in perl). The only way to have the resulting messages sorted by src package name instead of now-used package name is to have initial package list sorted by src package name. This will get your example lines split in two files instead of five, but somebody has to write this additional sorter.
Having all binary packages of one src package in the same list sounds reasonable to me. So if one binary is in kde_cd, pull up all others too. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-11-16 13:32 GMT+03:00 Stephan Kulow <coolo@suse.de>:
On 15.11.2015 23:40, Alexander Melentev wrote:
Well, there is not much sense in such splitting for me either, but I was trying to stay compatible with existing realisation, which was generating package lists based on media (kde cd, gnome cd, dvd, repo) and then splitting them into parts by package name. I couldn't break this by doing splitting in a different fashion cause we are still not aware of the way these translations get used on real media (and breaking another people's workflow without preliminary agreement is definitely not the way to have a lot of fun). The split is just there to help translators - the translations are merged into one big thing before usage anyway.
So fix the splitting to be as useful as needed by translators.
...skip...
Having all binary packages of one src package in the same list sounds reasonable to me. So if one binary is in kde_cd, pull up all others too.
If we can split how we want it to split, then I wouldn't take media in account anymore. Leap doesn't have CDs and Tumbleweed has no physical media at all, so it will be much more logical and convinient to just get the packages descriptions from the repo and split them by src package name into pieces of reasonable size. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Hi, But it's unreasonable to expect that most trams will reach even 50%, so my idea was to signal importance of the package. But those sources connected to the DVD - including the patterns - and the rest could do. Stephan Am 17. November 2015 05:07:54 MEZ, schrieb Alexander Melentev <minton@opensuse.org>:
2015-11-16 13:32 GMT+03:00 Stephan Kulow <coolo@suse.de>:
On 15.11.2015 23:40, Alexander Melentev wrote:
Well, there is not much sense in such splitting for me either, but I was trying to stay compatible with existing realisation, which was generating package lists based on media (kde cd, gnome cd, dvd, repo) and then splitting them into parts by package name. I couldn't break this by doing splitting in a different fashion cause we are still not aware of the way these translations get used on real media (and breaking another people's workflow without preliminary agreement is definitely not the way to have a lot of fun). The split is just there to help translators - the translations are merged into one big thing before usage anyway.
So fix the splitting to be as useful as needed by translators.
...skip...
Having all binary packages of one src package in the same list sounds reasonable to me. So if one binary is in kde_cd, pull up all others too.
If we can split how we want it to split, then I wouldn't take media in account anymore. Leap doesn't have CDs and Tumbleweed has no physical media at all, so it will be much more logical and convinient to just get the packages descriptions from the repo and split them by src package name into pieces of reasonable size.
-- Regards, Minton.
-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Den 17. nov. 2015 05:07, Alexander Melentev skreiv:
If we can split how we want it to split, then I wouldn't take media in account anymore. Leap doesn't have CDs and Tumbleweed has no physical media at all, so it will be much more logical and convinient to just get the packages descriptions from the repo and split them by src package name into pieces of reasonable size.
Why split them at all? Just have one ‘packages.pot’ file. The translation software we use (Lokalize and poEdit) have no problems handling large translation files (e.g. 50,000 strings). (Having separate kde.pot and gnome.pot would be OK, though, i.e. separate files for truly separate subsystems. But arbitrarily splitting files will cause more problems than they help, e.g. where a string may move from file to file in different releases.) -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Den 17. nov. 2015 05:07, Alexander Melentev skreiv:
If we can split how we want it to split, then I wouldn't take media in account anymore. Leap doesn't have CDs and Tumbleweed has no physical media at all, so it will be much more logical and convinient to just get the packages descriptions from the repo and split them by src package name into pieces of reasonable size.
Why split them at all? Just have one ‘packages.pot’ file. The translation software we use (Lokalize and poEdit) have no problems handling large translation files (e.g. 50,000 strings). Not everything that is possible for software is possible for a human being. For instance, 200 messages is my personal maximum for one time
(Having separate kde.pot and gnome.pot would be OK, though, i.e. separate files for truly separate subsystems. But arbitrarily splitting files will cause more problems than they help, e.g. where a string may move from file to file in different releases.) kde.pot and gnome.pot don't refer to the software, but for the non-common packages of corresponding LiveCDs (common packages are in
2015-11-17 23:36 GMT+03:00 Karl Ove Hufthammer <karl@huftis.org>: translation, so files bigger than 2000 make me sad, cause I cannot make reasonable progress in decent time. Also I can hardly imagine how to split the translations tasks between several people while having one huge file. In good old days 15 people translated to Russian and I even saw 50% overall progress (well, before the bug with messages generation was fixed and a huge bunch of new messages appeared). base1 and base2). Since LiveCDs are not available for both distributions in question, as I mentioned earlier, I see no practical sense to split those out. Right now my intention is to split out several meaningful package groups to ease the distinction of what is inside and what to translate. For example, leave patterns in a separate file for quicker translation. Or have perl*, php*, python* and texlive* split out so that their translations can be postponed due to the specifics of target audience. The same is true for libraries (lib* not including libreoffice). I am open to suggestions about other package groups that can be split out to ease the translations. Old splitting was done by number of packages, so string movement was possible at every update/merge. Right now the splitting is by name, so from-fi-to-file transitions are possible only on package rename, which doesn't happen too often. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Den 20. nov. 2015 15:49, Alexander Melentev skreiv:
Why split them at all? Just have one ‘packages.pot’ file. The translation
software we use (Lokalize and poEdit) have no problems handling large translation files (e.g. 50,000 strings). […] Also I can hardly imagine how to split the translations tasks between several people while having one huge file.
It shouldn’t be *too* difficult if you have good communication (which you’ll need even if the file was split) and use poediff and poepatch. But I see your point. :)
Right now my intention is to split out several meaningful package groups to ease the distinction of what is inside and what to translate. For example, leave patterns in a separate file for quicker translation. Or have perl*, php*, python* and texlive* split out so that their translations can be postponed due to the specifics of target audience.
I don’t have a problem with such logical splitting of the translation. Actually, I think it’s a rather good idea.
The same is true for libraries (lib* not including libreoffice).
This I’m not so happy about. I think the lib- (and devel-) strings should should stay with the packages they belong to. Then it’s much easier to ensure consistent terminology.
I am open to suggestions about other package groups that can be split out to ease the translations.
rubygem-*, ghc-*, python3-*, gnome-*, libreoffice-*, myspell-*, …? Running the following in the packages folder (containing the .pot) file gives some more suggestions grep -h summary$ * | cut -f2 -d/ | cut -f1 -d- | sort | uniq -c | sort -n Perhaps groups (as defined by the above command) with more than 100 packages?
Old splitting was done by number of packages, so string movement was possible at every update/merge. Right now the splitting is by name, so from-fi-to-file transitions are possible only on package rename, which doesn't happen too often.
Yes, splitting by name should be fine. -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-11-21 19:20 GMT+03:00 Karl Ove Hufthammer <karl@huftis.org>:
Den 20. nov. 2015 15:49, Alexander Melentev skreiv:
The same is true for libraries (lib* not including libreoffice).
This I’m not so happy about. I think the lib- (and devel-) strings should should stay with the packages they belong to. Then it’s much easier to ensure consistent terminology. Oh, yes, I forgot to mention that I'm talking about splitting by src-package name, so all subpackages of one src-package (like in your example with anjuta some days ago) will stay together. Still there are lots of standalone libraries and it makes perfect sense for me to split them out.
-- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Well, if speaking about numbers, the new form of current package splitting looks like this (read as <distro>-<splitter>: <number of packages> ): tumbleweed has 27214 packages tumbleweed-a.list: 597 tumbleweed-aspell.list: 98 tumbleweed-b.list: 500 tumbleweed-c.list: 765 tumbleweed-d.list: 405 tumbleweed-e.list: 388 tumbleweed-f.list: 480 tumbleweed-ghc.list: 503 tumbleweed-g.list: 1199 tumbleweed-gnome.list: 267 tumbleweed-google.list: 136 tumbleweed-gstreamer.list: 161 tumbleweed-gtk.list: 193 tumbleweed-h.list: 208 tumbleweed-i.list: 380 tumbleweed-j.list: 249 tumbleweed-kde.list: 561 tumbleweed-k.list: 688 tumbleweed-leechcraft.list: 156 tumbleweed-lib.list: 2585 tumbleweed-libqt.list: 248 tumbleweed-libreoffice.list: 97 tumbleweed-l.list: 453 tumbleweed-mate.list: 97 tumbleweed-m.list: 592 tumbleweed-myspell.list: 143 tumbleweed-n.list: 303 tumbleweed-o.list: 505 tumbleweed-patterns.list: 129 tumbleweed-perl.list: 1020 tumbleweed-php.list: 243 tumbleweed-p.list: 840 tumbleweed-python.list: 1223 tumbleweed-q.list: 216 tumbleweed-r.list: 273 tumbleweed-rubygem.list: 1401 tumbleweed-s.list: 1022 tumbleweed-tesseract.list: 107 tumbleweed-texlive.list: 217 tumbleweed-texlive-specs.list: 5125 tumbleweed-t.list: 463 tumbleweed-u.list: 228 tumbleweed-v.list: 266 tumbleweed-w.list: 478 tumbleweed-xfce4.list: 108 tumbleweed-x.list: 557 tumbleweed-yast2.list: 187 tumbleweed-y.list: 84 tumbleweed-z.list: 69 Any additionals suggestions are welcome before I merge those to SVN. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Den 27. nov. 2015 18:18, Alexander Melentev skreiv:
Well, if speaking about numbers, the new form of current package splitting looks like this (read as <distro>-<splitter>: <number of packages> ):
Any additionals suggestions are welcome before I merge those to SVN.
It’s looking good. Perhaps add wx* (wxWidgets-*, but also other packages starting with wx, like wxMaxima and wxhexeditor)? Will the strings be sorted by (source) package name inside each file, so that, for example, all kde3-* packages will be in one ‘block’ inside kde.pot? Also, the files will be named, e.g., texlive.pot, not tumbleweed-texlive.pot, right? (*Not* having the distro prefix is better.) -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2015-11-27 21:23 GMT+03:00 Karl Ove Hufthammer <karl@huftis.org>:
It’s looking good. Perhaps add wx* (wxWidgets-*, but also other packages starting with wx, like wxMaxima and wxhexeditor)? OK, I will.
Will the strings be sorted by (source) package name inside each file, so that, for example, all kde3-* packages will be in one ‘block’ inside kde.pot? Correct, as I already mentioned in previous email, this will be done to ease everyone's life. However, this doesn't *fully* work for more than one distro due to gettext specifics. So all identical messages get sorted by source package name, but unique/different messages from "second" distro stay in the end of the file (see patterns.pot, where two different messages from leap are left in the end). Currently I have no idea how to fix that, but due to Lokalize translation memory abilities I don't consider this a huge problem.
Also, the files will be named, e.g., texlive.pot, not tumbleweed-texlive.pot, right? (*Not* having the distro prefix is better.) Sure, this was just an example of intermediate splitting before messages from two distros get merged together. Distro prefix is needed on generation stage, but gets omited after merging.
-- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
participants (9)
-
Alexander Melentev -
Carlos E. R. -
Carlos E. R. -
jcsl -
Karl Ove Hufthammer -
Luiz Fernando Ranghetti -
Martin Schlander -
opensuse.lietuviu.kalba -
Stephan Kulow