Skip to content
English
  • There are no suggestions because the search field is empty.

Why are characters consumed when translating back into German with the Translate module?

Overview

When using Eye-Able Translate, it can happen that characters are consumed, even though it seems like only a translation back into German is being made. This is due to which language is recognized as the source language when the script is loaded.

How does Eye-Able Translate determine the source language?

Eye-Able Translate translates based on the HTML Language Code that is present at the time the script is loaded.

Why can this lead to unexpected translations?

If a person has already used another translator (e.g., the browser translator), the following can happen:

  • The other translator has already changed the HTML Language Code

  • Or translations have already been made

When the Eye-Able Translate script is then loaded, it might recognize the content as not being in German and could carry out translations from other languages back into German (or even into other languages). These translations consume characters.

What improvement is planned?

In one of the upcoming dashboard updates, it is planned:

  • To allow the HTML Language Code to be set manually

  • That if there is a deviation in the HTML Language Code, the Eye-Able Translate button will no longer be displayed