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
Describe the bug
Whenever a content element is translated via wv_deepltranslate / DeepL, words that have an opening HTML tag directrly behind them (no whitespace) get trashed in a specific way. In our case, product names are followed by a superscript registered trademark sign. In the translation, the whole product name is superscript as well!
To Reproduce
Create a content element (e.g. CType 'text') and add this to the field 'header' or 'bodytext' (code view): Try the new FOOBAR<sup>®</sup> now!
Translate it to a language of your choice. The result looks like this: Probieren Sie das neue <sup>FOOBAR®</sup> jetzt!
(the whole product name is superscript now - this means lots of "postprocessing" for us)
Expected behavior
We expected the translation to look like this: Probieren Sie das neue FOOBAR<sup>®</sup> jetzt!
Side info: Product names within text are generally not translated in our case.
TYPO3 Setup
TYPO3 Version 11.5.23
PHP version 7.4
Extension version 3.0.5
DeepL PAID API
composer setup
Additional context
We did some debugging an figured out that the result returned from the DeepL API already contains the error. We contacted the DeepL support (we are a paying client). They took 3 months (!) for a reply, stating that they could not do much about it. However, they had some suggestions like putting a whitespace between the product name and the registered trademark (which is no option for us, and no "solution" anyway). And they suggested the use of placeholder tags like <placeholder suptext="®" /> during translation.
Suggestion
Maybe, some workaround for such cases could be added to wv_deepltranslate - e.g. by using the "placeholder" tags suggested by the DeepL support (see last paragraph). They could be added dynamically before the translation, then removed thereafter?
The text was updated successfully, but these errors were encountered:
Describe the bug
Whenever a content element is translated via wv_deepltranslate / DeepL, words that have an opening HTML tag directrly behind them (no whitespace) get trashed in a specific way. In our case, product names are followed by a superscript registered trademark sign. In the translation, the whole product name is superscript as well!
To Reproduce
Create a content element (e.g. CType 'text') and add this to the field 'header' or 'bodytext' (code view):
Try the new FOOBAR<sup>®</sup> now!
Translate it to a language of your choice. The result looks like this:
Probieren Sie das neue <sup>FOOBAR®</sup> jetzt!
(the whole product name is superscript now - this means lots of "postprocessing" for us)
Expected behavior
We expected the translation to look like this:
Probieren Sie das neue FOOBAR<sup>®</sup> jetzt!
Side info: Product names within text are generally not translated in our case.
TYPO3 Setup
Additional context
We did some debugging an figured out that the result returned from the DeepL API already contains the error. We contacted the DeepL support (we are a paying client). They took 3 months (!) for a reply, stating that they could not do much about it. However, they had some suggestions like putting a whitespace between the product name and the registered trademark (which is no option for us, and no "solution" anyway). And they suggested the use of placeholder tags like
<placeholder suptext="®" />
during translation.Suggestion
Maybe, some workaround for such cases could be added to wv_deepltranslate - e.g. by using the "placeholder" tags suggested by the DeepL support (see last paragraph). They could be added dynamically before the translation, then removed thereafter?
The text was updated successfully, but these errors were encountered: