In the "in body" insertion mode, shouldn't the "eod-of-file token"
case have a special handling of "if the current node is a plaintext
element" and not generate a parse error in this case?

The current behavior is that if you use <plaintext>, you'll have a
parse error at EOF. Is this intended?

-- 
Thomas Broyer

Reply via email to