List of known issues and limitations of Instant Translation.
- Special Pages, such as Special:Search and, Special:Login, are not translated.
- Web crawlers and spiders cannot access translated content.
- Content translation must be manually requested through the translation menu. It is not triggered based on the geographic location of the user.
- Filenames of attachments and their contents are not translated.
- Images and alt-text descriptions are not translated.
- Instant Translation may fail when the content is too large, the translation service is temporarily unavailable, or the translated content has invalid formatting.
- Search queries are always performed in the source language of the site.
- Right to Left (RTL) languages will not be available if the source language is LTR and vice-versa.
- Content is not editable in the translated language.
- The language report is based on translated content consumption. The language report does not show who initiated the translation.
- Navigation breadcrumbs, with the exception of Home, are not translated.
- The add guide tab action is available when the page is translated.
- Page Restrictions menu entry is shown when the page is translated.
- Content with an XML namespace prevents the instant translation process (e.g.
<svg xmlns="http://www.w3.org/2000/svg">). The workaround is to not translate such content by adding the
translate="no"attribute to the problematic HTML (e.g.
<svg translate="no" xmlns="http://www.w3.org/2000/svg">).
- Adding the
translate="no"attribute to a word or phrase in the middle of a sentence can alter the meaning of the sentence in other languages.