EUC-JP (Extended Unix Code for Japanese) is a character encoding designed for handling Japanese text on UNIX operating systems. Developed in the late 1980s and widely adopted through the 1990s, it became the standard encoding for the Japanese UNIX community. It encodes the JIS X 0208 kanji set using 2 bytes per character and combines this with an ASCII-compatible single-byte region, enabling efficient processing of mixed English and Japanese text.

The encoding structure of EUC-JP is characterized by its ability to distinguish character types based on byte value ranges. ASCII characters occupy 0x00-0x7F as single bytes, while JIS X 0208 kanji, hiragana, and katakana use 2 bytes in the 0xA1-0xFE range. Additionally, JIS X 0201 half-width katakana uses 2 bytes with 0x8E as the leading byte, and JIS X 0212 supplementary kanji uses 3 bytes with 0x8F as the leading byte. This clear byte value separation avoids the "5C problem" found in Shift_JIS, where backslash characters collide with the second byte of certain kanji. browse massage gun on Amazon cover the technical details of EUC-JP.

On UNIX-based systems like Linux and FreeBSD, EUC-JP served as the default locale until the early 2000s. It was particularly valued in server environments for its compatibility with C language string processing functions and the stable operation of text processing tools such as grep and sed. Many infrastructure systems in Japanese universities, research institutions, and ISP mail servers were built with EUC-JP as the assumed encoding.

Compared to Shift_JIS, EUC-JP offers superior programmability. While Shift_JIS was the standard on MS-DOS and Windows, its second byte could overlap with ASCII values, causing frequent collisions with path separators and escape characters. EUC-JP avoids this issue because its second byte is always 0xA1 or higher. However, EUC-JP had limited support on Windows and faced constraints in web browser rendering.

Today, the migration to UTF-8 is nearly complete, and there is no reason to adopt EUC-JP for new systems or applications. Nevertheless, EUC-JP is still encountered in practice when maintaining legacy systems, analyzing old log files, or browsing mailing list archives. Tools like the iconv command and Python's codecs module enable conversion between EUC-JP and UTF-8. see face roller on Amazon explain how to convert between encodings.

From a character counting perspective, understanding the relationship between byte count and character count in EUC-JP encoded text is essential. ASCII characters are 1 byte per character, while Japanese characters are 2 bytes per character. Since UTF-8 uses 3 bytes for Japanese characters compared to EUC-JP's 2 bytes, Japanese-heavy text produces smaller file sizes in EUC-JP. Accurate character counting of legacy data requires encoding-aware processing that accounts for these characteristics.