Skip to Content (Press Enter)
Back to Ideas
21
Like
Follow Idea
Managing Multilingual Web Component Resource Files for Bulk Modules
495Views
6Comments
New
Service Center

Greetings Folks,

Before I jump on Idea discussion, would like to share my use-case :

I have around 60+ modules using the multilingual web component under one single product. We use a third-party paid translator tool to manage the translations.
Every time by the end of the sprint, we export the Translations files for all 60 modules via downloading the solution & then using cmd's which in the end give us translation files.

Now the actual pain is to update back each respective translated file by using the service studio of a module.

Idea :

It would be easy for developers If we get an option to directly update all the bulk files via service-center or any means like service-studio or API at once.

For instance, like Service Center showing all the modules using the multilingual web component & we have an option to either update any single module resource or all at once.


07 May 2020
Copy link to comment
Changed the category to
Service Center
08 May 2020
Copy link to comment
Merged this idea with 'Export and import language resources for several modules at once' (created on 02 Mar 2022 16:13:22 by Rob van den Broek)
05 Mar 2022
Copy link to comment

For one of our clients we are developing multiple apps that should support 8 languages. We are using the functionality to import and export language resources to provide the texts to be translated to the team that takes care of the actual translations, which works great.

The problem that we have is that we now have eight modules that need translations. This means that we have to manually export and import these documents 8 times, and it is hard to keep track of the different versions that are floating around the organization.

It would be a great help if we could export and import one Excel file for multiple modules, so that it is less work for developers to update the translations, and it is easier for the translation team to keep track of the different verions of the translation Excel that is being used.

02 Mar 2022
Copy link to comment

That would be great!

02 Mar 2022
Copy link to comment

Dear Rob,
In my case, I have 100 Modules that I export after every 2/3 sprints for translations.
Well for the Import ... yes it's always the pain to import all manually.

But for export I use a convenient approach:
- Created a solution for all that respective modules.
- Now I Download the Solution from Service Center
- Extract the Zip
- And I use CMD with a loop to extract the Translation Files from each OML.
- This way automatically I have a folder with all translation files.

Here's a similar idea that I have posted long back:
https://www.outsystems.com/ideas/8900/managing-multilingual-web-component-resource-files-for-bulk-modules/

Kindly either merge any of them :)

Thanks

02 Mar 2022
Copy link to comment

I can relate so much to this use case. Although I export every single translation file manually though service center and import them again. (Have no idea how to do it more efficiently)

Managing translation though e.g., service center or another centralized place, where you can handle multiple modules at the same time would be THE best feature in OS history IMO 😊 (Yes, I'm spending a lot of boring hours managing translations ... )

I’m already dreaming of all the hours of work saved on this. Outsystems, please get this going asap.

23 Dec 2022
Copy link to comment