Skip to content
Snippets Groups Projects
Commit 2bc7b00b authored by Eliot Berriot's avatar Eliot Berriot
Browse files

Merge branch 'patch-1' into '662-context-documentation'

Nest multiple component parts by a dot instead of a /

See merge request funkwhale/funkwhale!582
parents 2fe403ed 7d52de5c
No related branches found
No related tags found
2 merge requests!582Nest multiple component parts by a dot instead of a /,!581See #662: documentation about i18n / contexts, and first contextualized strings
Pipeline #3174 passed with stages
in 3 minutes and 29 seconds
......@@ -483,19 +483,19 @@ The detail part, which is optional and refers to the contents of the string itse
Here are a few examples of valid context hierarchies:
- ``Sidebar/Player/Button/Title``
- ``Sidebar/Player/Button``
- ``Content/Home/Button/Call to action``
- ``Footer/*/Help text``
- ``*/*/*/Verb, Short``
- ``Modal/Playlist/Button``
It's possible to nest multiple component parts to reach a higher level of detail:
It's possible to nest multiple component parts to reach a higher level of detail. The component parts are then separated by a dot:
- ``Sidebar/Queue/Tab/Title``
- ``Content/*/Button/Title``
- ``Content/*/Table/Header``
- ``Footer/*/List item/Link``
- ``Content/*/Form/Help text``
- ``Sidebar/Queue/Tab.Title``
- ``Content/*/Button.Title``
- ``Content/*/Table.Header``
- ``Footer/*/List item.Link``
- ``Content/*/Form.Help text``
Collecting translatable strings
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment