Question
375008155608
US
Last activity: 9 Oct 2017 6:02 EDT
Localization Unable to Save Export File
Has anyone ever had the localization wizard NOT generate the zip file of values to be translated? I click to download the extract, and it completes, however the file is never sent to my downloads folder. I am in a unique scenario...explained below.
The wizard originally worked fine for me. I am an English speaking developer working on a Spanish speaking application. When the wizard worked correctly, our system was set as the en_US locale.
Recently, I had cloud support update our system to have the es_CR locale. As soon as this happened, the issue began. I understand that you really would never need to translate an application from Spanish to Spanish, however it is necessary for me to develop in English now, and translate it to Spanish later.
As of now, my solution is going to be to keep the dev environment set up as en_US, so I can continue normal development, and then later run the localization wizard. My test, staging, production environments would be set as es_CR, and everything would run correctly.
Is this something that others have run into? Is this something that could be considered a defect, or am I stretching beyond the intended use of the localization wizard?
***Edited by Moderator Marissa to update categories***
375008155608
US
When reading the help, "Preparing your application for translation" I noticed the following:
Verify that the current system locale is the same as your base language in the original application.
Caution: Do not run the wizard in a locale other than your base language.
What is the base language? Where is that defined? Why can't the wizard handle this?
Pegasystems Inc.
US
Hi Jerome,
Which release your application is on?
On my Pega 7.2 system, I tried the localization wizard (select Designer Studio >User Interface > Localization Tools > Translate to New Language). I did a translation for my personal rules from English to Spanish. It was successful. The generated zip file (Translation_Spanish_2017-09-26_18-33-55.zip) was downloaded in 'Downloads' folder.
Please see captured snapshots.
Based on the below pdn help link,
https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
The base language is the "text in the original application".
Thanks,
Susan
375008155608
US
I am also on 7.2. The wizard works fine for translating a Spanish pack, as long as my system locale is not Spanish. If I have the cloud admins change the system to es_CR however, the Spanish translator will no longer work.
If in your system, you try to generate an English language pack, does it still generate a file for you?
I have no idea what is going on. There is nothing in the logs. For now, my solution is to keep the dev environment set as en_US, so I can run the localization wizard for Spanish language, but to have staging/prod set as es_CR so that system based actions...correspondence sent via SLA in particular, run under the desired locale.
Pegasystems Inc.
US
Hi,
One of Localization wizard prerequisites is :
"Verify that the current system locale is the same as your base language (text in the original application). Do not run the wizard in a locale other than your base language."
If your base language is "Spanish ES", then your locale should be the same. Then you can run Localization wizard.
How did you set system locale? Did you use Locale Settings (Designer Studio >User Interface > Localization Tools > Locale Settings)?
Can you show me a snapshot which shows your current locale?
Thanks,
Susan
375008155608
US
That is the problem. I am doing a Smart Dispute install, and he framework is entirely in English. Also, all of our developers are English speaking. So, by default, all of our rules are developed in English, but we then need to run the wizard to translate a Spanish language pack. Our production users will all be Spanish users, and the production environment will be set to use a Spanish locale. Ideally, the wizard would be able to handle this sort of scenario. Our current solution is to just have the dev environment set as an English locale so we can run the translation wizard, and keep the production environment set as a Spanish locale so that it behaves as needed for our client.
Pegasystems Inc.
US
Hi Jerome,
Based on your description, your current approach is fine with me.
Since the framework (Smart Dispute) is in English, then your dev env (used by English speaking) is set as English locale.
For your production env which is used for your client (in Spanish), so just keep it as Spanish locale.
thanks,
Susan