Pasting Into Translation Input Method from Browsers and Documents
Convert to plain text, remove hidden formatting and links, then test again in the target app.
1 Pasting is not just typing more text
Content copied from browsers, documents, or chat apps can carry formatting and hidden characters that are not visible at first glance.
Rich text may include line breaks, bullets, emojis, web links, tables, and invisible spaces. Those can change how the input text is read and translated.
Start by reducing the content to a plain short sentence. If plain text works, add complexity back gradually so you can find the trigger.
2 Turn pasted content into a testable input
Do not test with a whole web page, table, or chat transcript first. Complex content makes it hard to know whether the issue is formatting, language direction, target app behavior, or network state.
If this happens only in one app, combine this guide with the specific-app troubleshooting page.
Convert to plain text first
Paste into a plain text editor, then copy a short plain segment for testing. This removes most hidden formatting.
Remove links and extra line breaks
Links, bullets, tables, and line breaks can change text boundaries. Remove them before testing translation output.
Split long content
For long paragraphs, mixed languages, or term-heavy text, test shorter sections and confirm language direction first.
Return to the target app last
After plain text works, test again in the chat, document, or browser field. If only that app fails, use the specific-app guide.
3 Do not treat old notes as current feature guarantees
If a changelog mentions clipboard or paste-related behavior, still use the current download page, current version notes, and app UI as the source of truth.
If pasted content leads to blank output, use the blank-output guide. If the output language is wrong, verify source and target language first.
Editor note
FAQ
Pasted content can include rich formatting, hidden characters, links, line breaks, or emojis. Test with plain text before treating it as an input method issue.
Do not assume clipboard monitoring. Any clipboard-related capability should come from the current app UI, download page, or on-site notes.
Paste as plain text, remove extra spaces, links, and line breaks, then test smaller sections before using the target app again.
Check before you install
Before installing, open the download page and verify the current release, platform notes, and file availability. If something behaves oddly, check the FAQ next.