Smartstaff
5
edits
Changes
no edit summary
==Text Strings Containing a Variable==
System Administrators can see all strings that contain a variable, by following the steps below:<br />
1. Select the user menu in the upper-right corner of your header, in this drop-down menu, select '''System'''.<br />2. In the modal window that appears, toggle on '''Translation Audit Mode''', click '''Save ''' and then close the modal window.<br />
3. Refresh the page CTRL + F5 on a pc. Now, any text that can be affected and translated by the Language Library will be enclosed in a combination of square brackets and asterisks; for example [*text*]. Some text may be wrapped in @ signs; for example, @text@.
====If a string contains text wrapped in @ signs it will need to be modified to work with the way translations function as of the November 2018 upgrade.====
See below for an example and how to translate it.
Text seen on screen is:
You can tag a block of text to be processed by the Language Library using the ''ssTranslate'' syntax. See [[Translating_Web_Page_Views#Language_Library_and_ssTranslate|Translating Web Page Views]] for further information.
==Grammatical Gender==
There can be text within the platform that references configurable terminology (eg. L1/L2/L3 names, types, statuses, etc.) and some languages have grammatical gender. We typically assume masculine for the word, however this may not always be correct given the context of the text.
When the text contains configurable terminology then it could be the case that you cannot override the grammatical gender system wide since the configurable text can be anything. For this specific case, you will need to override it using the actual translation instead of using the placeholder.
====Example for French:====
The text for “'''New @value@'''” is translated to “'''Nouveau @value@'''” where '''@value@''' is the placeholder for the configured terminology.
* Correct if the configured term is “'''Payment'''” as its translation “'''Paiement'''” is masculine
* Incorrect if it is plural (“'''Payments'''”) as it would translate as “'''Nouveaux Paiements'''” so this requires an entry in the instance’s Language Library for “'''New Paiements'''” as “'''Nouveaux'''''' Paiements'''”
* Incorrect if the configured term is “'''Request'''” as its translation “'''Requête'''” is feminine and would translate to “'''Nouvelle Requête'''” and similarly when it’s plural “'''Nouvelles Demandes'''” so this requires an entry in the instance’s Language Library for “'''New Requête'''” as “'''Nouvelle Requête'''” or similarly “'''New Demandes'''” as “'''Nouvelles Demandes'''” for when it’s plural
==Notes==
