You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Emre Sokullu <so...@ultratv.net> on 2005/02/26 23:45:06 UTC
Turkish Translation
Hi all,
Last month, I've sent our translations to this mailing list.. However, I
still can't see "tr" in "Available Languages:" menu.. Did I miss
something, is there sth to be done for me? Or is this a usual delay?
Thank you,
Emre SOKULLU
turkix.org
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Turkish Translation
Posted by emre sokullu <so...@ultratv.net>.
OK, finally I got it :) .. We'll switch to the new version and I'll
resend you the new translations.. This may take some time.. Thanx for
the explanation..
André Malo wrote:
>* Emre Sokullu wrote:
>
>
>
>>Bringing the files up to date? But this would be a totally new work from
>>scratch, wouldn't it?
>>
>>
>
>No. That's the day by day work of a translator ;-) If the English version
>changes, you need to compare the old version with the new version and
>adjust the translation.
>
>
>
>>I'd rather prefer switching to svn for our
>>upcoming translations, and publish the existing ones as they are, if
>>possible..
>>
>>
>
>As said above, translating once is only the half way. When I'm committing
>the files as they are, they are marked outdated immediately - If this is ok
>for you; well, I have no problem with it (other opinions would be nice
>here).
>
>nd
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Turkish Translation
Posted by André Malo <nd...@perlig.de>.
* Emre Sokullu wrote:
> Bringing the files up to date? But this would be a totally new work from
> scratch, wouldn't it?
No. That's the day by day work of a translator ;-) If the English version
changes, you need to compare the old version with the new version and
adjust the translation.
> I'd rather prefer switching to svn for our
> upcoming translations, and publish the existing ones as they are, if
> possible..
As said above, translating once is only the half way. When I'm committing
the files as they are, they are marked outdated immediately - If this is ok
for you; well, I have no problem with it (other opinions would be nice
here).
nd
--
package Hacker::Perl::Another::Just;print
qq~@{[reverse split/::/ =>__PACKAGE__]}~;
# André Malo # http://www.perlig.de #
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Turkish Translation
Posted by Emre Sokullu <so...@ultratv.net>.
On Sun, 2005-02-27 at 13:26, André Malo wrote:
> * Emre Sokullu wrote:
>
> > Last month, I've sent our translations to this mailing list.. However, I
> > still can't see "tr" in "Available Languages:" menu.. Did I miss
> > something, is there sth to be done for me? Or is this a usual delay?
>
> Hmm, perhaps we've misunderstood each other ;)
> I thought, that you were going to bring the files up to date and switch to
> svn before committing them.
Bringing the files up to date? But this would be a totally new work from
scratch, wouldn't it? I'd rather prefer switching to svn for our
upcoming translations, and publish the existing ones as they are, if
possible..
Emre Sokullu
turkix.org
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Turkish Translation
Posted by André Malo <nd...@perlig.de>.
* Emre Sokullu wrote:
> Last month, I've sent our translations to this mailing list.. However, I
> still can't see "tr" in "Available Languages:" menu.. Did I miss
> something, is there sth to be done for me? Or is this a usual delay?
Hmm, perhaps we've misunderstood each other ;)
I thought, that you were going to bring the files up to date and switch to
svn before committing them.
nd
--
Flhacs wird im Usenet grundsätzlich alsfhc geschrieben. Schreibt man
lafhsc nicht slfach, so ist das schlichtweg hclafs. Hingegen darf man
rihctig ruhig rhitcgi schreiben, weil eine shcalfe Schreibweise bei
irhictg nicht als shflac angesehen wird. -- Hajo Pflüger in dnq
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org