Databases
StackOverflow2013
Postsdbo
POLocalization with mysql/PHP
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLocalization with mysql/PHP
    primarykey
    data
    text
    <p>I'm currently building a multilingual website using PHP and MySQL and am wondering what the best approach regarding localization is with regards to my data model. Each table contains fields that need to be translated (e.g. <code>name</code>, <code>description</code>....) in several languages.</p> <p>The first idea was to create a field for each language (e.g. <code>name_en</code>, <code>name_de</code>, <code>name_fr</code>) and retrieve the appropriate field from PHP using a variable (e.g. <code>$entry['name_' . LANGUAGE]</code>). While it would work, this approach has in my opinion many drawbacks:<br> -you need as many occurrences of each field as you have languages (bearing in mind you can have en-US, en-CA, en-GB...)<br> -if you add or remove languages you need to modify the database structure accordingly<br> -if you have untranslated fields, they are still created for each entry which doesn't seem very optimized</p> <p>The second idea is to create a translation table that can be used to store the translation of any field of any table in the database:</p> <pre> ---------------- translation ---------------- id INT table_name VARCHAR field_name VARCHAR value VARCHAR language_id VARCHAR </pre> <p>The <code>table_name</code> and <code>field_name</code> will allow identifying which table and which field the translation is about, while <code>language_id</code> will indicate which language that translation if for. The idea is to create models that would replace the value of the translatable fields (e.g. <code>name</code>, <code>description</code>) by their corresponding translation based on the language selected by the user.</p> <p><strong>Can you see drawbacks with this approach? Have you got suggestions to make?</strong></p> <p>Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMax
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLocalization with mysql/PHP
      1. This table or related slice is empty.
      1. VTModeratorReview
    1. COThis question has been asked before. Suggest you search through SO. Look at http://stackoverflow.com/questions/6242478/php-translation-frontend-similar-to-rosetta/6244655#6244655 and here http://stackoverflow.com/questions/6000541/multi-language-php-application-best-practice/6000874#6000874
      singulars
      1. POLocalization with mysql/PHP
      1. USPurplePilot
    2. COAs you can see from the answers given, there was still room for discussion.
      singulars
      1. POLocalization with mysql/PHP
      1. USMax
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload