Home / Blog / Why Sinhala Text Turns into English Letters When You Paste It

Why Sinhala Text Turns into English Letters When You Paste It

Sinhalaeditor · Nov 11, 2026

Why Sinhala Text Turns into English Letters When You Paste It

You copy a Sinhala sentence, paste it into another app, and suddenly see English-looking letters or symbols. The clipboard has usually not translated or destroyed your sentence. More often, the original text depended on a legacy font, and the new app is showing the underlying characters in a different font.

The first step is to identify the type of problem. Latin-looking output, empty boxes, clipped vowel marks, and an unchanged Singlish input are different symptoms. Each needs a different fix. Keep your original text or document untouched while you test a small copy.

Understand the most common cause: legacy text

Fonts such as FM Abhaya and Isiwara use mappings that place Sinhala shapes on character positions associated with Latin letters and other symbols. The shapes look Sinhala while the matching font is applied. Remove that font and the mapped characters become visible.

For example, SinhalaEditor's FM mapping represents මම with the character sequence uu. That sequence appears as Sinhala only with the appropriate legacy font. The Singlish source is mama, so the raw legacy output is not even the same thing as phonetic Sinhala written in English letters.

Unicode works differently: the characters themselves represent Sinhala. A suitable font draws them, and another Sinhala Unicode font can draw the same characters differently without changing their identity. The Unicode and FM Abhaya comparison explains when each format makes sense.

Match the visible symptom to the likely problem

What you seeWhat to check first
Latin-looking letters and symbolsLegacy output pasted without the matching font.
The original phrase mama gedhara yanawaaYou may have copied the Singlish input instead of Sinhala output.
Empty squares or missing charactersThe destination font or device may lack Sinhala support.
Sinhala letters with detached marksFont quality or complex-script shaping in the destination app.
Only the top or bottom of marks is missingLine spacing, text-box size, or clipping.

A font change is a sensible test for boxes or legacy display. It is not a universal conversion method. Applying a Unicode font to FM character sequences will not decode the old text, just as applying FM Abhaya to genuine Unicode will not turn it into the correct legacy sequence.

Copy fresh Unicode for messages and online forms

  1. Open the Sinhala Unicode typing tool.
  2. Enter your intended wording in the Singlish box.
  3. Keep the Unicode switch on. Do not select a legacy output for ordinary chat messages.
  4. Check the actual Sinhala words in the Sinhala box. Turn Suggestions off if you are comparing an exact key combination.
  5. Press the output's Copy button rather than selecting the English-letter source.
  6. Paste one short line into the destination and read it before pasting the rest.
Singlish inputSinhala Unicode output
mamaමම
ammaaඅම්මා
mama gedhara yanawaaමම ගෙදර යනවා

The Copy button transfers plain text. It does not carry the website's font appearance. That is normal for WhatsApp, Facebook, forms, and email: the destination app chooses the display font. As long as you copied Unicode and the app supports Sinhala, the characters should remain Sinhala.

If a design application really needs legacy text

Return to the checked Singlish source, turn Unicode off, and select the required legacy option: Default (FM Abhaya) or Isiwara. Copy again, paste into a new text object, select all pasted characters, and apply the corresponding installed legacy font.

Do not change FM output to Isiwara simply by changing the font in the destination. Generate the correct output mapping first. If the required font is not available in your app, resolve that before proceeding. The fact that the website can preview it does not mean the desktop font is installed.

For a more complete workflow, use the FM Abhaya copy-and-paste guide. Keep a Unicode master for future messages and website captions even when the print design uses legacy text.

Diagnose an older Word file safely

  1. Save a separate copy of the document.
  2. Select one short Sinhala passage and note the font name shown by Word.
  3. Temporarily choose an ordinary Latin font. If the passage becomes Latin-looking characters, it likely depends on a legacy mapping.
  4. Undo the change immediately so you retain the original appearance.
  5. Repeat on another passage if the document may mix different fonts or encodings.

A document can contain both Unicode and legacy Sinhala. Selecting everything and applying one font may repair one section while breaking another. Work section by section and keep a reference copy. Font fallback can also make the displayed font name misleading, so combine the font test with a plain-text copy test.

If all you have is an old FM file, SinhalaEditor's verified typing workflow is not a reverse-conversion service. Do not overwrite your source by feeding its legacy characters into the Singlish box. Preserve the document and arrange a separate checked conversion if you need reusable Unicode.

Separate spelling problems from display problems

If the same word is wrong in the browser and in every destination, examine the input. A missing h can change tha to ta, and a missing capital can change Na to na. Those are different Sinhala letters, not damaged font rendering.

If the word is correct in one app but broken in another, test a known Sinhala Unicode font and a new text object in the failing app. Increase line spacing if marks are clipped. Avoid manually adding spaces inside joined forms; that changes the text structure and can cause more problems later.

For a PDF, check both appearance and copy behaviour. A page can look Sinhala while the copied line remains legacy characters. For a social-media image, remember that the caption is separate text: prepare the caption in Unicode even if the artwork was made with a legacy font.

FAQ

Did the converter translate my Sinhala into English?

No. Latin-looking legacy output is a font-mapping issue, not a translation. If you see the original Singlish wording, check which box you copied.

Will pasting without formatting fix everything?

It can remove unwanted styling, but it cannot turn legacy character sequences into Unicode. For genuine Unicode, plain-text paste is often useful; for legacy text, the exact matching font is still required.

Why can a poster look correct while its caption is wrong?

The poster is an image, so its letter shapes are already pixels. The caption is live text rendered by the app. Use Unicode for that caption rather than copying legacy design text.