Question
Last activity: 23 Jan 2017 12:54 EST
When I run the Localization wizard for the Dutch Locale (nl_NL) with option 'Re-translate existing options' then the translation column in the generated excel file is empty and does not show the translated field values in the localized ruleset RBG_nl. Wha
When I run the Localization wizard for the Dutch Locale (nl_NL) with option 'Re-translate existing options' then the translation column in the generated excel file is empty and does not show the translated field values in the localized ruleset RBG_nl. What can cause this problem?
Our application has many field value rules in the ruleset RBG_nl. When I run the localization wizard for the dutch locale with option 'Re-translate existing options' then these field values are not available in the column Translation in the exported excel. So for some reason the localization wizard is not able to find the field value rules in the RBG_nl ruleset.
The version our Pega development server is 7.1.8
Message was edited by: Vidyaranjan Av| Included Category
Pegasystems Inc.
US
Hi Jan-Jaap
I have not actually tried this particular use case. I will try and get back to you on this thread.
Just to confirm , you are running the localization wizard while the locale is set to "Dutch" right ?
Jan-Jaap,
I have a few questions for you that should help us better understand your scenario:
- if you don't select the re-translate option, do you see the previously translated values?
- is this behavior unique to the Dutch language, or does it occur with any language choice?
- do the field values exist in both the base ruleset and the localized ruleset, or just the localized one?
- on step 2 of the wizard (Select Rulesets) are you checking the "Include field value from other rulesets" option and including any rulesets?
Thanks!
Pegasystems Inc.
IN
Hi Jan-Jaap,
As a diagnostic test, could you please execute the following steps while running the Localization Wizard -
1. Check "Include application layer rulesets"
2. Click the "Enable records for translation" button
3. Choose "No, do not include any example files" option
and finally Download the Translation.xml file. Now check whether the records are included for translation.
Hi David,
See below for my answers to your questions.
Regards,
Jan-Jaap
- if you don't select the re-translate option, do you see the previously translated values? [ Jan-Jaap: No I have tried that one too]
- is this behavior unique to the Dutch language, or does it occur with any language choice? [ Jan-Jaap: I don't know we only support english and dutch]
- do the field values exist in both the base ruleset and the localized ruleset, or just the localized one? [ Jan-Jaap: most only exist in the localized ruleset but few exists in both]
- on step 2 of the wizard (Select Rulesets) are you checking the "Include field value from other rulesets" option and including any rulesets?[ Jan-Jaap: No I have tried that one too]
Amex
US
Hi,
We also have similar issue in our project. Any solution recommended by PEGA for this issue.
The issue description is given below:
Expectation when we select the Re-translate existing translations? check box next to a selected language is that pega will pull all the previously translated verbiage and will be available in “Translation” column in pega generated sheet. This will help the translator to verify the existing translation and can make changes accordingly. But pega is not pulling any of the existing translation for same selected language. Refer below screenshot for more details.
Thanks.
Pegasystems Inc.
US
Jan-Jaap (and Jayaram),
Can you confirm that your localized rulesets match your application's major and minor ruleset version numbers? (so, if your application ruleset is MyApp:02-03-12, your localized ruleset would have to be something like: MyApp_nl:02-03-xx).
Thanks!