Elona Wiki

This guide assumes the user already has both Wine and winetricks installed on their computer.

Dealing with Mojibake

An example of Mojibake. In this case, it's caused by text being improperly decoded (en_GB)

Mojibake (文字化け) (lit. character transformation) is the garbled text that is the result of text being decoded using an unintended character encoding.

Text Files

Open Text Editor from a menu. Pressing open, select the "Character Encoding" drop-down list and select SHIFT_JIS. If SHIFT_JIS is unavailable, select "Add or Remove..." and put SHIFT_JIS from an Available to a Chosen encoding. Then select the text file. This is useful for opening Japanese documentation and editing config.txt.


As most of the Elona archives (in my personal experience) are .zip encoded in SHIFT-JIS, use the following unzip command:

unzip -O shift-jis archive.zip

Replacing "archive.zip" with the target. This only fixes file name encodings.

The necessity of properly doing this depends on the variant of Elona being used, although omake overhaul is probably the only case I know of where a file name will appear in game - "user/god/omake_overhaul/�y�à�Ì�C�i�� �¹�n�z.eum" which when properly decoded becomes "【財のイナリ 聖地】.eum" (or translated roughly could become "Inari of Wealth's Sacred Place"). If improperly decoded, loading the Show House can cause the game to crash.

Inside Elona

Can be fixed by running Wine under Japanese locale. Of course, that being said, if the OS language is set to Japanese, this step is optional, as Wine will run under the ja_JP.utf8 locale anyway.

  1. Run this line under root to generate Japanese locale: locale-gen ja_JP.utf8
  2. Use LC_CTYPE=ja_JP.utf8 LC_COLLATE=ja_JP.utf8 to use Japanese locale.

This only effects how Japanese text is displayed in Elona.

Setting up


Sets up a Wine Prefix with the folder name "wine-elona" at home. If you decide to use the default wine prefix instead, simply remove "WINEPREFIX="$HOME/wine-elona"" from the below lines.

WINEPREFIX="$HOME/wine-elona" WINEARCH=win32 winecfg

WINEPREFIX="$HOME/wine-elona" winetricks dinput quartz directmusic gmdls

With the dll dinput being selected for [controller input?], and directmusic and gmdls for background music.

Then run the Elona executable (of your choice) via Wine, using your wine prefix of choice, i.e.

WINEPREFIX="$HOME/wine-elona" LC_CTYPE=ja_JP.utf8 LC_COLLATE=ja_JP.utf8 WINEDEBUG=-all wine elona.exe

in the case of launching Elona.


The font used by Elona depends on what the in-game language is set to:

Language 言語 Font Default
Japanese 日本語 font1 MS ゴシック
English 英語 font2 Courier New

As Wine doesn't provide either default font, Wine will use a fallback font instead.

The font chosen to be font2 should ideally be capable of supporting both English and Japanese characters (due to some variants having instances of untranslated strings). If font2 only supports English characters, Japanese characters won't be rendered, instead showing missing glyph characters. While using a Japanese font for font2 will always make Japanese text render, most will render spaces wider than usual.

When choosing fonts, the fonts should be monospaced to prevent any rendering errors. I personally use "IPAGothic" for font1 and "Unifont" for font2. For font1, I'd recommend any fonts in the fonts-japanese-gothic package.


  • Coopatroopa - the "Setting up Wine" section is based off of their Linux guide.
  • Several Anons - most of my knowledge of locales comes from them.

Technical Notes

Based off of my personal experience running Elona+ 1.89 on Wine 4.11, in a 32-bit, Windows 7 based prefix.

As Wine gradually improves its font rendering, the advice in this blog post is subject to change.

This page uses Creative Commons Licensed content from Wikipedia (view authors).