Google Docs can hold ordinary Sinhala Unicode text, so you do not need a Sinhala keyboard just to write a document there. Prepare your wording with English letters in SinhalaEditor, check the Sinhala output, then paste it into Docs. After that, use Docs for paragraphs, headings, collaboration, and downloads.
The key choice is Unicode. FM Abhaya and Isiwara legacy output depend on specific font mappings and are a poor fit for a shared Docs document. Installing a legacy font on your own computer does not automatically make that font available to everyone editing the file.
Prepare the text in the converter
- Open the Singlish to Sinhala Unicode converter in a browser tab.
- Leave the Unicode switch on.
- Type your wording in the Singlish box and read the converted text in the Sinhala box.
- For a direct mapping check, change Suggestions on to Suggestions off. For normal writing, you can use suggestions after verifying each selected word.
- Press Copy when the passage is ready.
| Singlish input | Sinhala Unicode output |
|---|---|
| mama gedhara yanawaa | මම ගෙදර යනවා |
| ammaa | අම්මා |
| shrii | ශ්රී |
If a vowel or special form is wrong, correct the input before moving the passage into Docs. The Sinhala typing chart helps with long vowels and case-sensitive combinations. Font changes in Docs cannot fix a wrong consonant entered at the source.
Paste into a Google Docs document
- Open the intended document in Google Docs and click the insertion point.
- Paste with Ctrl+V on Windows or Command+V on a Mac.
- If you are bringing in formatting from another source, use Edit and Paste without formatting, or Ctrl+Shift+V on Windows and Command+Shift+V on a Mac.
- Select the pasted text and choose a font that supports Sinhala from the font menu.
- Read one full paragraph before pasting the remaining sections.
SinhalaEditor's Copy button already copies plain text, so the website's selected font will not come with it. A different appearance in Docs is normal. What matters is that the Sinhala characters, vowel length, and joined forms remain correct.
If the clipboard action does not work in your browser, use the app's permitted paste method or keyboard shortcut. Do not keep clicking a button without checking the cursor location; repeated pastes can create duplicate paragraphs.
Find a suitable font in Docs
Select the passage, open the font dropdown, and look for a Sinhala-capable family. You can use More fonts to search the fonts Docs offers; where the script filter is available, choose Sinhala. Try Abhaya Libre or Noto Sans Sinhala if they are offered in your account's font list.
Docs has its own supported font catalogue. It does not provide a general upload box for any font file installed on your computer. If a particular desktop font is missing from Docs, choose an available Sinhala font instead of copying legacy text and hoping it will adopt the same appearance.
Compare the font at a sensible reading size, not only a large headline size. Check marks above and below the line. A font that looks attractive for a title may feel crowded across several pages. Use the Sinhala Unicode font selection guide to build a short test passage before committing to a family.
Format a document people can read
Set normal paragraphs first. Use paragraph styles for headings rather than enlarging every heading separately. Keep line spacing generous enough for Sinhala vowel marks, and use paragraph spacing instead of repeated blank lines.
Sinhala is written left to right, so you do not need right-to-left paragraph direction. For English names, email addresses, and reference codes, type the English directly in Docs after pasting the Sinhala. Otherwise the converter may interpret those words as phonetic Sinhala input.
For a letter or report, check page setup, margins, and page size before arranging the final page breaks. For a table, ensure cells have enough height and padding for marks. Avoid splitting a Sinhala word with manual spaces just to make it fit; change the column width or layout instead.
Work in small sections and review edits
Move a paragraph into Docs as soon as you have checked it. The typing page should not be treated as a full-document autosave system. Refreshing or closing it can clear your current draft. Docs can maintain its own saved document state, but confirm its save status and connection rather than assuming every change is already stored.
If other people edit the file, agree on a Unicode font and a clear heading structure. Ask reviewers to mark spelling changes rather than silently substituting an unfamiliar form. Names, addresses written in Sinhala, amounts, and formal wording deserve a separate review.
When using suggestions in the converter, remember that selecting a plausible word is not the same as confirming its meaning. Re-read the entire sentence once it is in Docs. A word that looks right in isolation may not be the word intended in context.
Download and inspect the finished file
- In Docs, choose File, then Download.
- Choose Microsoft Word (.docx) for an editable Word copy, or PDF Document (.pdf) for a fixed-layout delivery copy.
- Open the downloaded file rather than judging only the live document.
- Check headings, line breaks, tables, and joined forms.
- For PDF, select and copy a Sinhala line into a plain text field to check that it remains useful text.
Different apps can substitute fonts and change pagination. If the Word version shifts, check the font available in Word and the page setup. For final delivery, the Sinhala PDF checklist helps you catch clipping and searchability problems.
FAQ
Can I use FM Abhaya in a shared Google Docs file?
It is safer to use Unicode. Legacy text depends on a matching font mapping, and Docs does not simply inherit any custom font installed on your computer.
Will changing the document language convert English into Sinhala?
No. A language setting is not a translation or transliteration command. Prepare the Sinhala characters in the converter and paste them into the document.
Why does the downloaded Word file have different line breaks?
Font substitution, page settings, and differences between layout engines can affect wrapping. Check the downloaded DOCX in Word and use a verified PDF when exact pagination matters more than editing.