• State Suggested Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 3678 views
  • Users 0 members are here
Options
Related

Struggling with leveraging

Torben Schulz

Hello passolo users,

 

as it comes out today I made a mistake using the leveraging mechanism one and a half year ago.

 

I had a source file in which one specific text was not translated, the field was marked as "not translated" and the color was red.

In my target file this text was already translated, the field was marked as "verified" and the color was black.

 

After the leverage process in my target file the text from the source file was taken even though this text was not marked as "verified" with the result, that in my target file there was a wrong text (the fallback text) and a wrong state (verified). As we use a cascading project structure this had quite an impact on all languages.

I can't remember what settings I exactly chose in April 2015 in the leverage dialog, but is there a way to ensure only to take verified texts from the source? What are the right settings to ensure that leveraging will not change any texts in the target that are marked as "verified"?

Currently we use Passolo 2011 but after our official release in the next few weeks we will use Passolo 2016. Not the time to change infrastructure in this phase ;-)

 

Thank you very much,

Torben
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hello Torben,

    I wouldn't mind seeing sample files in order to test this on my end but right off the bat I would suggest 3 things here:

    1) 'Hide' any strings in the source file that you do not wish to translate. You have to make sure and update the string list of the target files after doing this. By hiding strings in the source file, you will not even see them in the targets so there's no room for error.

    2) Is there a particular reason you are Leveraging vs. Pre-translating? I would say use 'Pre-translate' instead of 'Leverage'. Leveraging will pull based on the string IDs unless you change that setting. Depending on filetype, string IDs might not be unique in which case you will pull incorrect content. Also, leveraging is really only preferred if you need to bring in other parts such as Properties, States, etc.

    3) Make sure and first filter to all 'Untranslated strings' in the target files. Then select all filtered strings and Pre-translate, using the setting to 'Apply to: selected strings'. This will only apply the pre-translate to the filtered strings and will not touch the other strings.

     

    Thanks

    Luke Hipsher
Reply
  • 0

    Hello Torben,

    I wouldn't mind seeing sample files in order to test this on my end but right off the bat I would suggest 3 things here:

    1) 'Hide' any strings in the source file that you do not wish to translate. You have to make sure and update the string list of the target files after doing this. By hiding strings in the source file, you will not even see them in the targets so there's no room for error.

    2) Is there a particular reason you are Leveraging vs. Pre-translating? I would say use 'Pre-translate' instead of 'Leverage'. Leveraging will pull based on the string IDs unless you change that setting. Depending on filetype, string IDs might not be unique in which case you will pull incorrect content. Also, leveraging is really only preferred if you need to bring in other parts such as Properties, States, etc.

    3) Make sure and first filter to all 'Untranslated strings' in the target files. Then select all filtered strings and Pre-translate, using the setting to 'Apply to: selected strings'. This will only apply the pre-translate to the filtered strings and will not touch the other strings.

     

    Thanks

    Luke Hipsher
Children