|
31.
|
|
|
{1} (<strong>{2}/{3}</strong> {3|string|strings} translated}
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TRANSLATION_PROGRESS
|
|
32.
|
|
|
You are currently selected to be using <strong>{1}</strong>. Content you add will be saved against {1}, but available in all languages. For it to be properly translated the website staff will need to process it via the content translation queue.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ADDING_CONTENT_IN_LANGUAGE
|
|
33.
|
|
|
You are currently selected to be using <strong>{1}</strong>. Content you add will be saved against {1}, but available in all languages. We would actually advise that you <a target="_self" href="{3}">switch to {2}</a> (the default website language) to add this content, and then you perform any translations from the “translate website content” option in the website footer.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ADDING_CONTENT_IN_LANGUAGE_STAFF
|
|
34.
|
|
|
You are currently selected to be using <strong>{1}</strong>. Content you edit will be saved against {1}, but your changes will not be applied to any pre-existing translations. Instead those translations will be marked outdated and come up for re-translation in the content translation queue which the website staff will have to process. We would actually advise that you <a target="_self" href="{3}">switch to {2}</a> to make this edit, and then you perform any translations from the “translate website content” option in the website footer.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]EDITING_CONTENT_IN_LANGUAGE_STAFF
|