TouchGFX translation with Crowdin

Streamline your app localization process with TouchGFX resource file support in Crowdin. Designed specifically for TouchGFX projects, this app ensures proper import and export of translations and produces files ready for use in your builds.

TouchGFX is a user interface framework for developing embedded systems with visually stunning graphics.

TouchGFX uses it's own multilingual XML-based format to store translatable texts. TouchGFX also provides a conversion tool to convert XML to XLSX format for translation. Doing translations directly in texts.xml has it's advantages. For example, you can integrate your Git repo with Crowdin and have your branches translated whenever you commit changes to your resources. All without having to do the conversion from XML to XLSX and back.

File Format Details

Sample File

<?xml version="1.0" encoding="utf-8"?>
<TextDatabase xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="texts.xsd" Version="4.20.0">
    <Languages>
        <Language Id="en"/>
        <Language Id="fr"/>
    </Languages>
    <Texts>
        <TextGroup Id="Group1">
            <Text Id="new_text_cdn" Alignment="Center" TypographyId="cn__bold_18px">
                <Translation Language="fr">New Text</Translation>
                <Translation Language="en">Nouveau texte</Translation>
            </Text>
        </TextGroup>
    </Texts>
    <Typographies>
        <Typography Id="cn__bold_18px" Font="cn__inkl.ttf" Size="12" Bpp="4" Direction="LTR" FallbackCharacter="?" WildcardCharacterRanges="0-9,0x25,0x2E"/>
    </Typographies>
</TextDatabase>

Translating TouchGFX

This app is sensitive to language codes. When uploading your files, make sure that your project language code is exactly the same as the source language code in your resource file. If you already have translations in your TouchGFX file, make sure they are all added to the Crowdin project and the language codes match.

Languages that are present in the resource file but not in Crowdin will not be imported. If the Crowdin project has more languages than the resource file, those languages will be added to the resource file.

If Crowdin has different language codes than you use in your resource file, or Crowdin has no languages you translate to, you can create custom languages in Crowdin.

Meta data from your resource files can't be edited by translators and won't be changed after export.