[opensuse-translation] We need urgent clarification on translation start date
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! See this (http://en.opensuse.org/Roadmap/11.0): Thu, Apr 17 openSUSE 11.0 Beta 1 release * Milestone: installation workflow is feature frozen * Proofreading of all software starts so that we have a new baseline. * Milestone: Feature and version freeze for the complete distribution (exception: patchlevel update of leaf packages until Beta1+) * Milestone: First localized build * Milestone: Complete string freeze * Milestone: All features are coding and function complete. * Milestone: Kernel and install works on all targeted machines. => * Milestone: Last round of software translation starts - "hard text freeze" * Milestone: Documentation deadline ("authoring deadline") for localized manuals, proofing starts, first source drop (locdrop) to Localization for volume estimates * Milestone: all new desktop applications, incl. KDE 4 apps, to ship with the product are integrated Mon, Apr 21 Main translation round * Milestone: All packages submitted latest POT file into SVN * 12:00 CEST: Developers to check in the POTs for the 2nd cycle of software translation So, the translation starts on 17th or 21th? I thought it was 21th, but some in our team thought that "string freeze" means that translators have the free to go flag. What is the correct date? What should we be doing now? I have seen some pots updates during this period... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICcAGtTMYHG2NR9URAp1kAJ0dABvuebZ+4y+oWZT9rFBgMdwxMgCfeHd5 zKUn9yIs3ac+Kt1ycHa9sMk= =NqsU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Am Samstag, 19. April 2008 schrieb Carlos E. R.:
So, the translation starts on 17th or 21th?
I thought it was 21th, but some in our team thought that "string freeze" means that translators have the free to go flag.
What is the correct date? What should we be doing now?
I have seen some pots updates during this period...
For bug fixes or and two strings hopefully. 17th is the start to translate 99% - 1% may slip in after that to fix feedback we got for beta1. Greetings, Stephan --------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 12:16 +0200, Stephan Kulow wrote:
Am Samstag, 19. April 2008 schrieb Carlos E. R.:
So, the translation starts on 17th or 21th?
I thought it was 21th, but some in our team thought that "string freeze" means that translators have the free to go flag.
What is the correct date? What should we be doing now?
I have seen some pots updates during this period...
For bug fixes or and two strings hopefully. 17th is the start to translate 99% - 1% may slip in after that to fix feedback we got for beta1.
And how do we handle collisions? Currently we reject the new translated file, work is lost... (the affected translator has no svn access, uses poat) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICcyDtTMYHG2NR9URAqMoAJ9qk6b9qw6Fn4KrB8x+JvXSiGAYagCcDMci vf4BgVooYMGNGFyAocxbDGg= =rsRa -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Can't you merge the files ? Cheers, Guillaume Carlos E. R. a écrit :
The Saturday 2008-04-19 at 12:16 +0200, Stephan Kulow wrote:
Am Samstag, 19. April 2008 schrieb Carlos E. R.:
So, the translation starts on 17th or 21th?
I thought it was 21th, but some in our team thought that "string freeze" means that translators have the free to go flag.
What is the correct date? What should we be doing now?
I have seen some pots updates during this period...
For bug fixes or and two strings hopefully. 17th is the start to translate 99% - 1% may slip in after that to fix feedback we got for beta1.
And how do we handle collisions? Currently we reject the new translated file, work is lost...
(the affected translator has no svn access, uses poat)
-- Cheers, Carlos E. R.
--------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 12:45 +0200, Guillaume Gardet wrote:
Can't you merge the files ?
Let me explain the procedure. A translator without SVN access emails, via POAT, his newly translated file to someone, like me. I run "svn up", then copy that file to my SVN local copy, then run "svn commit", and I get a big error with collision, and prbably three files: the one on the server, the new one from the translator, and a diff file. Result: abort. How can I commit the translated file, and add to it the changes from the new one on the server? If the file were mine, I'd use and editor looking at the diff file on one term and the new file on another. That's time consuming, and I would have to be doing that for half the team work. If I were the only translator, I would force commit of the newly translated file and then run "make update-po" locally so that changes in the .pot file gets added automatically, and finally I would commit that changed file, that hopefully would be correct. But I'm not the only translator, so I can't do that. If I knew of a procedure to apply the update-po to a single file, I would do that. But I don't know of such a procedure. I don't know of an automated procedure to "merge" those two files. I don't know what you mean by "merge". Therefore, all the Spanish team is right now siting doing nothing, since the 17th, waiting till this thread tells them how to continue. We are stuck :-( - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICd3xtTMYHG2NR9URAlEwAJsHcByHUnhm3vbikc0OZJMEJn06+wCdHF1A hZnAMppdl3yZfLkyo+/3r/k= =9Prp -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Am Samstag, 19. April 2008 schrieb Carlos E. R.:
The Saturday 2008-04-19 at 12:16 +0200, Stephan Kulow wrote:
Am Samstag, 19. April 2008 schrieb Carlos E. R.:
So, the translation starts on 17th or 21th?
I thought it was 21th, but some in our team thought that "string freeze" means that translators have the free to go flag.
What is the correct date? What should we be doing now?
I have seen some pots updates during this period...
For bug fixes or and two strings hopefully. 17th is the start to translate 99% - 1% may slip in after that to fix feedback we got for beta1.
And how do we handle collisions? Currently we reject the new translated file, work is lost...
Because you don't see if automerge or another translator commited? That's bad then. This needs fixing in the tool then. Greetings, Stephan --------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 14:49 +0200, Stephan Kulow wrote:
And how do we handle collisions? Currently we reject the new translated file, work is lost...
Because you don't see if automerge or another translator commited? That's bad then. This needs fixing in the tool then.
Sorry, I have no idea what you are talking about :-? Please read my answer to Guillaume for an explanation of what is hapening to us. What is the correct procedure to merge a finished translation, with a file in the SVN that has been updated by some one outside of our team, probably the result of a new .pot file with new messages or modified messages? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICd65tTMYHG2NR9URAsVmAJ96Iz73ym6Ov6uDGgkjRW6PymlxIACaAptu IB46RQUEWnXG5egUe8U6oLs= =/Ypd -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Am Samstag, 19. April 2008 schrieb Carlos E. R.:
The Saturday 2008-04-19 at 14:49 +0200, Stephan Kulow wrote:
And how do we handle collisions? Currently we reject the new translated file, work is lost...
Because you don't see if automerge or another translator commited? That's bad then. This needs fixing in the tool then.
Sorry, I have no idea what you are talking about :-?
Please read my answer to Guillaume for an explanation of what is hapening to us.
What is the correct procedure to merge a finished translation, with a file in the SVN that has been updated by some one outside of our team, probably the result of a new .pot file with new messages or modified messages?
If you're the only one with SVN access and you're sure that you do not overwrite other people's work, just svn up; copy file; svn ci. If you wait too long between svn up and svn ci; do: svn revert file; svn up; copy file; svn ci. Greetings, Stephan --------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 16:18 +0200, Stephan Kulow wrote:
What is the correct procedure to merge a finished translation, with a file in the SVN that has been updated by some one outside of our team, probably the result of a new .pot file with new messages or modified messages?
If you're the only one with SVN access and you're sure that you do not overwrite other people's work, just svn up; copy file; svn ci. If you wait too long between svn up and svn ci; do: svn revert file; svn up; copy file; svn ci.
No, we are two or three people with svn write access, and a few more without. The procedure you describe is what we do, and we get collisions: 1) Translator 'A' downloads a file via the http interface, and translates it, taking perhaps several days. 2) During this time, a developer changes the .pot file, changes get to the .po in the server copy. Translator 'A' does not know anything about this, nor can he/she do anything even if he/she knows. 3) Translator 'A' emails, via Verbum aka Poat, the file to the pool of translators having svn write access 4) One of the several translators with svn access, say 'B', takes the file. 5) Translator 'B' does: - svn up - copy file to local tree - svn commit 6a) Translator 'B' gets a collision, and simply rejects the file. We are stuck. 6b) Alternatively, translator 'B' overwrites the developer changes, committing translator 'A' file, destroying whatever the developer changed. 7) If the translation is now packaged, some strings will not be translated. I hope this helps to understand our problem :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICgdQtTMYHG2NR9URAnvoAJ97sNSpI5bqMERzgyPHQc+IMO8/6wCfenzh DsADGF/6peqBWiARaYuZcLc= =Y58O -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Ok. - You download your file. - You translate it in several days (say seven days). - Two days after you took the file (five days before you try to commit it) a developer updates the .pot and the .po on the server updates automatically. - You have translated the file an you try to do svn ci. - It fails. -Then you have to do a backup of your file (for when doing svn update your translations doesnt dissapear). - Then you do svn update. - You copy the backup over the .po file downloaded in the previous step from the server using svn update. - You merge it with the latest .pot (remember to checkout it from the server) - You translate the new strings - You do svn ci (now it works) Bye, Leandro Regueiro --------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 18:13 +0200, Leandro Regueiro wrote:
Ok.
- You download your file. - You translate it in several days (say seven days). - Two days after you took the file (five days before you try to commit it) a developer updates the .pot and the .po on the server updates automatically. - You have translated the file an you try to do svn ci. - It fails. -Then you have to do a backup of your file (for when doing svn update your translations doesnt dissapear). - Then you do svn update. - You copy the backup over the .po file downloaded in the previous step from the server using svn update. - You merge it with the latest .pot (remember to checkout it from the server)
What is a merge? An svn operation? There is a command "svn merge". You mean that? cer@nimrodel:~> svn help merge merge: Apply the differences between two sources to a working copy path. usage: 1. merge sourceURL1[@N] sourceURL2[@M] [WCPATH] 2. merge sourceWCPATH1@N sourceWCPATH2@M [WCPATH] 3. merge [-c M | -r N:M] SOURCE[@REV] [WCPATH] What exactly do I type? Or do you mean a manual operation, using an editor to mix both files, the one on the server and the one from the translator? That's not my job, I'm not the translator. I'm the commiter. See below.
- You translate the new strings
Impossible.
- You do svn ci (now it works)
You forget that I'm not the translator that translated that file. I'm only the one uploading it. There are two translators involved, using Verbum. If we don't find an automated procedure soon, what we'll do is commit the translator file deleting the developer file. :-/ Meanwhile, the entire (ES) team is stopped, waiting for an answer. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICjFztTMYHG2NR9URAqBWAJ451mhT74ZELPue7f7o1364tnex7wCfZ9p8 iZSrsLfOQE5d6zeSULNEWYs= =OBpj -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
- You download your file. - You translate it in several days (say seven days). - Two days after you took the file (five days before you try to commit it) a developer updates the .pot and the .po on the server updates automatically. - You have translated the file an you try to do svn ci. - It fails. -Then you have to do a backup of your file (for when doing svn update your translations doesnt dissapear). - Then you do svn update. - You copy the backup over the .po file downloaded in the previous step from the server using svn update. - You merge it with the latest .pot (remember to checkout it from the server)
What is a merge? An svn operation? There is a command "svn merge". You mean that?
Or do you mean a manual operation, using an editor to mix both files, the one on the server and the one from the translator? That's not my job, I'm not the translator. I'm the commiter. See below.
No, it isn't a svn operation. The merge is the operation of updating a .po file with a newer .pot file. You could do it with a .po editor, like Poedit, or using the gettext tool: msgmerge --update yourpofile.po newerpotfile.pot
- You translate the new strings
Impossible.
It is possible, but if you don't want to do it, no matter.
- You do svn ci (now it works)
You forget that I'm not the translator that translated that file. I'm only the one uploading it. There are two translators involved, using Verbum.
If we don't find an automated procedure soon, what we'll do is commit the translator file deleting the developer file. :-/
You could automate this in some way with a script. See the command above. Bye, Leandro Regueiro --------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 22:25 +0200, Leandro Regueiro wrote:
Or do you mean a manual operation, using an editor to mix both files, the one on the server and the one from the translator? That's not my job, I'm not the translator. I'm the commiter. See below.
No, it isn't a svn operation. The merge is the operation of updating a .po file with a newer .pot file. You could do it with a .po editor, like Poedit, or using the gettext tool:
msgmerge --update yourpofile.po newerpotfile.pot
Is this what the "make update-po" does? That would suffice. I have been loking for a method of replicating what "make update-po" does, but on a single file (I believe it also uses the memory files). That would be the best solution.
- You translate the new strings
Impossible.
It is possible, but if you don't want to do it, no matter.
It is extra work for a file that is not mine, and even worse when I'm sure there is an automated way of doing it; simply I do not know it.
If we don't find an automated procedure soon, what we'll do is commit the translator file deleting the developer file. :-/
You could automate this in some way with a script. See the command above.
That command is what I'm looking for, although it misses the memory part. What we need is a method to do an update-po on a single file. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICmJbtTMYHG2NR9URAmj3AJ9IHampH3ew1Paq8LXwB9Mx3RfMCwCeKqKA TL8K+mvJJJ3VZwdB2amtLIg= =uo6c -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Or do you mean a manual operation, using an editor to mix both files, the one on the server and the one from the translator? That's not my job, I'm not the translator. I'm the commiter. See below.
No, it isn't a svn operation. The merge is the operation of updating a .po file with a newer .pot file. You could do it with a .po editor, like Poedit, or using the gettext tool:
msgmerge --update yourpofile.po newerpotfile.pot
Is this what the "make update-po" does? That would suffice. I have been loking for a method of replicating what "make update-po" does, but on a single file (I believe it also uses the memory files). That would be the best solution.
Yes. But it doesn't use memory translation.
If we don't find an automated procedure soon, what we'll do is commit the translator file deleting the developer file. :-/
You could automate this in some way with a script. See the command above.
That command is what I'm looking for, although it misses the memory part.
What we need is a method to do an update-po on a single file.
Open the update-po to see what it does. But I think that if you don't care about the translation process, and you only are a comitter, this command is the only thing you need. The translators could do the part of the memory, the translation, and that other stuff that you don't want to do. Bye, Leandro Regueiro --------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 23:26 +0200, Leandro Regueiro wrote:
msgmerge --update yourpofile.po newerpotfile.pot
Is this what the "make update-po" does? That would suffice. I have been loking for a method of replicating what "make update-po" does, but on a single file (I believe it also uses the memory files). That would be the best solution.
Yes. But it doesn't use memory translation.
I know, the command above doesn't use memory. The Makefile does.
What we need is a method to do an update-po on a single file.
Open the update-po to see what it does.
I did, several times, but I don't understand it. I know that something somewhere does something like this (looking at an old log output): echo $po; \ if [ -f $po ]; then \ msgmerge --no-wrap --force-po -U $po -C ../../50-memory/memory.es.po $p; \ else \ msgmerge --no-wrap --force-po -o $po -C ../../50-memory/memory.es.po \ --verbose /dev/null $p; \ fi || { echo "msgmerge --no-wrap --force-po for \"$po\" failed" ; }; \ msgfmt --check --stat $po ; \ done which I think applies memory, but not pot.
But I think that if you don't care about the translation process, and you only are a comitter, this command is the only thing you need. The translators could do the part of the memory, the translation, and that other stuff that you don't want to do.
You don't understand. I'm also a translator, and I commit the files I translate myself. I also have to commit files from others, and those I can not do the merge. In the case of the files I translate, my local copy probably overwrites the server copy without my noticing (because a kbabel save will overwrite a previous "svn up" run without telling). As to the translators doing the part of the memory... imposible. Nobody knows how to do that. I wrote most of the instructions and I don't know it... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICmiZtTMYHG2NR9URAmfLAJ9DinYtNzFT117CXc019lPZmkkhiACfRHrG OybYu/qwKeKDgDffuNN74TA= =jN/J -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
msgmerge --update yourpofile.po newerpotfile.pot
Is this what the "make update-po" does? That would suffice. I have been loking for a method of replicating what "make update-po" does, but on a single file (I believe it also uses the memory files). That would be the best solution.
Yes. But it doesn't use memory translation.
I know, the command above doesn't use memory. The Makefile does.
What we need is a method to do an update-po on a single file.
Open the update-po to see what it does.
I did, several times, but I don't understand it.
I know that something somewhere does something like this (looking at an old log output):
echo $po; \ if [ -f $po ]; then \ msgmerge --no-wrap --force-po -U $po -C ../../50-memory/memory.es.po $p; \ else \ msgmerge --no-wrap --force-po -o $po -C ../../50-memory/memory.es.po \ --verbose /dev/null $p; \ fi || { echo "msgmerge --no-wrap --force-po for \"$po\" failed" ; }; \ msgfmt --check --stat $po ; \ done
which I think applies memory, but not pot.
This uses a po compendium that is different to translation memories.
But I think that if you don't care about the translation process, and you only are a comitter, this command is the only thing you need. The translators could do the part of the memory, the translation, and that other stuff that you don't want to do.
You don't understand. I'm also a translator, and I commit the files I translate myself. I also have to commit files from others, and those I can not do the merge.
In the case of the files I translate, my local copy probably overwrites the server copy without my noticing (because a kbabel save will overwrite a previous "svn up" run without telling).
As to the translators doing the part of the memory... imposible. Nobody knows how to do that. I wrote most of the instructions and I don't know it...
Then don't use the memories. You don't need them for nothing. The example I put on my first message is to explain how to commit yours (or others) translation if the file changes in the serves after you (or others) start translating that file. This is the only thing you need (and to use the svn command and a program to translate the files :) ). Bye, Leandro Regueiro --------------------------------------------------------------------- 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 The Saturday 2008-04-19 at 23:56 +0200, Leandro Regueiro wrote:
which I think applies memory, but not pot.
This uses a po compendium that is different to translation memories.
I found the complete code excerpt from the above, modified it, and got this piece of code that appears to work: #!/bin/bash F=`basename $1 .po` FF=`basename $F .es` POFILE=$FF.es.po POTFILE=../../50-pot/$FF.pot if test -f $POFILE -a -f $POTFILE; then echo Applying msgmerge to $POFILE msgmerge --no-wrap --force-po -U $POFILE -C \ ../../50-memory/memory.es.po $POTFILE msgfmt --check --stat $POFILE rm messages.mo else echo "Not found: " $POFILE and $POTFILE fi || { echo "msgmerge --no-wrap --force-po for \"$po\" failed" ; }
As to the translators doing the part of the memory... imposible. Nobody knows how to do that. I wrote most of the instructions and I don't know it...
Then don't use the memories. You don't need them for nothing. The example I put on my first message is to explain how to commit yours (or others) translation if the file changes in the serves after you (or others) start translating that file. This is the only thing you need (and to use the svn command and a program to translate the files :) ).
Ok. But this should have been explained somewhere so that newcomers can know how to handle this situation. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFICoAjtTMYHG2NR9URAm9+AKCV4yGY2E4IBgQ+XGZyOku9RMc8JwCfYPxo 0fXnZR5CYWmiKm5f7Ga23dg= =+8KU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
which I think applies memory, but not pot.
This uses a po compendium that is different to translation memories.
I found the complete code excerpt from the above, modified it, and got this piece of code that appears to work:
#!/bin/bash
F=`basename $1 .po` FF=`basename $F .es` POFILE=$FF.es.po POTFILE=../../50-pot/$FF.pot
if test -f $POFILE -a -f $POTFILE; then echo Applying msgmerge to $POFILE msgmerge --no-wrap --force-po -U $POFILE -C \ ../../50-memory/memory.es.po $POTFILE msgfmt --check --stat $POFILE rm messages.mo else echo "Not found: " $POFILE and $POTFILE
fi || { echo "msgmerge --no-wrap --force-po for \"$po\" failed" ; }
Instead of using rm you could modify the msgfmt this way: msgfmt --check --statistics -o /dev/null $POFILE
As to the translators doing the part of the memory... imposible. Nobody knows how to do that. I wrote most of the instructions and I don't know it...
Then don't use the memories. You don't need them for nothing. The example I put on my first message is to explain how to commit yours (or others) translation if the file changes in the serves after you (or others) start translating that file. This is the only thing you need (and to use the svn command and a program to translate the files :) ).
Ok.
But this should have been explained somewhere so that newcomers can know how to handle this situation.
Then update the wiki. Bye, Leandro Regueiro --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (5)
-
Carlos E. R. -
Carlos E. R. -
Guillaume Gardet -
Leandro Regueiro -
Stephan Kulow