Skip to content

Commit e15906f

Browse files
authored
Merge pull request spryker#316 from spryker/Fix/trans_usage_in_template
Merge pull request spryker#316 from Fix/trans_usage_in_template
2 parents 7442526 + ce8286b commit e15906f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Diff for: 202108.0/761b1f67-31a5-425e-b897-a622eb230a23.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ $stores['DE'] = [
4949
On the Storefront, you can use glossary keys to translate rendered content. The following examples shows how to do it using a dedicated extension for the Twig template engine:
5050

5151
```xml
52-
<div class="form-group"><label class="col-sm-2 control-label">First Name</label>
52+
<div class="form-group"><label class="col-sm-2 control-label">{{ 'First Name' | trans }}</label>
5353
<div class="col-sm-10">
5454

5555
<input type="text" class="form-control" name="first_name" value="{{ form.first_name.value }}">
@@ -59,4 +59,4 @@ On the Storefront, you can use glossary keys to translate rendered content. The
5959
</div>
6060
```
6161

62-
The keyword `trans` marks an operation exposed by the `TwigTranslator` extension. This means that the text of the label is either the default value provided in the view or the corresponding translation for it.
62+
The keyword `trans` marks an operation exposed by the `TwigTranslator` extension. This means that the text of the label is either the default value provided in the view or the corresponding translation for it.

0 commit comments

Comments
 (0)