Translation

Overriding the translation domain

The translation domain can be overridden at either the form group or individual field level.

If a translation domain is set at the group level it will cascade down to all fields within the group.

Overriding the translation domain is of particular use when using Customize admin, where the extension and the translations would be defined in one bundle, but implemented in many different Admin instances.

Setting the translation domain on an individual field:

1
2
3
4
5
6
7
8
9

use Symfony\Component\Form\Extension\Core\Type\CheckboxType;

$form
    ->with('form.my_group')
        ->add('publishable', CheckboxType::class, [], [
            'translation_domain' => 'MyTranslationDomain',
        ])
    ->end()
;

The following example sets the default translation domain on a form group and over-rides that setting for one of the fields:

1
2
3
4
5
6
7
8
9
10
11

use Symfony\Component\Form\Extension\Core\Type\CheckboxType;
use Symfony\Component\Form\Extension\Core\Type\DateType;

$form
    ->with('form.my_group', ['translation_domain' => 'MyDomain'])
        ->add('publishable', CheckboxType::class, [], [
            'translation_domain' => 'AnotherDomain',
        ])
        ->add('start_date', DateType::class, [], [])
    ->end()
;

Translation can also be disabled on a specific field by setting translation_domain to false.

Setting the label name

By default, the label is set to a sanitized version of the field name. A custom label can be defined as the third argument of the add method:

1
2
3
4
5
6
7
8
9
10
11
12
13
14

// src/Admin/PageAdmin.php

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $form): void
    {
        $form
            ->add('isValid', null, [
                'required' => false,
                'label' => 'label.is_valid',
            ])
        ;
    }
}

Label strategies

There is another option for rapid prototyping or to avoid spending too much time adding the label key to all option fields: Label Strategies. By default labels are generated by using the following rule:

isValid => Is Valid

The AdminBundle comes with different key label generation strategies:

• sonata.admin.label.strategy.native: DEFAULT - Makes the string human readable

  isValid => Is Valid

• sonata.admin.label.strategy.form_component: The default behavior from the Form Component

  isValid => Isvalid

• sonata.admin.label.strategy.underscore: Changes the name into a token suitable for translation by prepending "form.label" to an underscored version of the field name isValid => form.label_is_valid

• sonata.admin.label.strategy.noop: does not alter the string

  isValid => isValid

sonata.admin.label.strategy.underscore will be better for i18n applications and sonata.admin.label.strategy.native will be better for native (single) language applications based on the field name. It is reasonable to start with the native strategy and then, when the application needs to be translated using generic keys, the configuration can be switched to underscore.

The strategy can be quickly configured when the Admin class is registered in the Container:

1
2
3
4
5
6
7
8
9
10
11
12

<!-- config/services.xml -->

<service id="app.admin.project" class="App\Admin\ProjectAdmin">
    <tag
        name="sonata.admin"
        model_class="App\Entity\Project"
        manager_type="orm"
        group="Project"
        label="Project"
        label_translator_strategy="sonata.admin.label.strategy.native"
        />
</service>