[opensuse-translation] Re: obsolete webyast pot files in openSUSE localization svn?
Hi Stafan, This sounds very promising for me. I really thank you for cooperation and thanks to Karl for help and thanks for other I forgot :). Can't wait to see how smoothly will run this process! best kalman On Fri, Mar 4, 2011 at 2:43 PM, Stefan Schubert <schubi@suse.de> wrote:
Hi Kálmán, WebYaST has the problem that is is used in OpenSUSE AND SLES products. In SLES products we have to use our own translations but we would like to use the community translations for OpenSUSE. We have one codestream for WebYaST only. So the problem is to take the correct translation set for each OpenSUSE or SLES release.
I have talked to Karl Eichwald how to solve this issue and we have found one solution which satisfies both sides: WebYaST packages will contain the Novell translations. When we are making the next OpenSUSE release the OpenSUSE translations will be put into the package "translation-update". This will be handled by Karl. (Thank you Karl !) gettext has a mechanism to prefer these translation. So the Novell translations will NOT be used by WebYaST on OpenSUSE although they are still in the WebYaST packages.
So, how is the timeframe ?
- As 11.4 is already out we have time until the next release. Feel free to start an translation round. But is has time until next release. - I will update the pot files around reaching the first milestone of the next OpenSUSE release and will post an EMAIL to this list in order to inform the translation community. - WebYaST will be integrated in the general OpenSUSE translation round workflow then. - Karl or I will pick up the translations and will generate the concerning package when the translations are available.
I hope that will solve this problem. Feel free remark other/additional opinions.
Greetings Stefan
Am 04.03.2011 12:29, schrieb Kálmán Kéménczy:
Hi Stefan,
First of all, thanks for the quick response and action!
But after the temporary cure, please let us know how the process should flow.
How often will you update the localization svn? How often would you like to pull out something? Is it better for you if someone else take care of it (pull out and push back to git or build service)?
We, translators would like to schedule our works and we also have to sync with the distribution release schedule.
thanks for your understanding best kalamn
On Fri, Mar 4, 2011 at 11:31 AM, Stefan Schubert <schubi@suse.de> wrote:
Hallo Kálmán, thank you for bringing that up. I have updated the pot files in
https://svn.berlios.de/viewvc/opensuse-i18n/trunk/webyast/00-pot
to the current state.
Thanks again and greetings Stefan
Am 03.03.2011 16:49, schrieb Kálmán Kéménczy:
Dear Stefan,
My name is Kálmán Kéménczy a Hungarian community translator for openSUSE.
On the translation mailing list came up the question about the webyast localization process. It seems that our pot files are obsolete: https://svn.berlios.de/viewvc/opensuse-i18n/trunk/webyast/00-pot/?sortby=dat...
I talked to Shane Wims today from Novell Localization department, Dublin and he said the latest pot files are here: https://svn.berlios.de/viewvc/opensuse-i18n/branches/SLE11SP1/webyast/00-pot...
These files looks newer but still old and we are a bit confused at this point. He mentioned to contact to you.
I would like to ask you to work together on a process to manage the translations of the webyast (the version which will be the part of the openSUSE).
I really appreciate your help in advance.
best kalman
-- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
-- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2011-03-04 at 15:41 +0100, Kálmán Kéménczy wrote:
This sounds very promising for me. I really thank you for cooperation and thanks to Karl for help and thanks for other I forgot :).
Can't wait to see how smoothly will run this process!
I have a doubt.
On Fri, Mar 4, 2011 at 2:43 PM, Stefan Schubert <> wrote:
Hi Kálmán, WebYaST has the problem that is is used in OpenSUSE AND SLES products. In SLES products we have to use our own translations but we would like to use the community translations for OpenSUSE. We have one codestream for WebYaST only. So the problem is to take the correct translation set for each OpenSUSE or SLES release.
I have talked to Karl Eichwald how to solve this issue and we have found one solution which satisfies both sides: WebYaST packages will contain the Novell translations. When we are making the next OpenSUSE release the OpenSUSE translations will be put into the package "translation-update". This will be handled by Karl. (Thank you Karl !) gettext has a mechanism to prefer these translation. So the Novell translations will NOT be used by WebYaST on OpenSUSE although they are still in the WebYaST packages.
I don't understand completely. I think you mean that the webyast package will contain the Novell translation, and in opensuse these will be overwritten by the openSuSE translations in a separate update. Is that it? Well... could be. I would prefer the webyast package containing the correct translation for each distribution, somehow. Or there will be problems ahead. I have already translated the Spanish side of webyast and uploaded it to the svn at berlios. I fear this is too late for 11.4 GM (although I opened a Bugzilla about this on Feb 14), so I would really like to see this update package distributed via YOU. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1yQeYACgkQtTMYHG2NR9XJ7ACglGXdh6rKbJUE4UeFPMs42u4f y7MAniVVORQJLIxwd0YpEIHXET8XE0kb =e/a/ -----END PGP SIGNATURE-----
Can't wait to see how smoothly will run this process!
I have a doubt.
We all have some doubts, but please be positive :) I believe all of us do the best to achieve our goals.
On Fri, Mar 4, 2011 at 2:43 PM, Stefan Schubert <> wrote:
Hi Kálmán, WebYaST has the problem that is is used in OpenSUSE AND SLES products. In SLES products we have to use our own translations but we would like to use the community translations for OpenSUSE. We have one codestream for WebYaST only. So the problem is to take the correct translation set for each OpenSUSE or SLES release.
I have talked to Karl Eichwald how to solve this issue and we have found one solution which satisfies both sides: WebYaST packages will contain the Novell translations. When we are making the next OpenSUSE release the OpenSUSE translations will be put into the package "translation-update". This will be handled by Karl. (Thank you Karl !) gettext has a mechanism to prefer these translation. So the Novell translations will NOT be used by WebYaST on OpenSUSE although they are still in the WebYaST packages.
I don't understand completely.
I think you mean that the webyast package will contain the Novell translation, and in opensuse these will be overwritten by the openSuSE translations in a separate update. Is that it?
you understand quite well. as far as I know Novell already reduced the number of target languages for webyast to 8. beyond this 8 languages there will be no conflict at all and we can handle separately the openSUSE localization team's work.
Well... could be.
I would prefer the webyast package containing the correct translation for each distribution, somehow. Or there will be problems ahead.
I don't thinks so, if a localization team from the 8 languages don't want to work on the translations the users will be happy with the existing ones from Novell. And every team has a chance to add an alternative localization for openSUSE, like your team. imho this is one of the best was so far we can manage.
I have already translated the Spanish side of webyast and uploaded it to the svn at berlios. I fear this is too late for 11.4 GM (although I opened a Bugzilla about this on Feb 14), so I would really like to see this update package distributed via YOU.
same here, hopefully this is what we would like to do. well we need to clarify this best k -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-03-05 at 15:42 +0100, Kálmán Kéménczy wrote:
I have a doubt.
We all have some doubts, but please be positive :)
I was being positive - when I'm negative I leave no doubts about it >;-)
I believe all of us do the best to achieve our goals.
On Fri, Mar 4, 2011 at 2:43 PM, Stefan Schubert <> wrote:
Well... could be.
I would prefer the webyast package containing the correct translation for each distribution, somehow. Or there will be problems ahead.
I don't thinks so, if a localization team from the 8 languages don't want to work on the translations the users will be happy with the existing ones from Novell.
Ah, that's a point that didn't occur to me. In that case, well, ok.
And every team has a chance to add an alternative localization for openSUSE, like your team. imho this is one of the best was so far we can manage.
Ok. :-) - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1ypeUACgkQtTMYHG2NR9U1EACdEmV0bZ8OhfcNuqsfPKMX5tyK 1pUAniUOqUc43VMkPLmLbtLJRxVEOxfC =CBBp -----END PGP SIGNATURE-----
"Carlos E. R." <carlos.e.r@opensuse.org> writes:
I have already translated the Spanish side of webyast and uploaded it to the svn at berlios. I fear this is too late for 11.4 GM (although I opened a Bugzilla about this on Feb 14), so I would really like to see this update package distributed via YOU.
Please, assign it to me. Are you still busy with translating webyast? How much time do you need for preparing this Update? I'd like to submit the packages end of this week or early next week. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2011/3/7 Karl Eichwalder <ke@suse.de>:
Are you still busy with translating webyast? How much time do you need for preparing this Update?
I'd like to submit the packages end of this week or early next week.
Karl, can you synchronize the Italian version? I tried using Carlos' scripts but I have found some problem generating new po files from pot. Thanks, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Le 07/03/2011 10:08, Andrea Turrini a écrit :
Are you still busy with translating webyast? How much time do you need for preparing this Update?
I'd like to submit the packages end of this week or early next week. Karl, can you synchronize the Italian version? I tried using Carlos'
2011/3/7 Karl Eichwalder<ke@suse.de>: scripts but I have found some problem generating new po files from pot.
Thanks, Andrea
You can try this one I used. You must have the POT files in ./00-POT/ and the po files in ./$lang/po/. If not, you can download them with SVN. It merge the PO files with latest POT files and create PO files for new POT files. You must change the lang (from "fr" to "it" for example). #!/bin/bash lang=fr POT_path=./00-pot/ PO_path=./$lang/po/ # Update all PO files with a POT file for PO_file in `ls $PO_path/*.$lang.po`; do echo $(basename $PO_file .$lang.po) POT_file=$POT_path/$(basename $PO_file .$lang.po).pot if [[ -e $POT_file ]] then # POT and PO files exist => update echo "NOTE: $POT_file exist." msgmerge --update $PO_file $POT_file else echo "WARNING: $POT_path/$(basename $PO_file .$lang.po).pot does not exist!!" fi done POT_file="" PO_file="" echo "" echo "" # Create PO files for new POT files for POT_file in `ls $POT_path/*.pot`; do echo $(basename $POT_file .pot) PO_file=$PO_path/$(basename $POT_file .pot).$lang.po if [[ -e $PO_file ]] then # POT and PO files exist => nothing to do echo "NOTE: $PO_file exist. Nothing to do" else echo "NOTE: $PO_file does not exist. Creating PO file." msginit --no-translator --locale=$lang --input=$POT_file --output-file=$PO_file fi done -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Mandag 7. mars 2011 11.05.00 skrev Guillaume Gardet :
Le 07/03/2011 10:08, Andrea Turrini a écrit :
2011/3/7 Karl Eichwalder<ke@suse.de>:
Are you still busy with translating webyast? How much time do you need for preparing this Update?
I'd like to submit the packages end of this week or early next week.
Karl, can you synchronize the Italian version? I tried using Carlos' scripts but I have found some problem generating new po files from pot.
Thanks, Andrea
You can try this one I used. You must have the POT files in ./00-POT/ and the po files in ./$lang/po/. If not, you can download them with SVN. It merge the PO files with latest POT files and create PO files for new POT files. You must change the lang (from "fr" to "it" for example).
#!/bin/bash
I have probably not followed this discussion from the beginning. However, is there a particular reason why the webyast files cannot be merged centrally for all languages in the same way as as lcn and yast repositories? -- Olav P. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
I have probably not followed this discussion from the beginning.
However, is there a particular reason why the webyast files cannot be merged centrally for all languages in the same way as as lcn and yast repositories?
you are right. this would be the best way. k -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Olav P." <olav.pet@gmail.com> writes:
However, is there a particular reason why the webyast files cannot be merged centrally for all languages in the same way as as lcn and yast repositories?
It can and now I'll run the 00-tools/lcn-merge.sh script. With the -c switch it commit automatically, IIRC. It was not done thus far, because I often forgot about webyast or I was not sure about the status. ATM, the script is running... -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hi, Just a little suggestion. If you use Lokalize, try msgmerge with --previous option too (in Lokalize it shows what changes in the string when it became fuzzy) Regards, Luiz 2011/3/7 Guillaume Gardet <guillaume.gardet@free.fr>:
Le 07/03/2011 10:08, Andrea Turrini a écrit :
2011/3/7 Karl Eichwalder<ke@suse.de>:
Are you still busy with translating webyast? How much time do you need for preparing this Update?
I'd like to submit the packages end of this week or early next week.
Karl, can you synchronize the Italian version? I tried using Carlos' scripts but I have found some problem generating new po files from pot.
Thanks, Andrea
You can try this one I used. You must have the POT files in ./00-POT/ and the po files in ./$lang/po/. If not, you can download them with SVN. It merge the PO files with latest POT files and create PO files for new POT files. You must change the lang (from "fr" to "it" for example).
#!/bin/bash
lang=fr
POT_path=./00-pot/ PO_path=./$lang/po/
# Update all PO files with a POT file for PO_file in `ls $PO_path/*.$lang.po`; do echo $(basename $PO_file .$lang.po) POT_file=$POT_path/$(basename $PO_file .$lang.po).pot if [[ -e $POT_file ]] then # POT and PO files exist => update echo "NOTE: $POT_file exist." msgmerge --update $PO_file $POT_file else echo "WARNING: $POT_path/$(basename $PO_file .$lang.po).pot does not exist!!" fi
done
POT_file="" PO_file=""
echo "" echo ""
# Create PO files for new POT files for POT_file in `ls $POT_path/*.pot`; do echo $(basename $POT_file .pot) PO_file=$PO_path/$(basename $POT_file .pot).$lang.po if [[ -e $PO_file ]] then # POT and PO files exist => nothing to do echo "NOTE: $PO_file exist. Nothing to do" else echo "NOTE: $PO_file does not exist. Creating PO file." msginit --no-translator --locale=$lang --input=$POT_file --output-file=$PO_file fi
done
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2011-03-09 at 12:12 -0300, Luiz Fernando Ranghetti wrote:
Hi,
Just a little suggestion. If you use Lokalize, try msgmerge with --previous option too (in Lokalize it shows what changes in the string when it became fuzzy)
I changed the script accordingly, so that I use it next time. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk15cSYACgkQtTMYHG2NR9UXQACcDizF+YP0BfWfObxrIwp/PQRS 4ugAn0JjCK7xc560fhu53NAQBqJUkr0L =Iye3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2011-03-07 at 10:08 +0100, Andrea Turrini wrote:
Karl, can you synchronize the Italian version? I tried using Carlos' scripts but I have found some problem generating new po files from pot.
I read you don't need it now, but my script assumes you have a tree structure like it is on the svn server: cer@Telcontar:~/Projects/babel/SuSE/trunk/webyast> tree -d . |-- 00-etc |-- 00-memory |-- 00-pot |-- 00-tools `-- es `-- po It uses the 00-pot and po directories. Obviously you need to change "es" with your language. And as a parameter it takes the .po file. Or this line to do all: for I in `ls *po` ; do ../../../applypot_webyast $I ; done The script is basically taken from the original makefiles and scripts, but small so that I can control it and know what it does. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk105ZIACgkQtTMYHG2NR9WO+ACdGODLjBYZrFuFEDJWxNt9Z8IU LaoAn2K1wojXJv4Slgh0VHRCRQnXnwCm =iMjH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2011/3/7 Carlos E. R. <carlos.e.r@opensuse.org>:
I read you don't need it now, but my script assumes you have a tree structure like it is on the svn server:
cer@Telcontar:~/Projects/babel/SuSE/trunk/webyast> tree -d . |-- 00-etc |-- 00-memory |-- 00-pot |-- 00-tools `-- es `-- po
It uses the 00-pot and po directories. Obviously you need to change "es" with your language. And as a parameter it takes the .po file. Or this line to do all:
for I in `ls *po` ; do ../../../applypot_webyast $I ; done
The script is basically taken from the original makefiles and scripts, but small so that I can control it and know what it does.
I have not found problems with the applypot_webyast script, but with the crearpo_webyast script. But probably I have made some mistake using it... I also tried with Guillaume's script and it work good, as your scripts (now that I tried again). But since I am not expert with pot files and msg-tools, I prefer someone else generates po files for me, so the only things I need to do are: svn update, translate, svn update, svn commit ;-) Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2011-03-07 at 15:27 +0100, Andrea Turrini wrote:
2011/3/7 Carlos E. R. <>:
I have not found problems with the applypot_webyast script, but with the crearpo_webyast script. But probably I have made some mistake using it...
The assumptions are the same, but you feed it with the pot name: cer@Telcontar:~/Projects/babel/SuSE/trunk/webyast/es/po> ~/Projects/babel/SuSE/crearpo_webyast ../../00-pot/webyast-software-ws.pot The .pot extension is ignored, as is the path. It created a Spanish (es_ES) po that has to be further initialized by kbabel or whatever you use, the header is minimal. You would have to edit the string to change the locale to Italian, of course. I wrote the scripts for myself, so they might need ironing.
I also tried with Guillaume's script and it work good, as your scripts (now that I tried again).
But since I am not expert with pot files and msg-tools, I prefer someone else generates po files for me, so the only things I need to do are: svn update, translate, svn update, svn commit ;-)
Me too :-) But sometimes I'm on a hurry. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk108csACgkQtTMYHG2NR9W+dQCdFWl8KhYlC+FxrQvCpMYSSHdT hXIAn2Z69z4Kim1yAtXOxmIwVIczx4hu =zRRf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Le 07/03/2011 15:27, Andrea Turrini a écrit :
I read you don't need it now, but my script assumes you have a tree structure like it is on the svn server:
cer@Telcontar:~/Projects/babel/SuSE/trunk/webyast> tree -d . |-- 00-etc |-- 00-memory |-- 00-pot |-- 00-tools `-- es `-- po
It uses the 00-pot and po directories. Obviously you need to change "es" with your language. And as a parameter it takes the .po file. Or this line to do all:
for I in `ls *po` ; do ../../../applypot_webyast $I ; done
The script is basically taken from the original makefiles and scripts, but small so that I can control it and know what it does. I have not found problems with the applypot_webyast script, but with
2011/3/7 Carlos E. R.<carlos.e.r@opensuse.org>: the crearpo_webyast script. But probably I have made some mistake using it...
I also tried with Guillaume's script and it work good, as your scripts (now that I tried again).
But since I am not expert with pot files and msg-tools, I prefer someone else generates po files for me, so the only things I need to do are: svn update, translate, svn update, svn commit ;-) Karl updated the PO files so you can : svn update, translate, svn commit ! ;)
Guillaume
Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2011-03-07 at 10:00 +0100, Karl Eichwalder wrote:
"Carlos E. R." <> writes:
I have already translated the Spanish side of webyast and uploaded it to the svn at berlios. I fear this is too late for 11.4 GM (although I opened a Bugzilla about this on Feb 14), so I would really like to see this update package distributed via YOU.
Please, assign it to me.
Done.
Are you still busy with translating webyast? How much time do you need for preparing this Update?
The Spanish translation is done. I can still review it, looking at things a second time catches things.
I'd like to submit the packages end of this week or early next week.
Perhaps early next week will leave time for other teams to work over the weekend. If teams had webyast fully translated for 11.3, the changes for 11.4 are doable in a few hours. If they have to translate it fully, then it takes a long time. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk102vIACgkQtTMYHG2NR9VkAgCeM/re8p2x18mRmse8ANSwfFfF miEAniRx1a8mQDWlJFm7/KhULM04Uzdo =DIGB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2011/3/7 Carlos E. R. <carlos.e.r@opensuse.org>:
Are you still busy with translating webyast? How much time do you need for preparing this Update?
The Spanish translation is done. I can still review it, looking at things a second time catches things.
Also Italian translation is done. Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (7)
-
Andrea Turrini -
Carlos E. R. -
Guillaume Gardet -
Karl Eichwalder -
Kálmán Kéménczy -
Luiz Fernando Ranghetti -
Olav P.