Smartstaff
5
edits
Changes
no edit summary
==Edit Translation==
Each Language Library entry consists of the following fields
[[image:language Library-002.png]]
* '''Label:'''This is - Specified the Label on the page in the system text string that you wish to changetranslate.
* '''Language:'''- Specified the language to be associated with this translation. This is language settign will be compared to the users's language for which setting to determine if the Label will be changedtranslation is required.
* '''Translation:'''This is - Specified the translated Label translation to be used for this string in the Language selectionselected language.
* '''URL:'''This is - You can use the URL to restrict the the translation to a specific page on which . You would use this feature if you needed to apply a different meaning to the same string in a different location. If ''URL'' is left blank, the label translation will be translatedapplied to all pages.
==Example==
In this example, on the users Change Password page we word Organization is changed to Organisation (British Isles spelling). [[Image:Language_Library-003.png]] Similar translations would be required for each string that contains Organization; singular and plural and within other strings such as Organizational Hierarchy. The list of translations will look as follows if the additional translations were created. [[Image:Language_Library-004.png]] The effects of these translations will be seen throughout the system where these strings are referenced. ==Text Strings Containing a Variable==In the November 2018 upgrade, the way strings containing a combination of both text and variables are processed has changed. This change mainly affects setting pages.As such, you may need to change the word way you have entered translations into the Language Library to ensure both the text plus the variable field values are translated as expected. 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'''Policy, click '' to 'Save'Políticas de'' 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 users 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 translations as of the Spanish language option selectedNovember 2018 upgrade.====See below for an example and how to translate it.Text seen on screen is: <pre>Enable and manage standard fields for my level 1</pre>When Translation Audit Mode is on, the above will look like this: <pre>[*Enable and manage standard fields for @value:my level 1@*]</pre>In order to translate this string, you need to enter two strings '''separately''' into Language Library. The first string is: <pre>Enable and manage standard fields for @value@</pre>The second string replaces the @value@, so you would enter: <pre>my level 1</pre>Note: * Remove the colon after key, in our example the key is the word value* Make sure the key is enclosed in @ signs without any spaces; for example @value@ or @company@
You can tag a block of text to be processed by the Language Library using the ''ssTranslate'' syntax. See [[File:EditTranslation.pngTranslating_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.
* 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==
* The '''Page X of Y''' navigation label can be translated using the following syntax:
: '''Page @PN@ of @PT@'''
: So to translate to Spanish:
: [[File:Page translation.png]]
==See Also==
* [[Custom Field Language Settings]]
[[Category:Global Settings]][[Category:Translation]]
