If you’ve ever used FOS user bundle, they handle all the translation for you for the form’s field labels. Whenever a translation is not there, you see the field’s id instead of seeing any label based on the field’s name like this is usually the case.
This seemed pretty cool to me and I couldn’t help but keep thinking “I want that too”. The reason is that my translations are based on “keys” instead of the actual text. So if my label reads “Contact person’s email”, I’d have to have a key with this name. But when I change this label in English to “Contact’s email” then I would have to change all the keys in the translation files. Which … I don’t want to!
So after a little experimentation, here’s what you can do to use this simple key based ways of translating form labels:
The first very simple solution is to manually set the label for any form field to be that field’s id. It’s super simple and fast to do:
So for each form label you manually specify that the label is the field’s id. Then in your translation file you add the corresponding keys and translations:
And … you’re good to go!
But if you’re as lazy as you should, you do not want to manually do this all the time. So (because you’re lazy), you spend 2 hours wondering “How the hell do they do this in FOSUserBundle so that it’s automatic???” Here’s how:
Form and form fragments can be themed as explained in symfony’s documentation. So we’re gonna use almost the same trick as in FOSUserBundle to translate our own forms.
Field label fragment
First we define a field label fragment. This is a view that you can put for example in “MyBundle:Form:label.html.twig” and that will look like this:
Then you either add this form theme in each page where you have a form or globally in your config file:
And then again you’ll be all set to add the field’s ids in your messages.<locale>.yml with their translations.
Pushing it further
When you use translations and set them in yml files, a nice feature is that you can “group” them. The translation for “mybundle.myform.myfield” can be made in any of the 2 following ways:
But right now we use the field’s id which is usually in the format of “mybundle_myformtype_mysubform_myfield”. We’re almost there. A small change to the form theme we made earlier and all will be good:
And there you go, you can translate your forms and use the nested yml format.