You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As #7456 includes the possibility to generate translation files and then to translate the project by providing translations, the actual workflow only exports one theme / style configuration of the project to the translation.
How to handle the translation of the whole project including multiple themes and styles?
Anyone having a working worflow.
We actually only translate the main theme by the current workflow which makes a bad surprise for any user switching the base theme of the project to another.
The current workaround is to replicate forms and fields with the style copy paste but it prevents us of inheriting future translations.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Feature description
As #7456 includes the possibility to generate translation files and then to translate the project by providing translations, the actual workflow only exports one theme / style configuration of the project to the translation.
How to handle the translation of the whole project including multiple themes and styles?
Anyone having a working worflow.
We actually only translate the main theme by the current workflow which makes a bad surprise for any user switching the base theme of the project to another.
The current workaround is to replicate forms and fields with the style copy paste but it prevents us of inheriting future translations.
Additional context
No response
The text was updated successfully, but these errors were encountered: