I love playing with data and I love Japan. So choosing kanji (one of the characters systems in the Japan) for my research assignment wasn’t a hard choice. The beauty of kanji for me lies in the contradiction between the (sometimes) poetic meaning of the characters and the systematic feel of the whole set. All the data about the kanji is written down: in what grade one should learn a character, in how many combinations the character can be used, how many strokes should be used to write the kanji and in what order they should be put down.
I started learning the kanji a couple of weeks ago using the Heisig system. This system is created by James W. Heisig used in his book ‘Remembering the Kanji’. This system mainly focuses on the visual appearance of the characters and really tries to see the Kanji as building blocks. You learn a character and after that you will learn characters where the original character is a part of, in shape and meaning. The Japanese don’t really use this kind of system. They only use one basic shape called a radical to divide all the Kanji in seperate groups.
I used this visual, building block system as my starting point and was looking for a way to make this visible. I wanted to build an interface where one could browse through all the kanji using this Heisig system, so it would be clear that there ‘are no complex characters in kanji’. I know this is not really true, but in a way every kanji always consists out of a small group op basic shapes. So no difficult pictographs with lots of scribbly lines, but different components put together to create a new meaning. I called it Kanji Breakdown:
I really wanted to make these different layers visible. So the character for ‘dr.’ is created out of two components; needle and speciality. This sounds pretty logical. The character for ‘speciality’ itself is also combined out of components. For some Kanji this breakdown goes as deep as 7 or 8 steps.
The story for this kanji is a little bit more abstract, but when you think of a needle as a very tiny precise point into a certain field, ‘speciality’ doesn’t sound as strange anymore. It is good to remember that these aren’t the official stories behind this kanji, but they are mainly used to help one remember the kanji visually and by its meaning.
I knew I wanted to visualize this system, but there wasn’t exactly a complete dataset floating around besides the book itself. So a big part of my work was to insert the correct data into the database. I created some very simple (and ugly) programs to help me fill up the database with data I read in the book.
and this program to help me save the position of every component within a certain kanji:
I only had to drag a box around the component and the size and location was stored inside my database. With this data now at hand I started looking for a way to visualize this system.
It seemed quite logical to place the 2048 kanji into a 3D-model, because of these ‘complexity layers’. The level of complexity in this screenshot goes from left to right. Every kanji on one layer always has at least one component coming from one layer to the right. The kanji in that layer also has at least one component which is stored in the layer to its right, and so on. Lines are drawn between these components and compounds. The layer all the way to the right is a special layer. It consists out of characters which aren’t really kanji itself (i.e. you can’t write them as seperate kanji) but Heisig uses them in his system as building blocks for other kanji.
The project is presented on a 40+ inch touchtable where people can play around with the 3D-model. An interface to the right (not shown in these screenshots) is used to travel from one kanji to another using its components or compounds. The whole 3D-model rotates around the selected kanji and shows all the possible next steps where one could go to next (all of the current selected kanji components and compounds with their translation).



















































