Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
{anchor:top}
{toc: class=contents}
h2. Overview
{styleclass: Class=topLink}[top|#top]{styleclass}
When translating individual pieces of content, it's important to remember that this process is less flexible as it doesn't allow the user to select languages to translate, or the content status (all, changed, none - untranslated). You can translate three different levels of content individually; Views, Reports, and Dashboards. This process will always export all text to be translated for the selected content, for all available languages, and will include any previous translations in the file.


h2. Translating Views
{styleclass: Class=topLink}[top|#top]{styleclass}
# Open the View you wish to translate by navigating to *Administration* > *Source Systems & Views*, and selecting it from the list.
# Place the View in draft mode and navigate to the final step of the builder - *View Summary*.
# Click on the *Create Exporta Translation File* link located in the bottom left corner of the *General* tab.
!01.png|thumbnail,border=1! 
# A CSV file will now be generated containing all the View related text. Follow standard browser settings to save and open the file.
# Update the CSV with the required translations
# You will need to navigate to the *View Summary* page if you have moved away, and click on the *Import Translated Content* link.
!02.png|thumbnail,border=1! 
# Locate your translated CSV and click the *Upload Data File* button
!03.png! 
# Yellowfin will now display one of the following validation messages when
## Your translation CSV upload is successful
!04.png! 
## There is an error in your CSV file, or an unsupported file type was used
!05.png! 
## One of the language column headers was changed and is not supported, in the example below *en_au* was changed to *australian* which is not a valid language code
!06.png! 
## Either the order of the standard (first four) columns has been altered or there is no language column
!07.png! 
## The CSV file was empty, or no file was selected
!08.png! 


h2. Translating Reports
{styleclass: Class=topLink}[top|#top]{styleclass}
# Open the Report you wish to translate by locating it in the *Report List*.
# Place the Report in draft mode by clicking *Edit* > *Format*
# Click on the *Edit* button again, this time selecting the *Create ana ExportTranslation File* option
!09.png! 
# A CSV file will now be generated containing all the customised Report related text. 
Follow standard browser settings to save and open the file.
{color:#CC0000}*Note:*{color} when exporting report translations, only text that has been customised in the report builder (since the view) will be included in the file. The report will inherit all other text from the view and as such, the view should also be translated. If there are no translations available, the original text will be used.
# Update the CSV with the required translations
# You will need to navigate to the *Report Preview* page if you have moved away, and click *Edit* > *Import Translated Content*.
!10.png! 
# Locate your translated CSV and click the *Upload Data File* button
!03.png! 
# Yellowfin will now display one of the following validation messages when
## Your translation CSV upload is successful
!04.png! 
## There is an error in your CSV file, or an unsupported file type was used
!05.png! 
## One of the language column headers was changed and is not supported, in the example below *en_au* was changed to *australian* which is not a valid language code
!06.png! 
## Either the order of the standard (first four) columns has been altered or there is no language column
!07.png! 
## The CSV file was empty, or no file was selected
!08.png! 

h2. Translating Dashboard Tabs
{styleclass: Class=topLink}[top|#top]{styleclass}
# Open the Tab you wish to translate by locating it on the *Dashboard*.
# Place the Report in draft mode by clicking the *Edit* button
!11.png! 
# Click on the tab drop down menu and select the *Translate* > *Create ana ExportTranslation File* option
!12.png! 
# A CSV file will now be generated containing all the Tab related text. 
Follow standard browser settings to save and open the file.
{color:#CC0000}*Note:*{color} when exporting dashboard translations, only text that is specific to the tab or its filters will be included. The tab inherits text in reports which inherit from the view and as such, the reports and view should also be translated. 
# Update the CSV with the required translations
# You will need to navigate to the *Tab* if you have moved away, and click *Translate* > *Import Translated Content*.
!13.png! 
# Locate your translated CSV and click the *Upload Data File* button
!03.png! 
# Yellowfin will now display one of the following validation messages when
## Your translation CSV upload is successful
!04.png! 
## There is an error in your CSV file, or an unsupported file type was used
!05.png! 
## One of the language column headers was changed and is not supported, in the example below *en_au* was changed to *australian* which is not a valid language code
!06.png! 
## Either the order of the standard (first four) columns has been altered or there is no language column
!07.png! 
## The CSV file was empty, or no file was selected
!08.png! 

\\
\\
{horizontalrule}
{styleclass: Class=topLink}[top|#top]{styleclass}