Setek - 2:02 am on Aug 7, 2006 (gmt 0)

You talking with CSS or without CSS? Got any examples of how to make this type of chart.

If you want a plain, unstyled table, then don't use any CSS on it. If you do, you can put padding on the th/tds, a border colour, a background colour, whatever you want to make it look how you want.

You all suggested tables. How are tables any better for this then divs?

It is tabular data - as in, one value in one column corresponds to the value in the same row, in another column - and that is why a table is better than a div. Someone say, on lynx, or on a screen-reader, will not be able to understand your div version as well as they would if it were a table. Just because you -can- CSS divs to make it resemble a table, -doesn't- mean you should. Everything has its purpose, this is a table's purpose.

What about the extra cell on the left for the 130x130px image? How would you add that?

...
<tr>
<td><img src="/images/kanji/kanji01.jpg" /></td>
<td>romanji counterpart</td>
<td>english meaning</td>
<td>contextual usage</td>
</tr>
...

N.B.: This is an incomplete representation of a table, in fact, just a single row in your table, and can be repeated as per every kanji.

How do you get all 80 tables to repeat down the page so you can scroll and read all 80 Kanji?

You don't. Not 80 tables. 80 rows in 1 table. All corresponding data.

<table summary="Table of Kanji and meanings">
<caption>Table 1: Kanji and their meanings, with contextual examples</caption>
<thead>
<tr>
<th scope="col">Kanji</th>
<th scope="col">Romanji</th>
<th scope="col">English</th>
<th scope="col">Example</th>
</tr>
</thead>
<tbody>
<tr>
<td><img src="/images/kanji/kanji01.jpg" /></td>
<td>romanji counterpart</td>
<td>english meaning</td>
<td>contextual usage</td>
</tr>
<tr>
<td><img src="/images/kanji/kanji02.jpg" /></td>
<td>romanji counterpart for kanji02</td>
<td>english meaning for kanji02</td>
<td>contextual usage for kanji02</td>
</tr>
... [repeat for all 80 characters]
</tbody>
</table>

Pretty vague posts people.

To be clear, they're not vague responses, they're pretty indicative as to what you should use, and why. We naturally assumed you have a greater understanding of HTML, semantics for the web, etcetera. But that's okay, I hope this clarifies.