Hi 

Please find my responses inline.

• Test and stabilize the application user interface. - What does the stabilize mean?
  • This means that your application development has to be complete and the application should be stable without or with as few issues as possible. If the application is not stable and the development is ongoing or if there are issues which needs UI changes etc, the wizard when run will not be picking up all the field values/ strings from your application. This may result in your application improperly localized.
• Verify that the current system locale is the same as your base language. - Where can I look up my base language and current system locale?
  • ​​By default, the system locale will be english and the operator locale is also english. Operator locale can be found in the operator record ("locale" text input ).The general recommendation is to run the wizard in this default configuration.
• If your application uses text strings in a way that does not create references, create base field values in one of your regular application rulesets so the wizard can include this text in the translation package. - I use a 'getLocalizedText' method to get translated text inside Java code and I also created some field values beforehand. Is it enough?
  • Ideally that should be enough. Please reach out to me in case if you face any issues.
• Determine what language packs you have on your system. - How can I do this?
  • Check the rulesets instances from Records->Sysadmin->Ruleset. If you have rulesets with extensions "_locale" then you have a language pack of that particular locale. For example, if you have a german ruleset imported in the system, then you will be seeing the rulesets with "_de" extension in your rulesets landing page.

Hi 

Please find my responses inline.

• Test and stabilize the application user interface. - What does the stabilize mean?
  • This means that your application development has to be complete and the application should be stable without or with as few issues as possible. If the application is not stable and the development is ongoing or if there are issues which needs UI changes etc, the wizard when run will not be picking up all the field values/ strings from your application. This may result in your application improperly localized.
• Verify that the current system locale is the same as your base language. - Where can I look up my base language and current system locale?
  • ​​By default, the system locale will be english and the operator locale is also english. Operator locale can be found in the operator record ("locale" text input ).The general recommendation is to run the wizard in this default configuration.
• If your application uses text strings in a way that does not create references, create base field values in one of your regular application rulesets so the wizard can include this text in the translation package. - I use a 'getLocalizedText' method to get translated text inside Java code and I also created some field values beforehand. Is it enough?
  • Ideally that should be enough. Please reach out to me in case if you face any issues.
• Determine what language packs you have on your system. - How can I do this?
  • Check the rulesets instances from Records->Sysadmin->Ruleset. If you have rulesets with extensions "_locale" then you have a language pack of that particular locale. For example, if you have a german ruleset imported in the system, then you will be seeing the rulesets with "_de" extension in your rulesets landing page.