khanh.pndc/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-01-02 17:59:36 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1425 from owncloud/phil-davis-dev-core-translation

Browse Source 
Dev Core Translation emphasize why not to split a sentence
This commit is contained in:
Carla Schroder
2015-08-10 09:17:35 -07:00
parent edc70c2740 ab79acd388
commit 5b6cf6ea07
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
developer_manual/core/translation.rst
View File

@@ -17,7 +17,7 @@ You shall never split sentences!
Reason:
~~~~~~~
Translators lose the context and they have no chance to possible re-arrange words.
Translators lose the context and they have no chance to possibly re-arrange words.
Example:
~~~~~~~~
@@ -34,7 +34,7 @@ Translators will translate:
* ' or "
* cloud
By translating these individual strings for sure the case will be lost of local filesystem and cloud. The two white spaces with the or will get lost while translating as well.
By translating these individual strings for sure the case will be lost of local filesystem and cloud. The two white spaces with the or will get lost while translating as well. For languages that have a different grammatical order it prevents the translators from reordering the sentence components.
Html on translation string:
~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -44,7 +44,7 @@ Html tags in translation strings is ugly but usually translators can handle this
What about variable in the strings?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In case you need to add variables to the translation strings do it like that:
If you need to add variables to the translation strings do it like this:
.. code-block:: php