My concern was in storing the user entered data. Like product descriptions etc.
The rest of your post is certainly valuable tho. Jeff. On 9/8/05, Johan Kuuse <[EMAIL PROTECTED]> wrote: > Just my two cents: > > Have you read the following article? > http://search.cpan.org/~sburke/Locale-Maketext-1.09/lib/Locale/Maketext/TPJ13.pod > It treats various problems (such as singular/dual/plural forms in different > languages, for example), and some good reasons to use Locale::Maketext and/or > related modules. > Hint: search for "locale maketext" on cpan.org, and you will have an idea what > I try to explain. > > Also recommended: > http://www.autrijus.org/webl10n/ > > I'm using CGI::App together with a couple of modules initially created by > Markus Spring, a patched HTML::Template together with a HTML::Translator, a > module which parses HTML text and then translates it using Locale::Maketext. > All HTML templates are in English, and translated to whatever language before > displayed. The advantage with this approach is that you can create an app > without first considering making it multilingual, but instead convert a > "monolingual" app into multilingual without modifying your templates. > > In the case of your product gallery tables, I think you could use the Tie::DBI > module to tie the lexicon hash to your SQL database. I'm using plain text > files for each lexicon, so I havent's tried Tie::DBI myself. > > Regards, > Johan > > > On Thursday 08 September 2005 07:22, Jeff MacDonald wrote: > > Hiya, > > > > Not really CGI::App specific, but you guys are a sounding board for > > CGI related stuff that I trust. You ask on groups you don't kwno and > > you just get a bunch of really dumb answers :) > > > > I'm working on an ecommerce site for a company in Quebec. Site is in > > english now and if they don't switch in a month, the QC gov't sues > > them. Awesome, go Quebec ! [and I live here] > > > > So for the product gallery , this is the schema I was thinking of, I > > want it to be flexible for when Quebec makes Mandarin, Italian and > > Martian manditory languages. > > > > CREATE TABLE products ( > > id SERIAL PRIMARY KEY, > > price numeric(10,2), > > instock int default 0, > > taxable boolean > > ); > > > > CREATE TABLE actual_products ( > > productid int REFERENCES products(id), > > lang char(2) REFERENCES languages(lang), > > title text, > > description text, > > specialinstructions text > > ); > > > > CREATE unique index actual_products_idx ON actual_products(productid,lang); > > > > I'm thinking about doing this sort of layout for my table of > > provinces, countries and any other select lists i draw upon. > > > > Alternativly I could just put them all in the same table, but that > > seems to stray from the relational guidelines of not reproducing the > > same data twice [ie price, taxable etc] > > > > Jeff. > > -- > Johan Kuuse > [EMAIL PROTECTED] > Thu Sep 8 07:34:10 2005 > > -- Jeff MacDonald http://www.halifaxbudolife.ca http://www.nintai.ca --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
