Re: SSI error messages
От | Kevin Grittner |
---|---|
Тема | Re: SSI error messages |
Дата | |
Msg-id | 4E207B8F020000250003F3D9@gw.wicourts.gov обсуждение исходный текст |
Ответ на | Re: SSI error messages ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: SSI error messages
|
Список | pgsql-hackers |
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote: > Alvaro Herrera <alvherre@commandprompt.com> wrote: >> Excerpts from Tom Lane's message: >> >>> I think that Peter's real concern is whether these are worth >>> translating, and I share that doubt. Perhaps we should invent >>> an errdetail_internal, parallel to errmsg_internal, that works >>> like errdetail but doesn't treat the message as a candidate for >>> translation? >> >> Yeah. The other point is that translated versions of those >> phrases are likely to introduce randomly diverging terms, which >> is not going to help with debugging. As long as the technology >> is new enough that a user is going to need help from -hackers (or >> at least someone who read and grokked README.SSI) to debug a >> problem, there's no benefit to translating those errdetails. > > OK, since that seems to be the consensus, I put a patch together. > Testing it now. Will post once I've confirmed it doesn't break > anything. OK, after getting distracted by test failures caused by an unrelated commit, I've confirmed that this passes my usual tests. I don't know anything about the tools used for extracting the text for the translators, so if that needs any corresponding adjustment, someone will need to point me in the right direction or cover that part separately. The leading whitespace changes in predicate.c are from pgindent. -Kevin
Вложения
В списке pgsql-hackers по дате отправления: