[[System Administrator]]s are able to '''export''' [[Custom Fields|custom field]] translation settings as [[XML]] files ==Overview==People collaborate using SmartSimple Cloud in many languages. For example your applicants, reviewers and '''import''' program managers may work together in over 30 different [[Custom Fields|custom fieldlanguages]] translation setting files that are [[XML]]. The '''Translation Import''' and '''Translation Export''' tabs are available within any Custom Fields Settings page.
== Accessing the Translation Import/Export Tabs ==# Go to [[Global Settings]]#: [[File:Globalsettings.PNG]]# Under [[System Variables and Custom Fields]], click on the hyperlink for [[Custom Fields]]#: [[File:GSCustomFields.PNG]]# Using the left menu, select the [[Custom Fields]] This article will provide you would like to translate. The associated custom fields will load within the main window once selected.#: [[File:CFSelect.PNG]]# Above an overview of the list configuration of custom fields you will see a language dropdown selection field. Use this to select the language you wish to add translations for.#: [[File:CFlanguage.png]]# With a language other than English (Default) selected you will notice the ''Import'' and ''Export'' tabs have now changed to ''Translation Import'' and ''Translation Export''. These tabs provide you the ability to export the existing field translation settings for the selected language in XML format, or import XML-formatted field translation settings. #: [[File:CFtranslate_imp-expmultiple languages.png]]
[[System Administrator]]s are able to '''export''' [[Custom Fields|custom field]] translation settings and '''import''' [[Custom Fields|custom field]] translation setting files. The '''Translation Import''' and '''Translation Export''' tabs are available within any Custom Fields Settings page.
== Translation XML Sample Breakdown Best Practices==* The following are samples usual process to deploy a system in multiple languages would be to first configure all of Translation XML files and how to update the dataprocesses in one language.<pre><customfield> <Then, all of the custom fields are translated in the additional language>14</language> <id>1234567</id>(s). External user pages are enabled in multiple languages more often than entire systems. <caption><span style="color:red">Are * Unless you are a charitable organization?</span></caption>native speaker, use a translation service to provide the translated field captions. <captiontranslation><span style="color:red">¿Eres una organización de caridad registrada?</span></captiontranslation> <formatxml> <audit>1</audit> <maxp>0</maxp> <searchable>0</searchable> <wvp>* The exported translation file can contain tags such as HTML formatting or sslogic so when translating the content,</wvp>remember to retain the original format. </formatxml> <formatxmltranslation> <audit>1</audit> <maxp>0</maxp> <searchable>0</searchable> <wvp>* For [[Custom Field Type: Select One – Combo Box]],</wvp>ensure your translation file retains the store-value=display-value syntax. </formatxmltranslation> <options>No;Yes</options> <optionstranslation>No;Sí</optionstranslation> <numberformat></numberformat> <numberformattranslation></numberformattranslation> <tabname></tabname> <tabnametranslation></tabnametranslation></customfield></pre>* Some custom field types such as [[Custom Field Type: Special - Advanced Data Table]] benefit from manual updating rather than import of the translation file.
Translations for ==Configuration – Essentials==1. Go to the above field are contained within UTA, in this case we will go to the following XML tags:* Submission Manager<captiontranslationbr /> 2. Go to Configuration Settings<br /captiontranslation>* <formatxmltranslation> 3. Go to Level 1 Custom Fields<br /formatxmltranslation>* <optionstranslation> 4. We want to Create a Translation File for all custom fields in this UTA.<br /optionstranslation>* <numberformattranslation> 5. Select the check box at the top to Select All custom fields.<br /numberformattranslation>* <tabnametranslation> [[File:TranslationExport1.png|thumb|none|800px|Create translation file export button]]<br /tabnametranslation> ; <language>146. Click the "Create Translation File" button at the top.<br /language>: This tag contains the language ID7. See Select the [[Language]] page file format, for a list of language IDsthis case we will use Excel 2010.; <id>1234567<br /id>: This tag contains the [[Custom Field IDFile:Translationfile2.PNG|750px|Select file format]]<br />8. This is used for matching when importing Go back to the file Custom Field page and must remain exactly as exportedclick the "Text Import" button at the top.; <captiontranslation> <br /captiontranslation>: These tags contain the translated [[captionFile:TranslationImport2.png|thumb|none|800px|Select Text Import]] as <br />9. Paste the data from above in the box shown. Make sure to select the Column Delimiter, we will be visible to select the end user with Tab in this case. Select the matching imported language ID settings.; <optionstranslation> Select the appropriate options in the box and click the "Analyze" button.<br /optionstranslation>: Should the field be a [[Custom Field TypeFile: Select Many – Check BoxesTranslationImport2.png|thumb|none|checkbox]] or [[Custom Field Type: Select One – Combo Box800px|combo boxChoose the language for import]] field, you will be provided with this tag <br />10. Map the columns to match the columns in which to enter the translations for excel sheet followed by clicking the options"Parse Data" button. ; <tabnametranslationbr />[[File:Translationfile6.PNG|1000px|Map the columns for import]]<br /tabnametranslation>: 11. This tag controls window will make sure that the translation fields are mapped correctly, if there seems to be an error in any of these, it will not be parsed into the instance. Once checked, click the [[Tabs#Navigation_Bar_Tabs|tab]] in which "Upload" button, it will then show if the field existsfields are Successful or Failed.
==See Also==