Difference between revisions of "Category:Translation"
From SmartWiki
(→Configuration setting to be translated) |
Lorena Ruiz (talk | contribs) m (Adding translation variables) |
||
| (20 intermediate revisions by one other user not shown) | |||
| Line 11: | Line 11: | ||
==Performing Configuration work in another language== | ==Performing Configuration work in another language== | ||
| − | + | [[System Administrator]]s can perform the configuration work in one of three languages; '''English, French''' and '''Danish.''' | |
Choosing one of these languages only affect configuration pages and have no impact on the system that you configure for users. For all user elements you will need to provide the translations for all the objects. | Choosing one of these languages only affect configuration pages and have no impact on the system that you configure for users. For all user elements you will need to provide the translations for all the objects. | ||
| Line 19: | Line 19: | ||
==Configuring the platform for use by users in other languages== | ==Configuring the platform for use by users in other languages== | ||
| − | * | + | * A single language system has all field captions, tool tips, instruction, object names, statues etc. configured for the language you wish to use. |
| + | * A multiple language system has multiple field captions, tool tips, instruction, object names, statues etc. configured for each language needed. | ||
| + | * If a user switches to an language where you have not set any language setting then everything will be displayed in English. | ||
| − | + | The usual process to deploy a system in multiple languages would be to first configure all of the processes in one language. Then, all of the configured elements in the system are translated in the additional language(s). This provides an opportunity to refine the processes in the system in the one language and reduces multiple requests for translation of configured elements. | |
| − | * | + | The process for translation includes: |
| + | |||
| + | * Exporting the list of fields that need to be translated from the system as well as button labels, statuses, type names, portal instructions, emails, etc. | ||
| + | * The client provides the translated content | ||
| + | * Importing the translated fields into the system | ||
| + | * Manual updates are required for some of the items where there currently no import ability | ||
| + | * Testing end to end process in the new language | ||
| + | * Complete any remediation | ||
| + | |||
| + | Generally, our clients are responsible for providing all translated content. Many systems are available in multiple languages for the end users. However, only very few have multiple languages configured for internal staff/system administrators. | ||
| + | |||
| + | Your [[System Administrator]] is able to configure the translated content. The effort involved depends on the number of processes and portals which require updating. | ||
| − | ==Configuration | + | ==Configuration settings to be translated== |
There are multiple parts of the system where translation options are defined: | There are multiple parts of the system where translation options are defined: | ||
| − | + | * [[Custom Field Language Settings]] - each custom field in your system can be given multiple language settings so that the caption, selection options and tool tips can be displayed in different languages. Administrators are able to use [[Translation Import/Export]] to export and import custom field translations. If a translation service is used, ensure any html tags or sslogic syntax, etc. are retained. Some custom field types such as [[Custom Field Type: Special - Advanced Data Table]] benefit from manual updating rather than import of the translation file. | |
| − | + | * [[UTA_Standard_Field_Settings#Language|Standard Field Language Settings]] - each standard field in your system can be given multiple language settings so that the caption, selection options and tool tips can be displayed in different languages. System Administrators are able to configure each field. | |
| − | * [[Custom Field Language Settings]] - each custom field in your system can be given multiple language settings so that the caption, selection options and tool tips can be displayed in different languages. | + | * [[Login Page]] - System Administrators create a separate login page for each language you want to support |
| − | * Standard Field Language Settings - each standard field in your system can be given multiple language settings so that the caption, selection options and tool tips can be displayed in different languages. | + | * [[Signup Page]] - each signup page in your system can be given multiple language settings so that the translations of instructions, as well as custom and standard field captions, are displayed in different languages. |
| + | * Organizations - includes standard and custom fields, status captions, submit buttons, SmartCheck Validation, List view captions | ||
| + | * People - includes includes standard and custom fields, status captions, submit buttons, SmartCheck Validation, List view captions | ||
| + | * Roles and [[Client Categories|Categories]] - System Administrators are able to update the captions of user roles and categories | ||
| + | * [[UTA Settings]] - includes status captions, type captions, submit buttons, SmartCheck Validation, Invitation Templates, List view captions for each UTA as well as each level | ||
| + | * [[Transactions]] - includes status captions, type captions, submit buttons, SmartCheck Validation, List view captions | ||
| + | * Portals including Shortcuts | ||
| + | * [[Workflows_Overview#Task_Type:_Acknowledgement|Workflow Email Templates]] - each workflow email can be configured with [[SSlogic]] to identify the [[language]] of the user using ''@me.langid@'' | ||
| + | * [[Email|Email Templates]] | ||
| + | * [[Using Language Translation in Reports|Reports]] - Users toggle the '''Enable Translation''' option and when a language specific version is required, add the parameter for the language to the report url. | ||
| + | * [[System Variables]] - System Administrators may need to create new system variables for referencing common variables. For example, the name of the client in different languages. | ||
* [[Language Library]] - for hard-coded labels on core SmartSimple pages, translations can be entered into the Language Library. | * [[Language Library]] - for hard-coded labels on core SmartSimple pages, translations can be entered into the Language Library. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Translating Content== | ==Translating Content== | ||
| − | In addition to the translation of the user interface, the platform also | + | In addition to the translation of the user interface, the platform also supports the translation of content. So if a user enters content in Chinese the content can be '''automatically''' translated to any other language and the resultant translation stored in another field. |
| − | * The purpose of this feature is not to replace high quality translation service that your organization used but rather to provide quick translation of content that would otherwise be unavailable to someone that does not understand the source language. | + | * The purpose of this feature is not to replace the high quality translation service that your organization used but rather to provide quick translation of content that would otherwise be unavailable to someone that does not understand the source language. |
* For details of this feature, please review the following article [[Enable Translation Service]]. | * For details of this feature, please review the following article [[Enable Translation Service]]. | ||
==Using UK English== | ==Using UK English== | ||
| − | If a user sets their language to UK English then you will need to ensure that you have provided translations for | + | If a user sets their language to UK English then you will need to ensure that you have provided translations for standard fields such as organization (to organisation) and Postal Code /Zip (to Postal Code). |
| + | |||
| + | ==Variables== | ||
| + | Below are a list of translation-specific variables you can use. | ||
| + | |||
| + | * '''@type_lang@''' : Outputs the translated type name. | ||
Latest revision as of 11:23, 31 March 2023
This category references articles related to providing SmartSimple to different users in different languages.
Contents
User Language Setting
Each user can select the language of their choice through System Profile menu. There are over 20 languages available. However changing language does not automatically translate the system. The behavior of the system will still depend on the configuration.
- If all interface elements have been translated then the entire system will be rendered in the selected language.
- If only parts of the interface have been translated then only the translated components will be rendered in the selected language, the rest will be rendered in English.
- If nothing has been translated for that language then everything will be displayed in English.
Note: you can always see the Language ID (numeric value) being using in the Address Bar of your browser and, in fact, you can simply change that number to change the language.
Performing Configuration work in another language
System Administrators can perform the configuration work in one of three languages; English, French and Danish.
Choosing one of these languages only affect configuration pages and have no impact on the system that you configure for users. For all user elements you will need to provide the translations for all the objects.
- If a System Administrator switches their language to any these three languages then the entire platform will be rendered in that language.
- If any other language is selected then the system will continue to rendered in English.
Configuring the platform for use by users in other languages
- A single language system has all field captions, tool tips, instruction, object names, statues etc. configured for the language you wish to use.
- A multiple language system has multiple field captions, tool tips, instruction, object names, statues etc. configured for each language needed.
- If a user switches to an language where you have not set any language setting then everything will be displayed in English.
The usual process to deploy a system in multiple languages would be to first configure all of the processes in one language. Then, all of the configured elements in the system are translated in the additional language(s). This provides an opportunity to refine the processes in the system in the one language and reduces multiple requests for translation of configured elements.
The process for translation includes:
- Exporting the list of fields that need to be translated from the system as well as button labels, statuses, type names, portal instructions, emails, etc.
- The client provides the translated content
- Importing the translated fields into the system
- Manual updates are required for some of the items where there currently no import ability
- Testing end to end process in the new language
- Complete any remediation
Generally, our clients are responsible for providing all translated content. Many systems are available in multiple languages for the end users. However, only very few have multiple languages configured for internal staff/system administrators.
Your System Administrator is able to configure the translated content. The effort involved depends on the number of processes and portals which require updating.
Configuration settings to be translated
There are multiple parts of the system where translation options are defined:
- Custom Field Language Settings - each custom field in your system can be given multiple language settings so that the caption, selection options and tool tips can be displayed in different languages. Administrators are able to use Translation Import/Export to export and import custom field translations. If a translation service is used, ensure any html tags or sslogic syntax, etc. are retained. Some custom field types such as Custom Field Type: Special - Advanced Data Table benefit from manual updating rather than import of the translation file.
- Standard Field Language Settings - each standard field in your system can be given multiple language settings so that the caption, selection options and tool tips can be displayed in different languages. System Administrators are able to configure each field.
- Login Page - System Administrators create a separate login page for each language you want to support
- Signup Page - each signup page in your system can be given multiple language settings so that the translations of instructions, as well as custom and standard field captions, are displayed in different languages.
- Organizations - includes standard and custom fields, status captions, submit buttons, SmartCheck Validation, List view captions
- People - includes includes standard and custom fields, status captions, submit buttons, SmartCheck Validation, List view captions
- Roles and Categories - System Administrators are able to update the captions of user roles and categories
- UTA Settings - includes status captions, type captions, submit buttons, SmartCheck Validation, Invitation Templates, List view captions for each UTA as well as each level
- Transactions - includes status captions, type captions, submit buttons, SmartCheck Validation, List view captions
- Portals including Shortcuts
- Workflow Email Templates - each workflow email can be configured with SSlogic to identify the language of the user using @me.langid@
- Email Templates
- Reports - Users toggle the Enable Translation option and when a language specific version is required, add the parameter for the language to the report url.
- System Variables - System Administrators may need to create new system variables for referencing common variables. For example, the name of the client in different languages.
- Language Library - for hard-coded labels on core SmartSimple pages, translations can be entered into the Language Library.
Translating Content
In addition to the translation of the user interface, the platform also supports the translation of content. So if a user enters content in Chinese the content can be automatically translated to any other language and the resultant translation stored in another field.
- The purpose of this feature is not to replace the high quality translation service that your organization used but rather to provide quick translation of content that would otherwise be unavailable to someone that does not understand the source language.
- For details of this feature, please review the following article Enable Translation Service.
Using UK English
If a user sets their language to UK English then you will need to ensure that you have provided translations for standard fields such as organization (to organisation) and Postal Code /Zip (to Postal Code).
Variables
Below are a list of translation-specific variables you can use.
- @type_lang@ : Outputs the translated type name.
Pages in category ‘Translation’
The following 10 pages are in this category, out of 10 total.
