i18n & l10n*

I agree, this is an issue which needs to be dealt with. It adds many hours of unecessary work in large applications.

Hmm, do I miss something, you just mark it as 'don't translate' and you can do that in bulk. I don't recall to ever lost hours of work because of this.

When working with larger applications, you might have hundreds or even thousands of CSS classes defined and used. Editing these in bulk would still require filtering for each CSS class in all modules and choosing "Don't translate". I'm not sure how that would not account for lost work hours, especially since translating CSS classes is seen as a bad practice that can lead to potential risks of missing CSS definitions. 

"Time is of the essence in the tech world, prompting developers to seek methods that speed up software creation" -https://www.outsystems.com/tech-hub/app-dev/what-is-rapid-app-development/

In conclusion, I don't see how the feature of including style classes in the translations would have any real-world use other than adding unnecessary complexity for large projects.

Hi Sebastian,

I see your point, what I did on a module, is set everything on don't translate and then select the elements that need translation (which are the lesser number of rows) and translate them. So the bulk of the work was done with one action.

-- Daniel