Wow,
Turkish seem to be the first translation to report 100% translation
completion for 8.0 release. Congratulations for great work! And thanks
to Peter for being patient with us all this time.

> > We can't reproduce it with msgfmt -v. How do you get those errors?
>
> The scripts that produce these tables do not use the standard gettext
> tools; they use hand-crafted Perl scripts. In some cases, these catch
> more errors. In all cases that I have analyzed further, this was
> because %m was not identified as a format specifier by msgfmt.

Could you share these scripts with us? Many update submissions
we made were beacause of these %m errors.

Also would it be easier to you Peter if we give you login to our CVS
poject (on sf.net) so that you just run "cvs up" every time
you package a new update and not bother with emails.

Thank you all folks for your efforts.
I will open a bottle of chamgne tonight to celebrate 8.0.

> Peter Eisentraut
> http://developer.postgresql.org/~petere/

Best regards,
Nicolai Tufar

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

On Mon, Jan 17, 2005 at 01:40:40PM +0200, Nicolai Tufar wrote:
> Wow,
> Turkish seem to be the first translation to report 100% translation
> completion for 8.0 release. Congratulations for great work! And thanks
> to Peter for being patient with us all this time.

There were several on 100% until some more messages were marked for
translation. Doing that days before release was not a good idea IMO.


> Also would it be easier to you Peter if we give you login to our CVS
> poject (on sf.net) so that you just run "cvs up" every time
> you package a new update and not bother with emails.

Maybe we should have a pgfoundry project where all translations were
kept, and from which the main CVS could be updated semi-automatically.
Then we wouldn't have Peter checking out and committing all the time.

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Et put se mouve" (Galileo Galilei)

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Alvaro Herrera wrote:
> There were several on 100% until some more messages were marked for
> translation. Doing that days before release was not a good idea IMO.

Yeah, I though so too, but if you think about it, it doesn't harm anyone
except your statistics.

> Maybe we should have a pgfoundry project where all translations were
> kept, and from which the main CVS could be updated
> semi-automatically. Then we wouldn't have Peter checking out and
> committing all the time.

That sounds like a fine idea. My only concern would be the
"not-maintained-here" syndrome, which occurs every time some CVS tree
contains a file that is actually maintained by an external group, thus
blocking the maintainers of the former CVS tree from applying necessary
fixes at times. Nevertheless, I think this is a winner. Let's
consider it when we start the 8.1 cycle.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

> >Alvaro Herrera wrote:
> > Maybe we should have a pgfoundry project where all translations were
> > kept, and from which the main CVS could be updated
> > semi-automatically. Then we wouldn't have Peter checking out and
> > committing all the time.
>
>Peter Eisentraut wrote:
> That sounds like a fine idea. My only concern would be the
> "not-maintained-here" syndrome, which occurs every time some CVS tree
> contains a file that is actually maintained by an external group, thus
> blocking the maintainers of the former CVS tree from applying necessary
> fixes at times. Nevertheless, I think this is a winner. Let's
> consider it when we start the 8.1 cycle.

It is definitely a winner. And I don't think anyonwone from
core group will object since Peter will be the only one who updates
main CVS tree. Just appoint a maintainer or two with cvs commit
priveleges for each language. It will ease your routine workload greatly.

Best regards,
Nicolai

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Peter Eisentraut wrote:
> > Maybe we should have a pgfoundry project where all translations
> > were kept, and from which the main CVS could be updated
> > semi-automatically. Then we wouldn't have Peter checking out and
> > committing all the time.
>
> That sounds like a fine idea. My only concern would be the
> "not-maintained-here" syndrome, which occurs every time some CVS tree
> contains a file that is actually maintained by an external group,
> thus blocking the maintainers of the former CVS tree from applying
> necessary fixes at times. Nevertheless, I think this is a winner.
> Let's consider it when we start the 8.1 cycle.

OK, is anyone opposed to this idea? I would register a pgfoundry
project (name suggestions? "translations"?), give most established
translators commit access, and move the statistics pages there. Also,
some translation groups seem to have their own mailing lists or web
pages, which could optionally also be hosted there.

We could then sync the translations either regularly (e.g., once a week)
or only at release time. Of course we would need to mirror all the
branches there.

Comments?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

On Thu, Jan 20, 2005 at 02:08:20PM +0100, Peter Eisentraut wrote:
> Peter Eisentraut wrote:
> > > Maybe we should have a pgfoundry project where all translations
> > > were kept, and from which the main CVS could be updated
> > > semi-automatically. Then we wouldn't have Peter checking out and
> > > committing all the time.
> >
> > That sounds like a fine idea. My only concern would be the
> > "not-maintained-here" syndrome, which occurs every time some CVS tree
> > contains a file that is actually maintained by an external group,
> > thus blocking the maintainers of the former CVS tree from applying
> > necessary fixes at times. Nevertheless, I think this is a winner.
> > Let's consider it when we start the 8.1 cycle.
>
> OK, is anyone opposed to this idea? I would register a pgfoundry
> project (name suggestions? "translations"?), give most established
> translators commit access, and move the statistics pages there.

Sounds good. Maybe the name is too generic; what about
"server translations", or something like that?

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"¿Cómo puedes confiar en algo que pagas y que no ves,
y no confiar en algo que te dan y te lo muestran?" (Germán Poo)

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

On Thu, 20 Jan 2005 14:08:20 +0100, Peter Eisentraut <peter_e@gmx.net> wrote:
> Peter Eisentraut wrote:
> > > Maybe we should have a pgfoundry project where all translations
> > > were kept, and from which the main CVS could be updated
> > > semi-automatically. Then we wouldn't have Peter checking out and
> > > committing all the time.
> >
> > That sounds like a fine idea. My only concern would be the
> > "not-maintained-here" syndrome, which occurs every time some CVS tree
> > contains a file that is actually maintained by an external group,
> > thus blocking the maintainers of the former CVS tree from applying
> > necessary fixes at times. Nevertheless, I think this is a winner.
> > Let's consider it when we start the 8.1 cycle.
>
> OK, is anyone opposed to this idea? I would register a pgfoundry
> project (name suggestions? "translations"?), give most established
> translators commit access, and move the statistics pages there. Also,
> some translation groups seem to have their own mailing lists or web
> pages, which could optionally also be hosted there.
>
> We could then sync the translations either regularly (e.g., once a week)
> or only at release time. Of course we would need to mirror all the
> branches there.
>
> Comments?

Perfectly fine. Please go ahead.

> --
> Peter Eisentraut

Nicolai Tufar
Turkish Language Translation Team.

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings