Re: Internationalization
От | Pedro Doria Meunier |
---|---|
Тема | Re: Internationalization |
Дата | |
Msg-id | 49DFF6C9.9090906@netmadeira.com обсуждение исходный текст |
Ответ на | Re: Internationalization (Justin <justin@emproshunts.com>) |
Ответы |
Re: Internationalization
|
Список | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Justin, First of all thank you for your input. :) Actually what I have is a fully internationalized site by means of getttext. *Some* of the content comes from the PGSQL database where 2 tables relation with others (namely for sensor data description). These tables have the simplest arrangement: id, description :] I wondered if there was some sort of pgsql extension providing a text replacement mechanism of sorts in order to achieve something like gettext ... I guess I'll have to resort to what I've previously thought of ... Regards, Pedro Doria Meunier. Justin wrote: > Pedro Doria Meunier wrote: >> Hi all, >> >> I'm wondering how to internationalize contents of a table, short >> of having a column for each language string ... Anyone with some >> experience to share? :) >> >> Regards, Pedro Doria Meunier >> > How about parent child table layout. The child table has one > record for translation for each document. something like this > > Create table ParentDoc ( docid serial, description text ) > > Create table ChildDoc ( docid integer, doc_text text, > short_description text, language text ) > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFJ3/bA2FH5GXCfxAsRAlZ0AKCnP9LDOJlOrDSF+Ci4G3CpdX8AlgCdFJqQ 5CrOIuWvgVBXCmyZwhjR8r8= =DmmH -----END PGP SIGNATURE-----
В списке pgsql-general по дате отправления: