(no subject)
by Rupesh Kumar Sunkara
Hi,
I have enrolled to translate into TELUGU language. When I tried to check out the 'po' files from the server with the following CVSROOT
:ext:vishrup@i18n.redhat.com:/usr/local/CVS
I am getting error message as "Unable to open connection. Host does not exist".
What should I do now to get the files for translation?
Regards,
Rupesh.
---------------------------------
Yahoo! for Good
Click here to donate to the Hurricane Katrina relief effort.
17 years, 12 months
Re: Re: Java application to help translation
by Sharuzzaman Ahmat Raslan
I would like to highlight Pootle, a web based translation system developed by the South African Translation Team.
Pootle can be viewed at http://pootle.wordforge.org/ and the development site is at http://translate.sourceforge.net/
-----Original Message-----
From: Manuel Eduardo Ospina Sarmiento <mospina(a)redhat.com>
To: Fedora Translation Project List <fedora-trans-list(a)redhat.com>
Date: Tue, 20 Sep 2005 11:09:31 +1000
Subject: Re: Java application to help translation
Hi,
Thanks Sherif for bringing this project in.
Korean community members are also working on a similar project:
* http://potron.sourceforge.net/
* http://codethread.net/potron/
It would be interesting to put all these initiatives together.
I believe it would be also important to develop support for xliff as
this standard is getting stronger in the localization industry.
Cheers,
Manuel
El vie, 09-09-2005 a las 07:11 -0400, Sherif Abdelgawad escribió:
> I thought of bringing this to a broader audience. I suggested to my team
> (Arabic translation team) while ago to have some sort of web interface to
> help non-technical ppl to contribute translation.
>
> The idea was:
>
> - Application that parse CVS po files
> - Store the strings, headers, and translation into DB
> - 3 interfaces:
> o Contributor - where an authenticated user can view untranslated and
> fuzzy strings
> and contribute translation from his browser.
> o Maintainer - Approve translation and merge new translation, QA, ..etc.
> o Admin - Populate DB with the PO files, generate PO files and
> check them
> back to CVS where it can be later sync'd to Fedora
> CVS.
>
> Mohamed Ghoniem and Maha Helwa from the Arabic team volunteered to
> contribute
> a Java code. The work still going and we only got a parser for the PO files
> but we
> wish to have full featured java application in the near future.
>
> To check the current first initial code:
>
> http://www.arabic-fedora.org/po2db.tar.gz
>
> This code takes care of all PO components. It handles strings correctly
> in UTF-8 charset, it works fine with Arabic, and it should handle anyother
> charset and/or all languages supported by java.
>
> We thought to bring this to a broader audience and other teams as we think
> this can be of a great help to all the translation effort. Also there maybe
> other ideas that we can share.
>
> Thanks
>
> Sherif
>
> --
> Fedora-trans-list mailing list
> Fedora-trans-list(a)redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-trans-list
--
Fedora-trans-list mailing list
Fedora-trans-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-trans-list
------------------------
Sharuzzaman Ahmat Raslan
18 years
Java application to help translation
by Sherif Abdelgawad
I thought of bringing this to a broader audience. I suggested to my team
(Arabic translation team) while ago to have some sort of web interface to
help non-technical ppl to contribute translation.
The idea was:
- Application that parse CVS po files
- Store the strings, headers, and translation into DB
- 3 interfaces:
o Contributor - where an authenticated user can view untranslated and
fuzzy strings
and contribute translation from his browser.
o Maintainer - Approve translation and merge new translation, QA, ..etc.
o Admin - Populate DB with the PO files, generate PO files and
check them
back to CVS where it can be later sync'd to Fedora
CVS.
Mohamed Ghoniem and Maha Helwa from the Arabic team volunteered to
contribute
a Java code. The work still going and we only got a parser for the PO files
but we
wish to have full featured java application in the near future.
To check the current first initial code:
http://www.arabic-fedora.org/po2db.tar.gz
This code takes care of all PO components. It handles strings correctly
in UTF-8 charset, it works fine with Arabic, and it should handle anyother
charset and/or all languages supported by java.
We thought to bring this to a broader audience and other teams as we think
this can be of a great help to all the translation effort. Also there maybe
other ideas that we can share.
Thanks
Sherif
18 years
Re: organizing CVS for trans
by Noriko Mizumoto
Hi Karsten-san and docs team
Thanks for your decision of having separate xml files per language!
As quality wise, I think it would be better to have proofreader
(maintainer) for each translation same way with software translation.
To avoid confliction committing same document file in same time by more
than one translators (or maintainer), access right should be restricted
to the maintainer, I think.
Any thoughts? translators?
Btw, I discussed with Warren about this.
Ideally we'd better to have trans cvs repository apart from docs cvs.
There are several challenges to make this happen at the moment.
Cheers
Noriko
Karsten Wade wrote:
> On Thu, 2005-08-25 at 11:03 +1000, Noriko Mizumoto wrote:
>
>>Hi docs team
>>
>>I am coming from fedora-trans-list, Japanese translator, Noriko
>>Mizumoto. I am so excited hearing the news that docs team is preparing
>>to host translation. I would like to say thank you, and am looking for
>>something that I can help. Please let me know if it is recommended to
>>make self introduction as translator, I am most happy to do so.
>
>
> That would be great to do. If you have done it already, you could just
> send us a link to that self-intro.
>
>
>>To me it would be nice if translators can work on po files similar to
>>fedora software modules we are currently working, since this must be one
>>of safe way to minimize translator from messing up tags. However this
>>might be required more time of your side, I guess.
>>
>>When the format will go with inline, the file can only be translated by
>>one translator at the time and other translators have to wait for
>>her/his turn, if my understanding is correct.
>>Then it seems that this is not practical for release notes which has
>>strictly limited time-frame for both docs and trans.
>
>
> Yes, this is how the RHEL documentation is translated, with separate XML
> files per language.
>
> Despite our geekish preference for translations all in one file, it is
> clear we need to make them separate files.
>
> foo-en.xml
> foo-it.xml
> foo-ru.xml
> foo-jp.xml
> ...
>
> Should we want to combine then in the future, I bet there is some way to
> do it in Perl.[1]
>
> - Karsten
> [1] Isn't this true of everything?
>
18 years
Java application to help translation
by Sherif AbdElGawad
I thought of bringing this to a broader audience. I suggested to my team
(Arabic translation team) while ago to have some sort of web interface to
help non-technical ppl to contribute translation.
The idea was:
- Application that parse CVS po files
- Store the strings, headers, and translation into DB
- 3 interfaces:
o Contributor - where an authenticated user can view untranslated and
fuzzy strings
and contribute translation from his browser.
o Maintainer - Approve translation and merge new translation, QA, ..etc.
o Admin - Populate DB with the PO files, generate PO files and
check them
back to CVS where it can be later sync'd to Fedora
CVS.
Mohamed Ghoniem and Maha Helwa from the Arabic team volunteered to
contribute
a Java code. The work still going and we only got a parser for the PO files
but we
wish to have full featured java application in the near future.
To check the current first initial code:
http://www.arabic-fedora.org/po2db.tar.gz
This code takes care of all PO components. It handles strings correctly
in UTF-8 charset, it works fine with Arabic, and it should handle anyother
charset and/or all languages supported by java.
We thought to bring this to a broader audience and other teams as we think
this can be of a great help to all the translation effort. Also there maybe
other ideas that we can share.
Thanks
Sherif
18 years
quick update about translation for FC5
by Karsten Wade
Sorry that we went silent on this for a little while.
The translation team, the documentation team, and the infrastructure/CVS
admins are discussing how to best integrate translation with
cvs.fedora.redhat.com.
The goals are:
* Same or similar locking tools, so translators can lock something for
translation
* Usage of CVS without making translators learn a whole new set of tools
* Translation process that is the same translators are used to, using PO
files, etc.
We'll let you know more about how this is shaping up.
thx - Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
18 years
