Resources | Resources |



Excel Add-in workflow

If not using the option to translate strings directly in the Excel file, the following is a description of the workflow using the Excel Add-in.

  1. Developer opens a CAR file in Excel and uses the Add-in to save the source-language string resources as an Excel workbook (.xlsx) file.

  2. Developer inserts a new column to the spreadsheet and introduces a column heading with the language code for each target language (in the example below, ES for Spanish), then saves the file. See Language support) for a list of supported languages and codes.

    Note: In practice, developers will usually do better to send one workbook with one target-language column to each translator in order to avoid confusing translators. Nevertheless, the Excel Add-in allows for multiple target languages, each in a separate column, in the same .xlsx file. This may be useful when compiling a master copy of all translations at the end of the project.

  • Developer sends the .xlsx file to the translator.
  • Translator translates the strings in the new column, saves the workbook and returns it to the developer.

  • Developer opens the workbook in Excel and uses the Add-in to save the file in CAR format. The

    Add-in generates a separate CAR file for each language, with a language suffix (in this case, _EN and _ES) before the file extension.

  • Developer copies the translated CAR files into respective application directories (see "Directory structure" in the Localization Technology Guide on the Brew MP website).
  • Developer compiles localized BAR files from the command line, the Resource Manager or the IDE (Visual Studio or Eclipse), then runs and tests the resulting binaries (including other required files) in Simulator or on the device: