silverstripe-framework/docs/en/02_Developer_Guides/01_Templates/08_Translations.md
Michael Pritchard fdbd899766 DOC Update SilverStripe to Silverstripe CMS
- Remaining Developer Guides and Upgrading
- SilverStripe in a namespace or api has not been change
- To keep PRs easier no formatting was changed

Update merge conflics with two files

Update Silverstripe Ltd, Silverstripe Cloud and Silverstripe CMS

Silverstripe CMS Ltd > Silverstripe Ltd
Silverstripe CMS Platform > Silverstripe Cloud
Silverstripe CMS Framework > Silverstripe CMS

Resolve merge conflict

Remove Framework from Silverstripe CMS Framework

- 3 files

Change SilverStripe CMS to Silverstripe CMS
2021-07-30 13:54:15 +01:00

36 lines
1.1 KiB
Markdown

---
title: Translations
summary: Definition of the syntax for writing i18n compatible templates.
icon: globe
---
# Translations
Translations are easy to use with a template, and give access to Silverstripe CMS's translation facilities. Here is an
example:
```ss
<%t Foo.BAR 'Bar' %>
<%t Member.WELCOME 'Welcome {name} to {site}' name=$Member.Name site="Foobar.com" %>
```
`Member.WELCOME` is an identifier in the translation system, for which different translations may be available. This
string may include named placeholders, in braces.
`'Welcome {name} to {site}'` is the default string used, if there is no translation for Member.WELCOME in the current
locale. This contains named placeholders.
`name=$Member.Name` assigns a value to the named placeholder `name`. This value is substituted into the translation
string wherever `{name}` appears in that string. In this case, it is assigning a value from a property `Member.Name`
`site="Foobar.com"` assigns a literal value to another named placeholder, `site`.
## Related
* [i18n](../i18n)
## API Documentation
* [i18n](api:SilverStripe\i18n\i18n)