• Home
• Imprint/Impressum
• Localization Glossary
• Who we are

I have two Sisulizer projects and I would like merge it to one project. Is this possible?

Sisulizer hasn’t implemented feature for directly merging several projects to one project. However, you can do it with Sisulizer in really easy and flexible way:

1. First, you should add all sources to one project, which belong to second project. You can add these new source items to project via “Add source” UI items available via “Project” menu, main toolbar icon or via context menu of Project Tree.

2. If your second project contains some translation languages unavailable in your targeted project, you should add these languages to this project via “Project” menu -> “Languages” or via “Select target language” dropdown menu on main toolbar.

3. Next, you should use “File” menu -> “Import”. This UI item opens dialog of Import Wizard. In first step you can select imported languages. Of course, you can use here standard Windows keys (Ctrl and Shift) for selecting multiple languages. Clicking on “Next” button navigates you to next wizard step, that is, “Import Wizard – Options”. Here you can find all import options. Below are short descriptions of most important options.

Import method

• By value – Sisulizer compares original values in both projects during import. The item is imported to all rows where the original value equals to the original value of the import item. This setting could automatically translate not translated originals in your first project which have been translated already in second project. However, you can lose some translations from second project, if this project contains originals translated in different way.
• By context – Sisulizer compares context values in both projects during import. The item is imported to the row where the context value equals to the context value of the import item. You can use this setting, if you would like get translations exact matched with translations from second (imported) project. So this option can be useful, if you have duplicate originals which have been translated in different ways in imported project.  However, this setting doesn’t translate automatically not translated items in first project identical with items from second project.
• By context first then by value – Sisulizer tries first to import by context. If no match, then import by value. This setting combines merits of both mentioned above methods.

Import also those items where the translated value equals to the original value
Some translations should be identical with identical with originals, for example names or some common captions (e.g. “OK” buttons) in most languages. So you can check this option.

Import only if context and original value match
I recommend checking this option, if you would like get results exact matched with your second (imported) project.

Import translation status:
I recommend checking of “Yes” option, because it allows you import to first project all translation statuses from second project

Comments
If your imported project contains translation comments, you can select “Import if there is no comment at the moment” setting, because it allows you import these comments.

Misc
If your second project contains items with “Do Not Translate” status and with maximum string length setting, you should also check following options:

• Import Read Only status
• Import maximum string length value

When you are ready, simply click on “Finish” button, and that’s all.

Janusz

Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.