Tagging XML Tables

[sgli...@adobeforums.com]

I'm stumped. I followed Adobe's methodology as described in the xml rules pdf, and all I get is a paragraph with all the cells run together. The table is pretty simple--it has a single header row, four columns, and five rows. I played with the tag settings until my eyes fell out, and appeal to someone to have mercy.

Here's what the exported table looks like in a browser:

Table 2-1. Special Characters in Character Classes CharacterMeaningPortabilityHow to Include It]End of classUniversalPut at the beginning of the class (or first after the negation character)[Beginning of classUniversalPut it anywhere in the class^InversionCommonPut after some other character!InversionUniversalPut after some other character-RangeUniversalPut at the beginning or end of the class
Ranges have an additional portability problem that is often overlooked, especially by English speakers. There is no guarantee that the range [a- z] matches every lowercase letter, and strictly speaking there is not even a guarantee that it matches only lowercase letters. The problem is that most people assume the ASCII character set, which defines only unaccented characters. In ASCII, the uppercase letters are contiguous, and the lowercase letters are also contiguous (but there are characters between them; [A- z] matches a few punctuation characters). However, there are UNIX- like systems on which either or both of these assumptions may be wrong. In practice, it is very nearly portable to assume that [a- z] matches 26 lowercase letters. However, accented variants of lowercase letters do not match this pattern. There is no generally portable way to match additional characters, or even to find out what they are. Scripts may be run in different environments with different character sets.

Clearly I am missing something.

What's the secret for getting something that looks like a table with rows and columns?

My company doesn't actually care about the xml--they want an InDesign chapter exported to plain html for posting on web sites.

Everything else in the chapter looks great on a web page, so if someone could help me fix this last miserable problem, I would be very grateful!