• State Verified Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 2792 views
  • Users 0 members are here
Options

Q: Best Practice when changed IDs in MFC project?

Alexander Sailer

Hello group, 

 

due to unhappy circumstances I had to renumber my ids in my resources (MFC with VS2015). The renumbered ids are approcimately 400-500 ressource values (all kind of ressources). 

Now I'd like to know what is the best practice to get the already translated resources (100%) back in PASSOLO2016 after update my string list in my project? 

 

Kind regards 

Alexander
Rate translation
×
Suggest better translation
×
  • 0
    Hi Alexander,

    I think this would work:

    1. Before you update to the new IDs, make a copy of your Passolo file.
    2. Update.
    3. Leverage the translations against the copy of the database.

    You may have to set your leverage rules to tolerate the mismatched IDs, but if the resources are of the same type, you should be able to pick up the translations.

    Melanie
  • 0 in reply to Melanie Baeske
    Hi Alexander,
    You can Project export all to the glossary (Projet, Export, you pick PASSOLO Glossary Export)
    You will need to add the Glossary after and create the index. ( Tools, Glossary, click add button, after select the new glossary in the list and click on create quickindex)
    After you can do in Home, pre-translate (in the options... button you specify your new glossary only) to reimport the translation.

    You need to be carefull if you have for the same source word with different translation it will translate all the same work with the last translation found in the glossary.

    example:

    Pull => Handel in French : Poignée

    Pull => Pull from the wall in french : Tiré

    all the pull words will translate as Poignée or Tiré

    good day
    Dan
  • 0

    There are 2 different proposals. If these 400-500 string entries are coming from different resources (i.e. menus, dialogs and StringTable) and if the resource IDs haven’t changed I would suggest to use Leverage instead of a pre-translation with a glossary.

    Use the Leverage options to match resource ID and source string and do not activate to match the string ID. The Leverage will be more secure and you will avoid a lot of checks if multiple 100% matches occur.
  • 0 in reply to Achim Herrmann

    Hello Achim,
    I 1st tested the English language. In this language I'm able to check if the translation is in the correct direction. But I'm also not able to validate all translations.
    I tested the leverage in the way you told. There was approx. 10 strings translated. Afterwards I used leverage without the resource ID and got further 40 translations.
    The rest of the pre-translation I made with opened the copy of may project (100% translated) and made the auto translation (F8). Unfortunately my comments in the sources of may projects are missing.
    BTW: Attached you'll find the change report. I'm able to create a mapping of the changed IDs if this would be helpful.

    PASSOLO Report01.pdf

     

    I also tested the "Allignment" function. The result do not satisfy me: Too less strings are taken from target file. Just about 76% (pre)translated strings.  
  • 0
    Solution:
    I merged a copy of Passolo2016 project (100% translated -> *1) step by step manually to the Passolo2016 project with the modified IDs. Unfortunately I found no way to do this in another way.
    - Merged sources with comments
    - Merged target languages 1st with pre translation (only 100% match), then with choice, then with search the old MFC ID in the *1 project.
    - All modified strings/phrases where set to the state "For Review" or "Pre-translated"
    - The last step is to give it to the translators to check the pre-translated phrases and strings.