On 10/27/05, Ilya Konstantinov <[EMAIL PROTECTED]> wrote:
true, but there are translators who use opensource you know...
Yes, but that is not relevent for the project I think.
So? It's not like all the string in the program change between versions,
if you translate everything once it would give a good base for future work.
It would also give reference for people.
Yes, I agree but not because of your reason I think that if we could get someone hired to help out with formulating
guidelines and making opensource gloassary it would be much more help than just translating,
I would go futher than that and say that with good guidelines and glossary we could do a lot of the translation
by automatic scripting and then go over it to fix mistakes. It could save a lot of time.
I'm trying to push glossary/guidelines work for a month now in [EMAIL PROTECTED]
Pro help would be a major help IMHO.
Ely
On ה', 2005-10-27 at 19:39 +0200, Gábor Szabó wrote:
> On 10/27/05, Uri Bruck <[EMAIL PROTECTED]> wrote:
> > The relevant number is not the number of messages but the word count of
> > the target text. When translating English -> Hebrew texts tend to shrink
> > by about 20%.
>
> Taking a few random files with some random sampling,
> that is to say using some meaningless numbers
> I would say there are 3-7 words in every message in English.
>
> 3*40.000*0.80*76/250 = 29.184 + VAT
> 7*40.000*0.80*76/250 = 68.096 + VAT
>
> OK, let's say under 100.000 NIS
>
> Can anyone point to specific applications that might be interesting
> to be translated/localized in the ISOC project?
I fear that localization work requires more community involvement than
an off-the-street paid translator has.
1) A translator should have actively used the system to know the context
of the strings.
true, but there are translators who use opensource you know...
2) A translator is an integrated part of a release cycle: e.g. often,
during a release cycle, there's a so-called "string freeze" so
translators could catch up and be on time for the release.
Yes, but that is not relevent for the project I think.
3) Many of our favorite FOSS projects have much shorter release cycles
than they have on the market.
So? It's not like all the string in the program change between versions,
if you translate everything once it would give a good base for future work.
It would also give reference for people.
That's why a one-time paid translation sounds to me a bit inappropriate.
Yes, I agree but not because of your reason I think that if we could get someone hired to help out with formulating
guidelines and making opensource gloassary it would be much more help than just translating,
I would go futher than that and say that with good guidelines and glossary we could do a lot of the translation
by automatic scripting and then go over it to fix mistakes. It could save a lot of time.
I'm trying to push glossary/guidelines work for a month now in [EMAIL PROTECTED]
Pro help would be a major help IMHO.
Ely
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
