Skip site navigation (1) Skip section navigation (2)

Re: Syntax got translated

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Susanne Ebrecht <susanne(at)2ndquadrant(dot)com>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Syntax got translated
Date: 2012-02-20 17:15:34
Message-ID: 1329757905-sup-8549@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Excerpts from Susanne Ebrecht's message of sáb feb 18 18:11:54 -0300 2012:

> Output in German:
> i      | integer | not null Vorgabewert nextval('t_i_seq'::regclass)
> 
> Output in French:
> i       | integer | non NULL Par défaut, nextval('t_i_seq'::regclass)
> 
> Output in Spanish:
> i       | integer | not null valor por omisión nextval('t_i_seq'::regclass)
> 
> I think that the constraint keyword "DEFAULT" should not be translated here.
> In my eyes in all cases it should output:
> 
> 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.

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-bugs by date

Next:From: Guillaume LelargeDate: 2012-02-20 20:19:29
Subject: Re: BUG #6478: Foreign tables not displayed
Previous:From: romanDate: 2012-02-20 16:32:27
Subject: BUG #6478: Foreign tables not displayed

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group