Re: Syntax got translated
От | Alvaro Herrera |
---|---|
Тема | Re: Syntax got translated |
Дата | |
Msg-id | 1329757905-sup-8549@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Syntax got translated (Susanne Ebrecht <susanne@2ndquadrant.com>) |
Ответы |
Re: Syntax got translated
|
Список | pgsql-bugs |
Excerpts from Susanne Ebrecht's message of s=C3=A1b feb 18 18:11:54 -0300 2= 012: > Output in German: > i | integer | not null Vorgabewert nextval('t_i_seq'::regclass) >=20 > Output in French: > i | integer | non NULL Par d=C3=A9faut, nextval('t_i_seq'::regclass) >=20 > Output in Spanish: > i | integer | not null valor por omisi=C3=B3n nextval('t_i_seq'::re= gclass) >=20 > I think that the constraint keyword "DEFAULT" should not be translated he= re. > In my eyes in all cases it should output: >=20 > i | integer | not null default nextval('t_i_seq'::regclass) I'm not clear on this. I translated it because it seemed sensible, but I remember stopping for a minute to consider it. Maybe if more people thinks it should not be translated, we could remove the translatability marker from DEFAULT and other stuff like NOT NULL. I'mnot sure however. Just removing the translations from the existing catalogs is not enough, because future versions will just put them back. --=20 =C3=81lvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-bugs по дате отправления: