To make the user experience better, I suggest dividing some Unlayer translations for specific situations. This way, we can make the translations clearer and more accurate, depending on the context.
For example every time in every tool we have header name "Content" like you can see below
That look's for form tool:
Here we want use instead of "Content", use just "Form", it will be nice split this because for example in "popups" we have "Content" like in form, but we want use "Content appearance", we want change the polish translations and now we cannot do this.
expertsender-jakubstankowski
commented
1 month ago
Hello!
To make the user experience better, I suggest dividing some Unlayer translations for specific situations. This way, we can make the translations clearer and more accurate, depending on the context.
For example every time in every tool we have header name "Content" like you can see below
That look's for form tool:
Here we want use instead of "Content", use just "Form", it will be nice split this because for example in "popups" we have "Content" like in form, but we want use "Content appearance", we want change the polish translations and now we cannot do this.
You shared some file where we can change translations, and it will be nice add splited already them. I mention about this file: https://github.com/unlayer/translations/blob/master/en.json
For example how it can be make it:
"tools.tabs.content": "Content",there can be something like this"tools.tabs.content.form":...or"tools.tabs.content.popup":....There's whole list where we want split the translations (and translate to polish):
WAS vs SHOULD BE Comparison: