mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-01 21:58:51 +02:00
Merge remote-tracking branch 'origin/3.0' into 3.1
Conflicts: i18n/i18n.php
This commit is contained in:
commit
8a3eebf289
@ -787,7 +787,7 @@ a map around any `SS_List`.
|
||||
$map = new SS_Map($members, 'ID', 'FirstName');
|
||||
|
||||
Note: You can also retrieve a single property from all contained records
|
||||
through `[api:SS_List->column()]`.
|
||||
through [SS_List->column()](api:SS_List#_column).
|
||||
|
||||
## Data Handling
|
||||
|
||||
|
@ -279,7 +279,7 @@ There are a few special cases:
|
||||
## Language definitions
|
||||
|
||||
Each module can have one language table per locale, stored by convention in the `lang/` subfolder.
|
||||
The translation is powered by `[Zend_Translate](http://framework.zend.com/manual/en/zend.translate.html)`,
|
||||
The translation is powered by [Zend_Translate](http://framework.zend.com/manual/en/zend.translate.html),
|
||||
which supports different translation adapters, dealing with different storage formats.
|
||||
|
||||
By default, SilverStripe 3.x uses a YAML format (through the [Zend_Translate_RailsYAML adapter](https://github.com/chillu/zend_translate_railsyaml)).
|
||||
|
Loading…
Reference in New Issue
Block a user