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