|
|
This is not part of the backoffice SPA, this page is a mustache template so the i18n is not the same and it won't be as trivial as the other.
I think we need to create one template for lang and backend should render based on http request headers.
On the other hand, this is not a screen that the merchant needs in any way. This screen is a fallback when there is no javascript enabled. |
|
|
|
With 0010819 the merchant should not be redirected to this pages.
Customer may be redirected to this pages but this is unlikely if merchant is using templates feature or is using a frontend like drupal.
Nevertheless, we should start from the backend. I see a "en" suffix on the files but I wonder if this is really supported. |
|
|
|
Looks like yes, lookup_template checks for MHD_HTTP_HEADER_ACCEPT_LANGUAGE.
The building process of the merchant-backend-ui doesn't support it. It only create .en.html files.
|
|
|
|
db8bee9b9..1ae203ea5 add supports for i18n
@Stefan you have to know add a new project to weblate. This one is located at packages/merchant-backend-ui
I still have to mark all the strings present in this projects for translation |
|
|
|
1ae203ea5..5d969971b 50 strings marked for translation
After these are translated to DE assign it back to me so I can complete the process and verify that all is ok @stefan |
|
