title: a2lix TranslationFormBundle AND Gedmo Doctrine Extension Translatable with just one Translation table
body: <p>I am trying to use the a2lix TranslationFormBundle  ( <a href="https://github.com/a2lix/TranslationFormBundle" rel="nofollow">https://github.com/a2lix/TranslationFormBundle</a> ) with a Symfony2 project.
  I have been looking at docs and specifically at this demo: <a href="https://github.com/a2lix/Demo/tree/master/src/A2lix/DemoTranslationBundle" rel="nofollow">https://github.com/a2lix/Demo/tree/master/src/A2lix/DemoTranslationBundle</a></p>
  
  <p>I noticed all examples in both the doc and the demo use specific translation tables (end entity) for each translatable entity, as set in the class annotation with</p>
  
  <pre><code>@Gedmo\TranslationEntity(class="A2lix\DemoTranslationBundle\Entity\ProductGedmoTranslation")
  </code></pre>
  
  <p>My idea was to stay with just one table, like the ext_translations table that the Gedmo Doctrine Extension Translatable creates and manages.</p>
  
  <p>Is this possible or does the TranslationFormBundle absolutely need separate tables?
  Does anyone have a working example?</p>
  
  <p>TIA</p>