Interface language. Loading from database

As an Admin I'd like to have my language settings kept in my profile so that when I visit Poulpe I see the interface in the tongue from my profile and I don't need to switch my preferred language again.
Since Larks team already have implemented storing language information to the database, we need to use their mechanisms to work with our language as well. A task is to contact the Larks team and figure out weather it's easy to move the entities to the JTalks Common project. You'll need to create a task in that project with detailed description of what to be done (what class should be moved to common codebase).
But probably the first step should be duplicating JCommune class with this information in Poulpe and mapping it to the same table. And after this class is moved to common, it should be removed from Poulpe.
The language and locale info should be kept in common tables, not in JCommune or Poulpe specific, so if this is not true in JCommune right now, a task should be raised in JCommune project as well.