Well, we don't have forever to wait on this, and I don't plan to require
patches to be held until one specific person can review them. Fabien,
which version is your best? I will put it in the patch queue.
---
Fabien
hello,
we are starting a new language translation in postgresql.
I send the pg_controldata message translation in Farsi language.
I sended it to the Peter Eisentraut with the name fa_IR.po. He said that
Is there any use of fa outside of IR? Else I would just call the
translation files fa.po.
How does your Win32 system rename prototype differ from what is in
port.h?
extern int pgrename(const char *from, const char *to);
extern int pgunlink(const char *path);
Good question on wether we need to keep this working but it would be
nice to keep it I guess for client-only
[EMAIL PROTECTED] wrote:
hello,
we are starting a new language translation in postgresql.
I send the pg_controldata message translation in Farsi language.
I sended it to the Peter Eisentraut with the name fa_IR.po. He said that
Is there any use of fa outside of IR? Else I would just call the
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Where are we on this?
I think we're waiting on Peter to review it.
I have no technical issue with the patch, except that as I have
previously mentioned, I don't particularly care for what it does.
--
Peter Eisentraut
Bruce Momjian wrote:
How does your Win32 system rename prototype differ from what is in
port.h?
What is the need of *any* special file handling functions for client tools?
Regards,
Andreas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
Andreas Pflug [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
I see that there is a farsi translation in pgadmin and you named it fa_IR.
This isn't comparable. In pgadmin, we're bound to the canonical names
defined in wxWidgets, which is fa_IR (and there's no other Farsi
version). Thus
The following patch fixes pltcl compiles on win32. The code change in
pltcl.c is from this post:
http://groups.google.com/groups?q=tcl_createslave+errorhl=enlr=ie=UTF
-8c2coff=1safe=offselm=20040107132138.57308.qmail%40web60304.mail.yah
oo.comrnum=3
Can't say I fully understand why, but it does
Tom Lane wrote:
Nonetheless, it would also be good to have some consistency between
the core PG server and related projects. I tend to agree that we
should honor pgadmin's precedent here; it's not a strong argument but
the argument for fa over fa_IR seems even weaker.
fa_IR would uselessly
Andreas Pflug wrote:
Bruce Momjian wrote:
How does your Win32 system rename prototype differ from what is in
port.h?
What is the need of *any* special file handling functions for client tools?
We could avoid it but it does give us Unix semantics so it seemed good
to keep it if we could.
Bruce Momjian wrote:
Andreas Pflug wrote:
Bruce Momjian wrote:
How does your Win32 system rename prototype differ from what is in
port.h?
What is the need of *any* special file handling functions for client tools?
We could avoid it but it does give us Unix semantics so it seemed good
to keep it
Andreas Pflug wrote:
Bruce Momjian wrote:
Andreas Pflug wrote:
Bruce Momjian wrote:
How does your Win32 system rename prototype differ from what is in
port.h?
What is the need of *any* special file handling functions for client tools?
We could avoid it but it does give us
Tom Lane wrote:
It seemed a tad excessive to me, at least for routine regression
testing. What do you think of making it a separate test script and
adding it to make bigcheck, as we did once with the numeric_big tests?
I'm not sure I see the point: I would guess that the rate at which we're
13 matches
Mail list logo
