Hi Monks!

I'm probably facing a simple problem that many of you have already solved long time ago: how to store and read many translations of a software.

Our application is a Web 2.0 software running under Linux/Apache/mod_perl/Postgres/BerkeleyDB for cache/etc. This application has about 1000 different expressions (from 10 to 200 character each). And we are plannig to prepare it to have multiple languare support (each user that logs in can choose it's prefered lang, just like phpPgAdmin).

So my question is: which is the best way to store all this data.

My fisrt choice was to have it on simple PM files, on hashref structures, wich is the fastest way to access the data, but having multiple languages simultaniously on mod_perl would increase memory consumption, having a hash of thousands of expressions in memory when each CGI may use only a few of them.

My second choice was to have it chached on a BerkeleyDB file (which I already use for other caches), tied to a hash. This would solve the Apache/mod_perl memory problem, but is this fast enougth?

So, before I begin working, what are you monks doing to solve this? Any of my ideas or a different one?

Thanks!

Diego de Lima

2006-02-09 Retitled by planetscape, as per Monastery guidelines
Original title: 'Multi-languare web app'

In reply to Multi-language web app by diego_de_lima

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.