internationalization.md

Internationalization

You can configure whether you want this package to attempt to translate texts or not, for example if your project only needs to implement one language and you prefer to simply write texts wherever you need them instead of using the Translator component, please deactivate translations in the configuration:

//config/html.php
return [
  //...
  'translate_texts' => false
  //...
];

But if your project needs to implement more than one language or you want to organize all the texts in one place instead of hardcoding them in the controllers, views, etc. set 'translate_texts' to true.

Note: The Field Builder will always attempt to translate texts.

Translating labels (field builder)

If you want to have a specific label in a field, you can do so by passing it as part of the attribute array:

{!! Field::text('name', ['label' => 'Full name']) !!}

But you can also define it as part of the attributes array in the resources/lang/en/validation.php file:

    //resources/lang/en/validation.php
    //..
    'attributes' => [
        'name' => 'Full name'
    ],

Note that this is also the convention used by the Laravel Validator component, so this way you can have all your label texts in one place.

Learn more about the field builder

Translating alert messages

If the 'translate_texts' is set to true, this component will assume that all the alert messages are in fact language keys and will try to translate them. This means you can do things like this:

Alert::success('messages.users.updated')
		->button('messages.users.go_to_profile', url('users/profile'))

Of course if the lang key is not found, it will return the literal string (so you can also pass the full message instead of a lang key).

Learn more about the alert component

Translating menu items

If the 'translate_texts' is set to true, and you don't specify an explicit title for a menu item; the component will search for a lang key in: menu.[menu_item_key] if the key is not found, the package will attempt to convert the menu item key in a title format. For example:

//resources/lang/en/menu.php
return [
    'home' => 'Homepage'
];

//config/menu.php
return [
    'items' => [
        'home'  => [],
        'about' => ['title' => 'Who we are'],
        'contact-us' => []
    ]
];

{!! Menu::make('menu.items') !!}

Will return something like:

<ul>
    <li><a href="#">Homepage</a></li>
    <li><a href="#">Who we are</a></li>
    <li><a href="#">Contact us</a></li>
</ul>

Note that:

• "Homepage" is taken from the menu key "menu.home".
• "Who we are" is explicit defined (no translation is attempted)
• "Contact us" is generated from the key "contact-us" (since no lang key is provided)

Learn more about the menu generator