Hi all,
in about 10 days the last round of translations should start (MS 3) but at the moment there are essentially no new/fuzzy strings to translate.
Since I do not think that there are no string changes, is it possible to have updated strings in the repository? Moreover, is it possible to induce developers to update/regenerate the POT files? so we are sure that translations are still good.
Best, Andrea
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-27 19:38, Andrea Turrini wrote:
Hi all,
in about 10 days the last round of translations should start (MS 3) but at the moment there are essentially no new/fuzzy strings to translate.
Last round? I thought the translation round has not even started!
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
On 27/03/12 20:47, Carlos E. R. wrote:
On 2012-03-27 19:38, Andrea Turrini wrote:
Hi all,
in about 10 days the last round of translations should start (MS 3) but at the moment there are essentially no new/fuzzy strings to translate.
Last round? I thought the translation round has not even started!
I just reported the description of MS3 in coolo's timeline [1]: Milestone: Last round of software translation starts - "hard text freeze"
Then there are MS4 (Apr. 26): first localized build and Jun. 6: translation finish
Best, Andrea
[1] http://www.suse.de/~coolo/opensuse_12.2/
It's good there is someone still looking at the Roadmap =) I beleive there should be string updates at least in yast bootloader module since grub2 is named to be integrated. I don't expect many new strings elsewhere (cause main features are new GCC, ARM port and plymouth - so, no new work for translators), but some fuzzy stuff definitely should pop up here and there.
Alexander Melentyev minton@opensuse.org writes:
It's good there is someone still looking at the Roadmap =)
If someone could help with translation coordination, it would be great ;) Lately, we unfortunately once again had to change the SVN server (now opensuse.org), thus some things must settle again...
I beleive there should be string updates at least in yast bootloader module since grub2 is named to be integrated. I don't expect many new strings elsewhere (cause main features are new GCC, ARM port and plymouth - so, no new work for translators), but some fuzzy stuff definitely should pop up here and there.
Some time ago, we did a partial yast proofreading for SLE 11 SP2, and I guess we still can make use of some of these improvements for openSUSE 12.2. I just asked Lukas and Jiri to merge in what is possible and then submit fresh yast pot files to the trunk of our SVN server.
In the afternoon, I'll approach the other developers to refresh the lcn files.
Thus, stay tuned ;)
Le 29/03/2012 11:34, Karl Eichwalder a écrit :
Alexander Melentyev minton@opensuse.org writes:
It's good there is someone still looking at the Roadmap =)
If someone could help with translation coordination, it would be great ;) Lately, we unfortunately once again had to change the SVN server (now opensuse.org), thus some things must settle again...
What kind of help is needed?
I beleive there should be string updates at least in yast bootloader module since grub2 is named to be integrated. I don't expect many new strings elsewhere (cause main features are new GCC, ARM port and plymouth - so, no new work for translators), but some fuzzy stuff definitely should pop up here and there.
Some time ago, we did a partial yast proofreading for SLE 11 SP2, and I guess we still can make use of some of these improvements for openSUSE 12.2. I just asked Lukas and Jiri to merge in what is possible and then submit fresh yast pot files to the trunk of our SVN server.
In the afternoon, I'll approach the other developers to refresh the lcn files.
Thus, stay tuned ;)
Thanks,
Guillaume
Guillaume Gardet guillaume.gardet@free.fr writes:
What kind of help is needed?
Thanks for asking! I'll answer it below.
The first simple thing that helps, is watching coolo's roadmap, discussing the translation related entries here and then pushing all the other involved persons (including me ;) ).
Alexander Melentyev minton@opensuse.org writes:
2012/3/29 Karl Eichwalder ke@suse.de:
Alexander Melentyev minton@opensuse.org writes:
If someone could help with translation coordination, it would be great ;) Lately, we unfortunately once again had to change the SVN server (now opensuse.org), thus some things must settle again...
Yeah, on berlios I could add new translators, but now it's purely your ability (no community admins on svn.opensuse.org)
Yes, I know. And the last one, whom I'm blaming, is you, of course! I'm very happy that we finally managed that you can maintain i18n.opensuse.org.
Daniel gave up a script that helps with password encoding and requesting an account on opensuse.org. We simply must document it. Updating the translation related docs on the openSUSE wiki is also still an issue; if someone could take a look there, it would be great.
I just asked Lukas and Jiri to merge in what is possible and then submit fresh yast pot files to the trunk of our SVN server.
So, you know the right guys and (more important) they know you, too. I can't imagine someone will do extra work cause of some unknown guy has told'em to do so. They do the merge only because it's you who ask them, not for some formal reason.
Lukas just told me that we'd better use the yast-devel ML for these purposes. I'll do so in the future and next time we can organize this better (e.g., a community member sends these reminder mails, with explicit cc: to me).
Here's the same situation: everybody knows that Karl Eichwalder is the man in charge with translations, so it'll be better to do what he says. The whole process is running not as formal act, but as personal relations act. So, you have to do it personally, there is no way you can escape from it =)
In this case, all the data are publically available on the SVN server; I'll document it a little bit better next time.
2012/3/29 Karl Eichwalder ke@suse.de:
Alexander Melentyev minton@opensuse.org writes:
It's good there is someone still looking at the Roadmap =)
If someone could help with translation coordination, it would be great ;) Lately, we unfortunately once again had to change the SVN server (now opensuse.org), thus some things must settle again...
Yeah, on berlios I could add new translators, but now it's purely your ability (no community admins on svn.opensuse.org)
Lack of help is happening because there is a lack of understanding the process. For example, you say
I just asked Lukas and Jiri to merge in what is possible and then submit fresh yast pot files to the trunk of our SVN server.
So, you know the right guys and (more important) they know you, too. I can't imagine someone will do extra work cause of some unknown guy has told'em to do so. They do the merge only because it's you who ask them, not for some formal reason.
In the afternoon, I'll approach the other developers to refresh the lcn files.
Here's the same situation: everybody knows that Karl Eichwalder is the man in charge with translations, so it'll be better to do what he says. The whole process is running not as formal act, but as personal relations act. So, you have to do it personally, there is no way you can escape from it =)
Thus, stay tuned ;)
Glad to here the merge is coming.
Karl Eichwalder ke@suse.de writes:
Some time ago, we did a partial yast proofreading for SLE 11 SP2, and I guess we still can make use of some of these improvements for openSUSE 12.2. I just asked Lukas and Jiri to merge in what is possible and then submit fresh yast pot files to the trunk of our SVN server.
New pot files are now available and I'll call the merge script now :-)
In the afternoon, I'll approach the other developers to refresh the lcn files.
This unfortunately will take a little bit longer.
Karl Eichwalder ke@suse.de writes:
New pot files are now available and I'll call the merge script now :-)
Something worth to add:
There are several modules that are not useful in the openSUSE context. coolo identified those last time and they defined in 50-tools/y2-prep-packages.sh, my old and ugly merge script:
business="CASA casa-ats heartbeat kernel-update-tool linux-user-mgmt \ registration s390 slepos-installation xpram"
I'll move this info to the 50-etc directory soon.
I no longer merge them and ignore them while building the openSUSE translation packages--but they are probably still confusing... I'm not that what we should actually do with these files.
Some background: The yast developers cannot easily identify, which files are needed for SLE only. Thus they will submit everything when asked to update the pot files ;)
In the afternoon, I'll approach the other developers to refresh the lcn files.
This unfortunately will take a little bit longer.
I just asked the maintainers to submit new pot files; this is the reminder mail sent to them:
[You receive this message because you are one of the POT file maintainers listed in https://svn.opensuse.org/svn/opensuse-i18n/trunk/lcn/50-pot/MAINTAINERS.]
We moved the openSUSE translation SVN from Berlios to opensuse.org; we also transferred the password file. So, either use the same password that you know by heart, or look it up somewhere at ~/.subversion/auth/ .
Please, submit the "@PACKAGE@" POT file later this week to:
https://svn.opensuse.org/svn/opensuse-i18n/trunk/lcn/50-pot
Edit the MAINTAINERS file, if necessary: add new files and remove obsoletes.
If you need help, ask Karl Eichwalder ke@suse.de.
Am Dienstag, 3. April 2012, 10:56:07 schrieb Karl Eichwalder:
business="CASA casa-ats heartbeat kernel-update-tool linux-user-mgmt \ registration s390 slepos-installation xpram"
I'll move this info to the 50-etc directory soon.
No pushing, just a friendly reminder :-)
I no longer merge them and ignore them while building the openSUSE translation packages--but they are probably still confusing... I'm not that what we should actually do with these files.
Do you want to move the translations itself too or just the .pot files? Should we delete those files ourself or will you do it?
Regards, Michael
Michael Skiba mailinglist@michael-skiba.de writes:
Am Dienstag, 3. April 2012, 10:56:07 schrieb Karl Eichwalder:
business="CASA casa-ats heartbeat kernel-update-tool linux-user-mgmt \ registration s390 slepos-installation xpram"
I'll move this info to the 50-etc directory soon.
No pushing, just a friendly reminder :-)
Yeah, for yast, this info ended up here (because an etc directory does not exist):
trunk/yast/50-tools/build.conf
I no longer merge them and ignore them while building the openSUSE translation packages--but they are probably still confusing... I'm not that what we should actually do with these files.
Do you want to move the translations itself too or just the .pot files? Should we delete those files ourself or will you do it?
That's the question. ATM, I just do not merge them and do not package them. Maybe, it is the best to move this stuff to a yast-sle (sle = SUSE Linux Enterprise) directory?
Am Donnerstag, 12. April 2012, 11:11:37 schrieb Karl Eichwalder:
Do you want to move the translations itself too or just the .pot files? Should we delete those files ourself or will you do it?
That's the question. ATM, I just do not merge them and do not package them. Maybe, it is the best to move this stuff to a yast-sle (sle = SUSE Linux Enterprise) directory?
If that's possible I think it's a good idea. I just want them out of our working directories so that noone accidentally translates them and thus wastes translation/proofreading capacities on unused files.
Regards, Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-12 11:22, Michael Skiba wrote:
Am Donnerstag, 12. April 2012, 11:11:37 schrieb Karl Eichwalder:
If that's possible I think it's a good idea. I just want them out of our working directories so that noone accidentally translates them and thus wastes translation/proofreading capacities on unused files.
Yes, please! :-)
If a .pot exists and not the .po, I usually find out and create it.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
Hi all,
2012/4/12 Carlos E. R. robin.listas@telefonica.net:
On 2012-04-12 11:22, Michael Skiba wrote:
If that's possible I think it's a good idea. I just want them out of our working directories so that noone accidentally translates them and thus wastes translation/proofreading capacities on unused files.
Yes, please! :-)
If a .pot exists and not the .po, I usually find out and create it.
I have just noted that there has been an update regarding some of the mentioned files.
Do you confirm that we can ignore such updates?
Best, Andrea
2012/4/18 Andrea Turrini andrea.turrini@gmail.com:
I have just noted that there has been an update regarding some of the mentioned files.
Do you confirm that we can ignore such updates?
Yes, ignore it totally. I accidently started the automerge script wrong way, sorry for the mess.
Best, Andrea
Am Donnerstag, 12. April 2012, 11:11:37 schrieb Karl Eichwalder:
I no longer merge them and ignore them while building the openSUSE translation packages--but they are probably still confusing... I'm not that what we should actually do with these files.
Do you want to move the translations itself too or just the .pot files? Should we delete those files ourself or will you do it?
That's the question. ATM, I just do not merge them and do not package them. Maybe, it is the best to move this stuff to a yast-sle (sle = SUSE Linux Enterprise) directory?
Any news?
2012/5/4 Michael Skiba mailinglist@michael-skiba.de:
Am Donnerstag, 12. April 2012, 11:11:37 schrieb Karl Eichwalder:
I no longer merge them and ignore them while building the openSUSE translation packages--but they are probably still confusing... I'm not that what we should actually do with these files.
Do you want to move the translations itself too or just the .pot files? Should we delete those files ourself or will you do it?
That's the question. ATM, I just do not merge them and do not package them. Maybe, it is the best to move this stuff to a yast-sle (sle = SUSE Linux Enterprise) directory?
Any news?
If I have understood correctly [1], we have to translate every file, also SLE-related things since they are available in openSUSE:Factory (but they will not be included in installation media).
Best, Andrea
[1] http://lists.opensuse.org/opensuse-translation/2012-04/msg00143.html
Am Freitag, 4. Mai 2012, 12:56:15 schrieb Andrea Turrini:
If I have understood correctly [1], we have to translate every file, also SLE-related things since they are available in openSUSE:Factory (but they will not be included in installation media).
Yes, I see your point, but wouldn't it be acceptable to package the SLE translation instead? (where it exists)
There are probably not many openSUSE users that use the SLE-Modules for YaST and for those it would surely be acceptable to have a slightly delayed translation, imho. (Their translations are probably better, since non of my team has ever seen those sections before)
Kind Regards, Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-05-06 19:37, Michael Skiba wrote:
Yes, I see your point, but wouldn't it be acceptable to package the SLE translation instead? (where it exists)
I'd prefer not mixing them.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
translation@lists.opensuse.org
-
Alexander Melentyev -
Andrea Turrini -
Carlos E. R. -
Carlos E. R. -
Guillaume Gardet -
Karl Eichwalder -
Michael Skiba