AppLocale

Open an older Japanese or Chinese application and the menus fill with question marks, accented Latin letters and boxes. Nothing is broken. The program is sending perfectly correct text and the system is decoding it with the wrong table. AppLocale fixes that for one program at a time, without touching anything else on the machine.

Understanding the cause makes the whole category clearer. Applications written before Unicode became universal store their text as numbered bytes, and the meaning of those numbers depends on which code page you read them with.

The system has a single setting deciding which table applies to all such programs, and when that setting disagrees with what an application expects, every character comes out as the wrong one.

One program, not the whole system

The blunt fix has always existed. There is a system-wide setting controlling the language used for these older applications, and changing it works, applies to everything at once, and requires a restart. Somebody running one Japanese program and everything else in their own language has to choose which set displays correctly.

AppLocale removes that choice. It launches a chosen program with a chosen code page applied to that process alone, so the application reads its own text correctly while everything else carries on unchanged.

A short wizard handles it. Point at the program, pick the language it expects, and optionally have a shortcut created so the next launch does the same thing without going through the tool again. That shortcut is the part people actually use.

Garbled text has two different causes

Check which symptom you have first, because the two look similar and are unrelated.

Empty rectangles mean the font has no glyph for those characters. The decoding worked and there is nothing to draw. Installing a font covering that script fixes it, and a viewer listing which fonts are actually installed tells you what you have before you go looking.

Readable but wrong characters, the Latin soup that spells nothing, means the bytes were decoded with the wrong table. That is the case AppLocale addresses, and no font will help.

The same distinction applies to text files, and Subtitle Edit shows and converts the encoding of subtitle files where exactly this problem is endemic.

The neighbouring problem it does not solve

Archives are the other place this appears constantly. A compressed file created on a machine using a different code page stores its filenames in that encoding, and extracting it elsewhere produces a folder of unreadable names even though the contents are fine.

Running the extraction tool through a locale wrapper is not the answer. Bandizip handles filename encoding directly, letting you choose how names are interpreted during extraction, which is the correct place to solve it.

Where it fails, and what came after

The tool is old enough that its rough edges are the main thing anybody meets.

Installers frequently fail under it. Running a setup program through the wrapper often produces an error or an installation that behaves as though nothing was applied, so install normally and apply the locale to the finished program.

Filenames created by the program can still come out wrong, since saving a file involves the system rather than only the application, and the wrapper’s reach ends at the process boundary. And it was built for a much older system generation, so on current machines it may refuse to install or misbehave.

Locale Emulator is the current answer to the same problem, doing the same job through a right-click entry with none of the compatibility baggage. Anyone starting today should begin there.

Conclusion

AppLocale solved a specific and irritating problem elegantly, letting one application read its own text properly while everybody else’s software carried on unaffected. The idea was right and the shortcut creation made it practical rather than a chore.

Time has caught up with it. Installers trip it, saved filenames can still emerge garbled, and the tool itself now struggles on the machines people actually run. Keep it in mind as the origin of a useful technique, use a maintained equivalent for the actual work, and remember that boxes mean a missing font rather than a wrong encoding, which saves installing anything at all.