Re: Transparent i18n?

From: David Pratt <fairwinds(at)eastlink(dot)ca>
To: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
Cc: postgres-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Transparent i18n?
Date: 2005-07-02 20:00:50
Message-ID: FD41775B-EB33-11D9-A19D-000A27B3B070@eastlink.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Many thanks Karsten for some insight into how you are handling this.

Regards,
David

On Saturday, July 2, 2005, at 06:08 AM, Karsten Hilbert wrote:

>> SELECT language_text[1][1] AS language_code,
>> language[1][2] AS text
>> FROM language_text;
>
> They way we do that in GNUmed:
>
> select lookup_val, _(lookup_val) from lookup_table where ...;
>
> If you want to know how see here:
>
>
> http://savannah.gnu.org/cgi-bin/viewcvs/gnumed/gnumed/gnumed/server/
> sql/gmI18N.sql?rev=1.20&content-type=text/vnd.viewcvs-markup
>
> Feel free to ask for clarification.
>
> Karsten
> --
> GPG key ID E4071346 @ wwwkeys.pgp.net
> E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Steffensen 2005-07-02 20:49:23 plpythonu and bytea
Previous Message Michael Fuhr 2005-07-02 18:31:06 Re: Hot to restrict access to subset of data