| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Trevor Talbot <quension(at)gmail(dot)com>, Zeugswetter Andreas ADI SD <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgwin32_open returning EINVAL |
| Date: | 2007-12-20 15:57:15 |
| Message-ID: | 12122.1198166235@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Dec 20, 2007 at 10:11:10AM -0500, Tom Lane wrote:
>> BTW, I concur with Martijn's comment to avoid constructing phrases from
>> spare parts; it creates a translation problem, and in this case you'd
>> only be saving a few bytes anyway.
> Ok. Are you saying whole sentence, or are you saying it's fine to just
> break out the part that's after the colon into "sharing violation" and
> "lock violation"? I assume the second?
Right, that's one reason for using the colon: to help divide the message
into phrases that can be translated separately without too much
grammatical mayhem. _("sharing violation") seems OK to me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trevor Talbot | 2007-12-20 15:57:23 | Re: pgwin32_open returning EINVAL |
| Previous Message | Magnus Hagander | 2007-12-20 15:28:57 | Re: pgwin32_open returning EINVAL |