I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
Hi, congratulations sheirf :)
cheers,
--- Sherif Abdelgawad sabdelg@redhat.com wrote:
I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
===== Gurban M. Tewekgeli
Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
Excellent work :)
How come you have got 5 extra strings than others? Perhaps some files are not quite in sync with the master pot file...
Here comes the question:: Should each language maintainer to ensure their po files are consistent with the pot file, or should it be the package maintainer's responsibilities?
Personally I prefer the former, since it will create less file conflict situations and give the language maintainer more control. Opinions anyone?
Sarah
在2004年09月07日的02:52，Sherif Abdelgawad写道：
I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
Hello, Sarah!
I suppose better choice is to make sure the consistents .po and .pot files by some automatic procedure.
Bernd wrote status page is regenerated about each 15 minutes. Is it possiple to carry out some checks and show warnings on status page?
I suggest at least two type of checks: - count of translated strings - equality of msgid strings in .po and .pot files
Regards, Andrew Martynov
Sarah Wang wrote:
Excellent work :)
How come you have got 5 extra strings than others? Perhaps some files are not quite in sync with the master pot file...
Here comes the question:: Should each language maintainer to ensure their po files are consistent with the pot file, or should it be the package maintainer's responsibilities?
Personally I prefer the former, since it will create less file conflict situations and give the language maintainer more control. Opinions anyone?
Sarah
在2004年09月07日的02:52，Sherif Abdelgawad写道：
I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
Good idea. I'm all for automation :) Maybe it can even be put into "pre-commit" check script to avoid possible file conflicts.
On Tue, 2004-09-07 at 16:49, Andrew Martynov wrote:
Hello, Sarah!
I suppose better choice is to make sure the consistents .po and .pot files by some automatic procedure.
Bernd wrote status page is regenerated about each 15 minutes. Is it possiple to carry out some checks and show warnings on status page?
I suggest at least two type of checks:
- count of translated strings
- equality of msgid strings in .po and .pot files
Regards, Andrew Martynov
Sarah Wang wrote:
Excellent work :)
How come you have got 5 extra strings than others? Perhaps some files are not quite in sync with the master pot file...
Here comes the question:: Should each language maintainer to ensure their po files are consistent with the pot file, or should it be the package maintainer's responsibilities?
Personally I prefer the former, since it will create less file conflict situations and give the language maintainer more control. Opinions anyone?
Sarah
在2004年09月07日的02:52，Sherif Abdelgawad写道：
I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
Why not run:
$ msgmerge translated.po reference.pot -o last_translation.po
thus if reference.pot is up to date (which it should) the last_translation.po file should be up to date too and ready to commit.
/Josep
On dt, 2004-09-07 at 12:28, Sarah Wang wrote:
Good idea. I'm all for automation :) Maybe it can even be put into "pre-commit" check script to avoid possible file conflicts.
On Tue, 2004-09-07 at 16:49, Andrew Martynov wrote:
Hello, Sarah!
I suppose better choice is to make sure the consistents .po and .pot files by some automatic procedure.
Bernd wrote status page is regenerated about each 15 minutes. Is it possiple to carry out some checks and show warnings on status page?
I suggest at least two type of checks:
- count of translated strings
- equality of msgid strings in .po and .pot files
Regards, Andrew Martynov
Sarah Wang wrote:
Excellent work :)
How come you have got 5 extra strings than others? Perhaps some files are not quite in sync with the master pot file...
Here comes the question:: Should each language maintainer to ensure their po files are consistent with the pot file, or should it be the package maintainer's responsibilities?
Personally I prefer the former, since it will create less file conflict situations and give the language maintainer more control. Opinions anyone?
Sarah
在2004年09月07日的02:52，Sherif Abdelgawad写道：
I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
Hello, Josep!
I thought we has discussed human factor in producing mistakes.
I always tried to check my translation before commit, and I founded two type of my mistake: - some strings (msgid and msgstr pair) was accidentally removed or added - msgid was modified (for example, changed count of spaces)
It is good idea to made pre-commit check for all modules.
Regards, Andrew Martynov
Josep Puigdemont wrote:
Why not run:
$ msgmerge translated.po reference.pot -o last_translation.po
thus if reference.pot is up to date (which it should) the last_translation.po file should be up to date too and ready to commit.
/Josep
On dt, 2004-09-07 at 12:28, Sarah Wang wrote:
Good idea. I'm all for automation :) Maybe it can even be put into "pre-commit" check script to avoid possible file conflicts.
On Tue, 2004-09-07 at 16:49, Andrew Martynov wrote:
Hello, Sarah!
I suppose better choice is to make sure the consistents .po and .pot files by some automatic procedure.
Bernd wrote status page is regenerated about each 15 minutes. Is it possiple to carry out some checks and show warnings on status page?
I suggest at least two type of checks:
- count of translated strings
- equality of msgid strings in .po and .pot files
Regards, Andrew Martynov
Sarah Wang wrote:
Excellent work :)
How come you have got 5 extra strings than others? Perhaps some files are not quite in sync with the master pot file...
Here comes the question:: Should each language maintainer to ensure their po files are consistent with the pot file, or should it be the package maintainer's responsibilities?
Personally I prefer the former, since it will create less file conflict situations and give the language maintainer more control. Opinions anyone?
Sarah
在2004年09月07日的02:52，Sherif Abdelgawad写道：
I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
Hi Andrew,
On dt, 2004-09-07 at 16:19, Andrew Martynov wrote:
Hello, Josep!
I thought we has discussed human factor in producing mistakes.
Oops, no, I wasn't talking about the human factor here, I was referring to the comment on your message about the consistence of .po files with their respective .pot file: http://www.redhat.com/archives/fedora-trans-list/2004-September/msg00008.htm...
I suppose better choice is to make sure the consistents .po and .pot files by some automatic procedure.
That's where msgmerge can help us with (provided .pot files are up to date).
I always tried to check my translation before commit, and I founded two type of my mistake:
- some strings (msgid and msgstr pair) was accidentally removed or
added
- msgid was modified (for example, changed count of spaces)
"Errare humanum est", but I believe there're more chances to make a bad translation than to mangle msgid strings if we don't touch them (and we're not supposed to). If you have any of the problems you described before, I would recommend you to find out why this actually happens, rather than to make a pre-commit script that should figure out what we did wrong. My guess is that you're modifying msgid strings, and we should _not_ do that (maybe the software being used does not respect the original msgid strings).
If one changes minimally a msgid, msgmerge can even make an entry fuzzy instead of wiping it out completely, that would really be cool, but it could also take a lot of CPU time for long .po files.
It is good idea to made pre-commit check for all modules.
It certainly is, and in fact the CVS server does check a file prior to its commit (try to commit an ill formatted po file, you'll see), I think there was another thread (long ago) talking about this.
Anyway, maybe my suggestion wouldn't be good for a pre-commit script, after all. I sent it here because it is what I usually do with my translations, and I thought it could be helpful to others too.
Regards, /Josep
Regards, Andrew Martynov
Josep Puigdemont wrote:
Why not run:
$ msgmerge translated.po reference.pot -o last_translation.po
thus if reference.pot is up to date (which it should) the last_translation.po file should be up to date too and ready to commit.
/Josep
On dt, 2004-09-07 at 12:28, Sarah Wang wrote:
Good idea. I'm all for automation :) Maybe it can even be put into "pre-commit" check script to avoid possible file conflicts.
On Tue, 2004-09-07 at 16:49, Andrew Martynov wrote:
Hello, Sarah!
I suppose better choice is to make sure the consistents .po and .pot files by some automatic procedure.
Bernd wrote status page is regenerated about each 15 minutes. Is it possiple to carry out some checks and show warnings on status page?
I suggest at least two type of checks:
- count of translated strings
- equality of msgid strings in .po and .pot files
Regards, Andrew Martynov
Hi
Why can't I see our beloved Arabic Translation mailing list at http://www.redhat.com/mailman/listinfo ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 07 September 2004 1:05 am, Sarah Wang wrote:
Excellent work :)
How come you have got 5 extra strings than others? Perhaps some files are not quite in sync with the master pot file...
Can you point which modules have those extra 5 ?? - --
Mohamed Eldesoky Systems Engineer RedHat Certified Engineer TE Data
On Yau al-Thulatha 22 Rajab 1425 1:05 am, Sarah Wang wrote:
Excellent work :)
How come you have got 5 extra strings than others? Perhaps some files are not quite in sync with the master pot file...
Here comes the question:: Should each language maintainer to ensure their po files are consistent with the pot file, or should it be the package maintainer's responsibilities?
Personally I prefer the former, since it will create less file conflict situations and give the language maintainer more control. Opinions anyone?
I remember this discussion goes towards running msgmerge with the original .pot automatically as a pre_commit requirement or somthing similar. Actually, I forgot this issue and now noticed again that:
Arabic has a total of 11407 words English-GB has a total of 11373 words Welsh has a total of 11403 words ...
If all the .pot files on one directory, I can go msgmerge them manually but this would be a rather tedious process to make for each file.
A prerequirement to scripting this process would be to make the po files consistent on their folders. The situation now is that you find some of the po files in a folder called po (like autorun/po/ar.po) whereas others on the same directory as the pot (like up2date/ar.po) and yet other files distributed between both like (system-config-lvm/po/ar.po and system-config-lvm/bg.po). Any reason for this?
Sarah
在2004年09月07日的02:52，Sherif Abdelgawad写道：
I would like to announce that we reached 100% Arabic Translated modules.
We still will go through a tough time unifying and tuning the translation. Yet, the state on it right now is good enough. I would like to thank the fedora team, and the arabic fedora arabic translation team.
Thanks
Sherif
On Mon, Dec 06, 2004 at 12:49:45PM +0300, Munzir Taha wrote:
Arabic has a total of 11407 words English-GB has a total of 11373 words Welsh has a total of 11403 words
en_GB is a little odd in a couple of spots. The en_GB team is mostly RH folk however who have been madly busy with a product approaching release and not en_GB. It's also a little odd as Sarah kindly generated the po files with the en (US) strings as fuzzy not blanks.
consistent on their folders. The situation now is that you find some of the po files in a folder called po (like autorun/po/ar.po) whereas others on the same directory as the pot (like up2date/ar.po) and yet other files distributed between both like (system-config-lvm/po/ar.po and system-config-lvm/bg.po). Any reason for this?
It's a view of bits of the code so the tree depends on the program layout some times. Remember the secret weapon "find"
cd $CVS find . -name "*.pot" -print
Hi,
Firstly I'd like to apologize for not being very responsive lately.
To clarify a few issues raised on the list:
1) directory structure: "translate" is not a "real" module. It's composed of all po/ directories of all packages. Whenever a new package is created and contains po files need to be translated, the po/ directory is added to "translate" module definition. So you can't use "cvs co <package-name>/<filename>" to get the po files. When a new package is added to "translate" module, there are a few ways to check it out from cvs: a) "cvs up -d" in your translate/ directory (may or maynot work) b) "cvs co po-<package-name>" in your translate/ directory c) go one directory about your translate/ directory, then "cvs up translate/", "cvs co translate/" again (you don't need to remove existing files, they will be automatically skipped)
2) Total number of entries As the package maintainer don't create/merge po files when the pot file is created/modified, and we don't have automatic merge feature in the pre-commit check yet, the number of entries for each locale in each package vary a great deal. Please manually compare your po file with pot file (use msgmerge) before starting translation. I'm definitely in favour of this to be done automatically, and would like to get the pre-commit check implemented soonish.
3) ssh key updates Yes it's an administrative intensive process right now when you lose your key or forget your passphrase and have to update the key. Again I'm firmly in favour of having a mechanism in place so everyone can update the key whenever is needed. Like the pre-commit check, I'd like to get this implemented soonish.
4) Automatically assign maintainer Someone suggested to have the maintainer automatically assigned whenever a new module is added. Not all locales have one single maintainer for all packages. Since this is not universal it can't be done automatically for all locales, however, we may be able to compose a list of locales that have one single maintainer and somehow semi-automate the process.
If you have more suggestions or feature requests regarding current process, feel free to post to this list.
Regards, Sarah
Em Segunda, 6 de Dezembro de 2004 23:46, Sarah Wang escreveu:
Hi,
Firstly I'd like to apologize for not being very responsive lately.
Hi Sarah, Could you please take a look at the untranslated messages in comps-po/pt.po? I think there's something wrong with the way comps.pot (same directory) is being generated.
Thanks Pedro Morais
On Tue, 2004-12-07 at 20:05, Pedro Morais wrote:
Em Segunda, 6 de Dezembro de 2004 23:46, Sarah Wang escreveu:
Hi,
Firstly I'd like to apologize for not being very responsive lately.
Hi Sarah, Could you please take a look at the untranslated messages in comps-po/pt.po? I think there's something wrong with the way comps.pot (same directory) is being generated.
Looks like there is something wrong with .pot file. File a bug report against FC4 is the way to go :)
Sarah
Thanks Pedro Morais
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 07 December 2004 1:46 am, Sarah Wang wrote:
Hi,
Firstly I'd like to apologize for not being very responsive lately.
however, we may be able to compose a list of locales that have one single maintainer and somehow semi-automate the process.
For now, Arabic locale has only one single maintainer, Munzir Taha
Thanks
If you have more suggestions or feature requests regarding current process, feel free to post to this list.
Regards, Sarah
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-trans-list
- -- Mohamed Eldesoky Systems Engineer RedHat Certified Engineer TE Data
On Yau al-Thulatha 24 Shawwal 1425 2:46 am, Sarah Wang wrote:
Hi,
Firstly I'd like to apologize for not being very responsive lately.
No problem. You are doing a great job!
- directory structure:
"translate" is not a "real" module. It's composed of all po/ directories of all packages. Whenever a new package is created and contains po files need to be translated, the po/ directory is added to "translate" module definition. So you can't use "cvs co <package-name>/<filename>" to get the po files. When a new package is added to "translate" module, there are a few ways to check it out from cvs: a) "cvs up -d" in your translate/ directory (may or maynot work)
My main problem against this is my slow connection. This will download all the languages for all the packages, isn't it? I would suggest (if not a problem for you and others) a reorganization of the translate module to have all .pot files in one module/folder and each language in it's own module/folder like in KDE for example. This would let each translator download all the files concerning his language easily. We wouldn't also need to guess the place of the po file on the server (in a po folder or not) to download it, am I wrong?
p.s. Remember, volunteering is the best choice! I'd hate to invoke clause 12.A of section 543 of your employment contract; which if you are not familiar with, allows us to appoint volunteeres. *Quoted From doom 3*
On Yaum al-Ithnain 23 Shawwal 1425 11:55 am, Alan Cox wrote:
On Mon, Dec 06, 2004 at 12:49:45PM +0300, Munzir Taha wrote:
Arabic has a total of 11407 words English-GB has a total of 11373 words Welsh has a total of 11403 words
en_GB is a little odd in a couple of spots. The en_GB team is mostly RH folk however who have been madly busy with a product approaching release and not en_GB. It's also a little odd as Sarah kindly generated the po files with the en (US) strings as fuzzy not blanks.
And I just mentioned these as examples so as not to spam the list but French has a total of 11384 Polish has a total of 11387 Dutch has a total of 11404 Bosnian has a total of 11409 ... You just name a number ;) This is just to set an alarm for all maintainers of the other teams to do the merge with the .pot before uploading the file. From now on I am going to take care of this in our translations.
It's a view of bits of the code so the tree depends on the program layout some times. Remember the secret weapon "find"
cd $CVS find . -name "*.pot" -print
Thanks Alan but is there a way that I can find the files on the server so I can only check out the required files for my language?
On Tue, Dec 14, 2004 at 06:04:07PM +0300, Munzir Taha wrote:
cd $CVS find . -name "*.pot" -print
Thanks Alan but is there a way that I can find the files on the server so I can only check out the required files for my language?
No that I can think of (sorry I was taking my broadband for granted again)
-
Alan Cox -
Andrew Martynov -
Gurban M. Tewekgeli -
Josep Puigdemont -
Mohamed Eldesoky -
Munzir Taha -
Pedro Morais -
Sarah Wang -
Sherif Abdelgawad