Changes

[[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 - Classic ==# 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]]

== Translation XML Sample Breakdown ==[[System Administrator]]s are able to '''export''' [[Custom Fields|custom field]] translation settings and '''import''' [[Custom Fields|custom field]] translation setting files. The following are samples of '''Translation XML files Import''' and how to update the data'''Translation Export''' tabs are available within any Custom Fields Settings page.<pre><customfield> <language>14</language> <id>1234567</id> <caption><span style="color:red">Are you a charitable organization?</span></caption> <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>,</wvp> </formatxml> <formatxmltranslation> <audit>1</audit> <maxp>0</maxp> <searchable>0</searchable> <wvp>,</wvp> </formatxmltranslation> <options>No;Yes</options> <optionstranslation>No;Sí</optionstranslation> <numberformat></numberformat> <numberformattranslation></numberformattranslation> <tabname></tabname> <tabnametranslation></tabnametranslation></customfield></pre>

Translations for ==Best Practices==* The usual process to deploy a system in multiple languages would be to first configure all of the above field processes in one language. Then, all of the custom fields are contained within translated in the following XML tags:additional language(s). External user pages are enabled in multiple languages more often than entire systems.* <captiontranslation> </captiontranslation>Unless you are a native speaker, use a translation service to provide the translated field captions.* <formatxmltranslation> </formatxmltranslation>The exported translation file can contain tags such as HTML formatting or sslogic so when translating the content, remember to retain the original format.* <optionstranslation> </optionstranslation>For [[Custom Field Type: Select One – Combo Box]], ensure your translation file retains the store-value=display-value syntax.* <numberformattranslation> </numberformattranslation>* <tabnametranslation> </tabnametranslation>Some custom field types such as [[Custom Field Type: Special - Advanced Data Table]] benefit from manual updating rather than import of the translation file.

==Configuration – Essentials==1. Go to the UTA, in this case we will go to the Submission Manager<br />; 2. Go to Configuration Settings<languagebr />143. Go to Level 1 Custom Fields<br /language>: This tag contains the language ID4. See the [[Language]] page We want to Create a Translation File for a list of language IDsall custom fields in this UTA.; <idbr />12345675. Select the check box at the top to Select All custom fields.<br /id>: This tag contains the [[Custom Field IDFile:TranslationExport1.png|thumb|none|800px|Create translation file export button]]<br />6. This is used for matching when importing Click the "Create Translation File" button at the file and must remain exactly as exportedtop.; <captiontranslationbr /> 7. Select the file format, for this case we will use Excel 2010.<br /captiontranslation>: These tags contain the translated [[captionFile:Translationfile2.PNG|750px|Select file format]] as will be visible <br />8. Go back to the end user with Custom Field page and click the matching language ID settings"Text Import" button at the top.; <optionstranslation> <br /optionstranslation>: Should the field be a [[Custom Field TypeFile: TranslationImport2.png|thumb|none|800px|Select Many – Check Boxes|checkboxText Import]] or [[Custom Field Type: Select One – Combo Box|combo <br />9. Paste the data from above in the box]] fieldshown. Make sure to select the Column Delimiter, you we will be provided with select the Tab in this tag case. Select the imported language. Select the appropriate options in which to enter the translations for box and click the options"Analyze" button. ; <tabnametranslationbr />[[File:TranslationImport2.png|thumb|none|800px|Choose the language for import]]<br /tabnametranslation>: This tag controls 10. Map the columns to match the columns in the translation of excel sheet followed by clicking the "Parse Data" button.<br />[[Tabs#Navigation_Bar_TabsFile:Translationfile6.PNG|1000px|tabMap the columns for import]] <br />11. This window will make sure that the fields are mapped correctly, if there seems to be an error in which any of these, it will not be parsed into the field existsinstance. Once checked, click the "Upload" button, it will then show if the fields are Successful or Failed.