title: How to store dynamic localized strings
body: <p>I'm using laravel framework and mysql to build a site which needs to be translated into, at the moment 3 but it may increase, different languages. Using Laravel it is relatively easy to create different language files for different languages and call them in the html for relatively static strings. However, for data coming out of a database, what is the best practice for localizing such data? It seems that storing the localized versions of the strings would work well in the sense that they can all be added at the same time as the data is created; however, it seems it would be horrible in the sense of adding a new language. Using language files for the data seems better for adding new languages, but would be annoying to keep up with when new rows are added to the database.
  I've come up with a solution to translate some of the data in a relatively static selectbox (it uses a static array of ids/names of some of the most common data) so that users may be able to utilize that part of the site pretty well no matter the language, but the data as it shows up on the rest of the site is naturally unaffected by that change.</p>
  
  <p>What is the best practice for handling such an issue? The few solutions I can come up with all seem rather flawed.</p>
  
  <p>Note: the new rows are added on a management site which is separate from the main site, but shares the same data in the database. The people adding the new rows would not have direct access to any language files.</p>