Broken Lao Text in Old Software: Fonts and Unicode Fixes

The question we actually get

"Our new computer shows boxes and broken vowels in the customer names, but the old PC in the back room reads the same file fine. And when we search for a name we know is there, the program says it cannot find it. Can you fix the file?"

We hear some version of this every month from Vientiane offices and provincial sites. The file is rarely damaged. The two computers read Lao letters with different rules. The fix is a short job: set up the keyboard once, convert the old data once, and check the printers.

What broken Lao text looks like

Broken Lao text has a small set of faces, and each face points to a different cause.

• Empty boxes or question marks where Lao letters should be. The computer has no font covering those codes.
• Vowels and tone marks in the wrong place, floating above the wrong consonant or pushed to the side. The font draws marks in positions that do not match the codes.
• Receipts that print half the name or strange symbols. The printer uses its own built-in letters instead of the computer font.
• Search and sort that fail. You can see the name on the list, yet typing it finds nothing, and names sort in a strange order.

Why it happens: two ways to store the same letter

A Lao document has two layers: the codes in the file, and the font that draws them. When both agree, you see correct text. When they disagree, you see boxes or shifted marks.

Older setups in Laos used non-Unicode Lao fonts, including the older non-OT Saysettha fonts. Those fonts placed Lao letters in code positions designed for Latin letters, typed through an old keyboard driver. On the one PC with that exact font and driver, everything looked right. Move the same file to a new PC without that font, and the letters fall apart.

Unicode fonts work differently. Each Lao letter has its own fixed code, the same on every computer. Phetsarath OT and Saysettha OT are the Unicode fonts most offices in Laos will meet. Windows also ships DokChampa and Lao UI, so a new PC usually displays Unicode Lao with nothing extra installed. A file stored in Unicode opens correctly on any PC or phone, because the codes mean the same thing everywhere.

A practical test: select a line of Lao text and change the font to Phetsarath OT. If the text turns to Latin gibberish, the stored codes are legacy codes. If it stays readable, the codes are already Unicode. Keep one old PC with the legacy font until conversion is done; it is the only place the old files still display correctly.

If your team also works across the two big office suites, our comparison of Microsoft 365 and Google Workspace explains how Lao text behaves in each.

The hidden duplicate: same look, different codes

The hardest case looks perfect on screen and still breaks search. The usual cause is one small spelling split: the vowel ຳ written two ways.

Lao has a single character ຳ, and it also has the two marks ໍ and າ, which placed together look nearly the same as ຳ. On older drivers, many typists entered ໍ plus າ as two keystrokes without noticing. In Unicode these are different stored codes, so the computer treats same-looking names as different strings. A customer file of 200 names can hold both spellings across 30 or 40 rows, and a search for one spelling misses every row typed the other way. Sorting splits the same way, and an Excel filter drops rows your eyes say should match.

The fix has three parts. Pick one spelling for new data. For most teams we would pick the single character ຳ: one code per vowel keeps search simple. Then normalize old data with find-and-replace after conversion, starting with names that hold the vowel. Then train the two or three staff who type customer names, because one person typing the old habit brings the split back within weeks.

What we usually see on sites is that one cleanup pass plus a short typing rule taped next to the keyboard ends the problem.

Setting up the Windows Lao keyboard correctly

Many offices already have the pieces but in the wrong order: a Unicode font with a legacy driver, or a legacy font with the Windows Lao keyboard. Both mix-ups produce shifting vowels. The goal is one matched pair: Unicode font plus the built-in Windows Lao keyboard.

• Open Settings, then Time and language, then Language, and add Lao. Windows adds its own Lao keyboard with the language.
• Remove or switch off any old third-party Lao keyboard driver on that PC, so two drivers do not fight over the same keys.
• Set the default document font in Word and Excel to a Unicode Lao font. Phetsarath OT suits formal letters; DokChampa and Lao UI are fine for internal sheets.
• Type a test line with vowels, tone marks, and the character ຳ, then change the font between Phetsarath OT and DokChampa. Correct Unicode text stays readable under both.

Bilingual staff often keep all three keyboards installed and switch several times per form. Lao customer data is always typed with the LAO indicator on and saved in a Unicode font.

Converting old data without losing it

Conversion is the step people fear, and it is safe when done in order. Back up first, convert a copy, check a sample, then switch.

• Copy every old file to a dated backup folder and keep the old PC untouched until the new files are accepted.
• List which files use the legacy font by opening each template and register and noting the font name. Files already in a Unicode font usually need no conversion.
• Convert with a tested converter on copies, one folder at a time, starting with the customer master list, because invoices and reports inherit its spellings.
• Check a sample of 20 to 30 rows by eye, covering vowels, tone marks, numbers, and mixed Lao and English rows. Search for five known names and confirm each one is found.
• Fix the ຳ split with find-and-replace, then run the same five searches again.
• Only then point daily work at the converted files, and keep the backup for one full billing cycle so a missed template can still be recovered.

For most small offices the sample check takes under an hour: 25 rows at roughly 2 minutes per row is about 50 minutes. Our notes on choosing an IT vendor in Laos list the questions that keep the scope clear.

Receipt printers, exports, and web forms

Three places outside Word still break Lao text after the PCs are fixed: receipt printers, file exports, and web forms with databases behind them.

Many thermal printers use built-in printer letters to run fast, and those letters often have no Lao, or an old Lao set. The fix is usually a driver setting, not a new printer: open the printer preferences and select graphic mode, raster mode, or "print as image" for Lao receipts. A 60 mm receipt line holds roughly 30 to 36 Lao characters at a readable size, so keep item names short and test one full receipt with the longest real product name first. Printing slows by a second or two per receipt in graphic mode, which most counters accept for correct names.

Exports fail for a different reason. A program that stores legacy codes can display fine while its Excel or PDF export writes those same legacy codes into the file. Excel then shows gibberish on any PC without the old font. Before buying or renewing, ask the vendor four questions: does the program store Lao in Unicode, does its Excel export open correctly on a PC with only DokChampa installed, does its PDF embed the Lao font, and which printer mode does it need for Lao receipts. A live test with ten real customer names answers all four faster than any brochure.

Web forms and databases are the simplest layer once the PCs are right. Any form that takes Lao names should save in UTF-8 end to end: the page, the connection, and the database columns. When one layer uses an older single-language setting, names corrupt where English and Lao mix in one field. Heat and the 17:00 to 19:00 brownouts do not cause font problems directly, but a PC that loses power mid-save can leave a half-written row. A small UPS on the cashier and server PCs prevents half-written rows when the power drops during rainy-season lightning.

Your one next step

Do the font test this week on the PC that shows the worst text. Select one broken line and switch it to Phetsarath OT. Whether it turns to Latin gibberish or stays Lao tells you if you need conversion or only a keyboard fix.

Send us on WhatsApp a screenshot of that test plus one exported Excel file with ten real customer names, and tell us the printer model on your receipts. We will reply with whether your data is legacy or Unicode, the conversion order for your files, and the exact printer setting to change.