Re: pgwin32_open returning EINVAL

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgwin32_open returning EINVAL
Дата
Msg-id 12122.1198166235@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgwin32_open returning EINVAL  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-hackers
Magnus Hagander <magnus@hagander.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Trevor Talbot"
Дата:
Сообщение: Re: pgwin32_open returning EINVAL
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: pgwin32_open returning EINVAL