Migrate existing translations from one project to another




  • Avatar

    It's possible to merge identical strings automatically? or is necessary to migrate strings for every change? (for instance, one from android app and another for iOS app) 

    What's the recomended way to proceed in these cases?



    Comment actions Permalink
  • Avatar
    Carlton Flores

    it worked for me, thanks ! shareit  vidmate

    Comment actions Permalink
  • Avatar

    India's biggest lotteries that is generally well known in West Bengal Sikkim Nagaland, in this state. on the off chance that you need to get it first, add us to your top picks or register.

    Comment actions Permalink
  • Avatar
    Rebecca (Edited )

    Hello i go through your post i have some suggestion for you

    To migrate existing translations from one project to another, you can follow these general steps:

    1. Export Translations: Start by exporting the translations from the source project. This can usually be done through the translation management system or localization tool you are using. Look for an option to export the translations, which will generate a file containing the source text and corresponding translations.

    2. Analyze Exported File: Review the exported file to ensure that it includes all the necessary translations and that the format is compatible with the target project. It's essential to understand the structure and organization of the exported file for a smooth migration process.

    3. Import Translations: In the target project, locate the import functionality within your translation management system or localization tool. Select the exported file from the source project and follow the instructions to import the translations. Make sure to map the source text and corresponding translations correctly during the import process.

    4. Verify and Adjust: After importing the translations, carefully review and verify the results. Check for any inconsistencies, missing translations, or formatting issues. Make necessary adjustments and edits to ensure the translations align with the target project's requirements and context.

    5. Test and Validate: Conduct thorough testing to ensure that the migrated translations function correctly within the target project. Test different scenarios and language variations to confirm the accuracy and integrity of the migrated translations.

    6. Update Workflows and Processes: As you Tell Happy Star Survey migrate translations from one project to another, consider updating your workflows and processes to align with the new project's requirements. This may include updating reference materials, collaborating with the relevant stakeholders, and establishing clear communication channels to ensure a smooth transition.

    Thanks and regards,


    Comment actions Permalink
  • Avatar
    • Destination project: The project you want to migrate translation TO.
    • Source project: The project you want to migrate translation FROM.
    • Steps to migrate your translations:
      1. Add the languages you have translations for in your Destination project.
      2. In your destination project, click the "+" sign next to Files.
      3. Choose Other platforms.
      4. Select the Source project from the drop-down menu.
      5. Translations for phrases with 100% matching base CONTENT (NOT string ID) will be migrated. This is case/whitespace/newline sensitive. Plural phrases or phrases with placeholders will also be skipped.

    For example, take Source project string: I have an apple.

    The following Destination project strings will not migrate:

    • I have an Apple. <-- capital "A"
    • I have an apple. <-- whitespace
    • I have
    • an apple. <-- newline
    • I have an apple <-- missing punctuation

    Note: We have pre-checked Import translations only. This means:

    • Only translations with their source phrases that are 100% match in CONTENT (NOT string ID) will be migrated.
    • If Source project contains strings A, B, C, but the destination project only contains strings A and B, we would only import the translations for A and B (and not string C) to the destination project.
    • If you uncheck the box, all strings A, B, C (including the source text of C) would be imported into the destination project.

    Example workflow: Migrating translations for your iOS and Android projects

    1. Create your iOS project and upload base string files.
    2. After translating the base strings of your iOS project, create a separate Android project.
    3. Upload the base language strings.xml file of your Android app (generated from Android internationalization).
    4. Add the languages you wish to migrate translations for in your Android project. (The migration will NOT be successful without this step.)
    5. Follow the steps above in this article to migrate the existing translations in your iOS project to your Android project (please select to "import translations only"). Then our system will analyze which phrases have 100% base content match for your iOS and Android projects and migrate the translations. (Translations for plural phrases and phrases with placeholders will NOT be migrated.)
    6. After the migration is done, order translations for your remaining phrases. Select "phrases without translation" on the order page.

    Not all translations will be successfully migrated since:

    • placeholders are handled differently between iOS and Android platforms
    • iOS .strings can’t handle plurals (but .stringsdict does)
    • Android .xml handles plurals
    Comment actions Permalink
  • Avatar
    Adam F. Clark

    THaanks for sharing this.

    Comment actions Permalink

Please sign in to leave a comment.