This is related to translations for customer defined lobby elements and pages. What is the best way when scanning for translatable constants in Lobby? Is it to select module as ‘No Module’ or create a new module and use that for all custom translations?
I checked translations for both elements and pages in APP10. It fetched the module ‘CONFIG’ by default.
Even if I changed the component in Information section(changed and Saved) when rescanning the component remined unchanged. Anyhow, you can select one from the drop down.
You don’t have to create a new module as lobbies are configurations and belong to CONFIG.
After Saving the Translations, you can use Translation Manager to export and import as explained below. (Since the translations are stored in the ordinary translation tables in the database, it is possible to use the same tools used when translating the entire Enterprise Explorer.)
To Export Translations
Open Translation Manager -> Administration -> Export Language Files.
Choose layer User.
Check the All Main Types checkbox.
Select Export All.
Select the CONFIG component (under Foundation1).
Select the languages you want to export.
Click Export... and select where you want your files.
To Import Translations
Open Translation Manager -> Administration -> Import Language Files.
Click Import...
Select the files you want to import and click Open.
Eg:
You can see the translations in exported files.
I believe you have to select the relevant component which you used when you scanning translations. But, it is always better to keep the component as ‘CONFIG’.
The same way you can import the files to another environment.
Thank you for your response. I have referred the same F1 page, but wondering whether we should scan to a customized module for future export/import process like applying to another environment.
If we select ‘No Module’, how can we export from dev environment and import to another environment?
I checked translations for both elements and pages in APP10. It fetched the module ‘CONFIG’ by default.
Even if I changed the component in Information section(changed and Saved) when rescanning the component remined unchanged. Anyhow, you can select one from the drop down.
You don’t have to create a new module as lobbies are configurations and belong to CONFIG.
After Saving the Translations, you can use Translation Manager to export and import as explained below. (Since the translations are stored in the ordinary translation tables in the database, it is possible to use the same tools used when translating the entire Enterprise Explorer.)
To Export Translations
Open Translation Manager -> Administration -> Export Language Files.
Choose layer User.
Check the All Main Types checkbox.
Select Export All.
Select the CONFIG component (under Foundation1).
Select the languages you want to export.
Click Export... and select where you want your files.
To Import Translations
Open Translation Manager -> Administration -> Import Language Files.
Click Import...
Select the files you want to import and click Open.
Eg:
You can see the translations in exported files.
I believe you have to select the relevant component which you used when you scanning translations. But, it is always better to keep the component as ‘CONFIG’.
The same way you can import the files to another environment.
Thank you very much for detailed explanation. We are using Apps9, however it has CONFIG module. I have tried out with one lobby page and seems it works well.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.