Re: plpgsql is not translate-aware
| От | Tom Lane |
|---|---|
| Тема | Re: plpgsql is not translate-aware |
| Дата | |
| Msg-id | 26378.1220632700@sss.pgh.pa.us обсуждение |
| Ответ на | Re: plpgsql is not translate-aware (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: plpgsql is not translate-aware
Re: plpgsql is not translate-aware |
| Список | pgsql-hackers |
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Actually this is wrong -- since the library is going to run with
> "postgres" text domain, we need to add the files to the backend's
> nls.mk:
Can't we give it its own text domain? It seems fundamentally wrong
for a plug-in language to require core support for its messages.
(Now that I think about it, that may have been the reason we don't have
localization for it already.) I suppose this must be possible,
since e.g. glibc manages to have its own messages separate from
whatever app it's linked with.
regards, tom lane
В списке pgsql-hackers по дате отправления: