[Tm4j-developers] [ tm4j-Bugs-1596060 ] XTMWriter writes invalid baseName markup

[SourceForge.net <no...@so...>]

Bugs item #1596060, was opened at 2006-11-14 04:19
Message generated for change (Comment added) made by ifurusato
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=391879&aid=1596060&group_id=27895

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Utilities
Group: TM4J 0.9.7
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ichiro Furusato (ifurusato)
Assigned to: Nobody/Anonymous (nobody)
Summary: XTMWriter writes invalid baseName markup

Initial Comment:
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.


----------------------------------------------------------------------

>Comment By: Ichiro Furusato (ifurusato)
Date: 2006-11-15 02:51

Message:
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.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=391879&aid=1596060&group_id=27895