tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-06-29 07:59:31 +02:00
Code Issues Projects Releases Wiki Activity
552cf5944d
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

1.1 KiB
Raw Blame History

title summary icon
Translations Definition of the syntax for writing i18n compatible templates. globe

Translations

Translations are easy to use with a template, and give access to Silverstripe CMS's translation facilities. Here is an example:

<%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

API Documentation