From: SourceForge.net <no...@so...> - 2004-01-31 00:00:16
|
Feature Requests item #636513, was opened at 2002-11-11 09:01 Message generated for change (Comment added) made by kal_ahmed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391882&aid=636513&group_id=27895 Category: None Group: None >Status: Closed Priority: 5 Submitted By: Kal Ahmed (kal_ahmed) >Assigned to: Kal Ahmed (kal_ahmed) Summary: Improve export "roundtripping" Initial Comment: When importing XTM syntax, <topicRef> and <subjectIndicatorRefs> get converted to a "blank" topic with a resourceLocator and a "blank" topic with a subjectIndicator respectively. Currently XTMWriter exports these blank topics and generates internal <topicRef> elements wherever they are referenced. Add an option to XTMWriter to turn the internal topic refs to blank topics into either external <topicRef> or <subjectIndicatorRef> elements at the point(s) where those topics are referenced. ---------------------------------------------------------------------- >Comment By: Kal Ahmed (kal_ahmed) Date: 2004-01-31 00:00 Message: Logged In: YES user_id=176992 Can now control the way such "stub" topics are written. If the property http://www.tm4j.org/tm4j/xtmwriter/writestubtopics is set to true, then the stub topics are written as <topic> elements (and the references as internal <topicRef>s, otherwise the references are written as either <subjectIndicatorRef> or <topicRef> elements and the stub topics are not written out. The default value of this property is "true", because the filtering of stub topics adds processing overhead. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391882&aid=636513&group_id=27895 |