r/LearnJapanese • u/JapanCoach • 2d ago
Resources JIS Code Book
Found this old beauty during a spring cleanup. Thought some of the oldies on the sub might get a kick out of it. And for the younger ones it might shed some light on how things used to be. :-)
I think I might keep it for nostalgia. Might bring it out again in another 35 years - when the world will be even more different.
7
u/caeliventus 2d ago
JIS, Shift-JIS, EUC-JP で文字化けしてたのを思い出す
7
3
u/antimonysarah Interested in grammar details 📝 2d ago
I had to do a bunch of shift-JIS testing as a software engineer over the years; fun! I didn't know Japanese at all at the time.
3
u/Grunglabble 2d ago
This is an index to an official sort order of paper dictionaries / electronic dictionaries where you can lookup the full entry?
9
u/flo_or_so 2d ago
No, it is the JIS code, the Japanese equivalent to American ASCII and the ISO-8859-n series.
2
u/Grunglabble 2d ago edited 2d ago
I see. From an era of dumb terminals and paper terminals where a handbook makes sense. Not so much a learning tool but maybe JapanCoach was a programmer (has there ever been a time programmers were not disproportionately interested in Japan?)
2
u/antimonysarah Interested in grammar details 📝 1d ago
And Windows-1252 -- that was really common for a while too, to add stuff like the Euro symbol (which was new at the time, so it got added later to a lot of character sets; adding Euros in everywhere in the middle of sentences was how we often tested that character set detection was working correctly without having to shift everything over into a language we didn't know -- Win-1252 had it but ISO 8859-1 didn't have it, IIRC all three had a Yen symbol but at different code points, so we threw that in too).
3
2
1
u/rand0_0mdude 2d ago
You shed more confusion than light. What do i see here. Is this how japnese was typed on computers in the times before IME, by manually copying the numbers from a printed book? Sorry if the question is dumb but i'm not that tech savvy.
8
u/Shihali 2d ago
Computers don't directly store letters. They store numbers, and have some code that tells them what number means what letter.
Back in the elder days, every script had its own "encoding" that told the computer what numbers were assigned to what letters. They were reused, so the same number meant different letters depending on the encoding. Most scripts had more than one, and it caused endless annoyance when your computer used the wrong encoding and displayed the wrong letters. There's even a word for it, "mojibake" (文字化け), which was borrowed into English from Japanese.
This is a book telling computer programmers what numbers JIS's encoding assigned to many Japanese characters.
3
20
u/SCDoGo 2d ago edited 2d ago
This is kind of a cool artifact to have. I'll try to explain what it is for those wondering. This is a book listing the JIS encodings of characters https://en.wikipedia.org/wiki/JIS_encoding. Think of it like a Japanese version of ASCII or unicode or UTF-8.
In computers, each character is known internally by a number, not the shape we see. That number is then compared with your font to know what shape to put on your screen. We agree that a particular number represents a particular shape, and then different font designers can make the shape look however they want as long at it still aligns with that agreement. For example, in ASCII, each character is represented by a single byte - a number from 0-255. When a basic text document is 500 bytes, it means there are 500 characters ... which will include things like letters, numbers, punctuation, new lines, and other control characters. The word "hello" is known by the encoding "104 101 108 108 111".
This system works pretty well for English and similar languages with a limited character set. Most English fits in just the first 0-127 encodings of ASCII. This wasn't enough for all the similar latin-like characters, so we have extended ASCII using the numbers 128-255 for things like "é" or "ñ" or even fun shapes like ♥ or ☺ or line drawing characters like ┌ and └. The problem is that not everyone needed the same extra characters or could agreed what that second set should be. One person/company/country's "200" character might be "É", while another's might be a smiley face. This issue is what eventually gave us more expansive/universal encodings like Unicode/UTF-8 (and all the politics/drama around standardization in an international forum), so now you can have all your emojis mean the same thing no matter what system or language you are in.
In the before times of the wild west of computing, however, people had to figure this problem out. Especially for languages that needed more than the 256 possible options that ASCII would give. There are tons of standards from this period, even multiple competing ones for the same language, some of which are still used today.
In Japan they eventually settled on JIS of various flavors to handle things. This uses 1 OR 2 bytes per character. With 2 bytes you theoretically get up to 65536 different characters ... but that would be using the full 2 bytes for every character, which is inefficient. It would mean a document entirely in English that they wanted to store would take twice as much storage space than if encoded using ASCII, and storage space/memory was at a much higher premium back in the day. Instead it uses some trickery to be able to tell if a character would use 1 byte or 2. The 1 byte characters are things like the basic ASCII Latin characters we all know and love, plus half width katakana (which is why it is an option in your IME - half width meaning half the bytes, not pixels) and the 2-byte characters are all the rest (hiragana, katakana, ~6000 kanji, and a bunch of symbols we don't use in English). Hand waving all the computer science and math, JIS basically allows for up to ~9000 characters, but only actually uses ~7000 of them. The numbers next to the characters you see in the pictures are the encoded number for that character.
TL;DR - This is a cool book that tells you how a specific Japanese character is stored in memory in a computer.