Symfony and i18n

If you want to use Symfony with i18n: forget about it! it’s not fully supported and you’ll save a lot of time if you don’t try to use it. You say: “eh, but in the documentation….” NO, forget about it. If you want to fully translate a website and have to store text in a database you can’t use it. If you want a proof or example, just try the admin generator with i18n databases and have fun for hours ;)

2 Responses to “Symfony and i18n”

  1. xavier Says:

    You might want to have a look at http://www.narkozateam.com/symfony/archives/7
    :)

  2. WarriorDeluxe Says:

    hey xavier,
    thank you for your link. But as you can imagine, I invested a few days in get it working and believe me, I googled a lot and also found your blog.

    The solution in your link shows the missing fields, but nothing more and nothing less. e.g. if you only have a category and this category has only a name a description and the primary key it doesn’t work without “hacking” symfony. The category doesn’t get saved properly.
    This is only one thing. Now, if you want to translate a category to any desired language you also have to put hour hands on the code.

    It would be ok, if it were only a matter of configuration, but it isn’t. That’s why I can’t understand symfony says: “we fully support i18n in our core”.

    Nik

Leave a Reply