#134 XTMWriter writes invalid baseName markup

[Ichiro Furusato]

The content model in XTM 1.0 for <baseName> is
(scope?,baseNameString,variant*), but the current
XTMWriter code is putting the baseNameString after the
variants, not before them.

This is a simple fix in XTMWriter of moving the
writeBaseNameString() method call from endBaseName() to
the end of the startBaseName() method.

[Ichiro Furusato]

Logged In: YES
user_id=1641765
Originator: YES

Not such a simple fix after all. It seems that rather than closing off an open <baseName> upon receiving the event for a variant, it's creating a new <baseName> and putting the <variant> in that. Because the latter doesn't have a <baseNameString> of its own, the element is invalid. This might be happening in the tree walker.