|
Rank: Member
Joined: 9/18/2017 Posts: 10 Location: Sweden
|
Source xml-fragment: <legend> <deflist> <term>1.</term> <def>Target A</def> <term>2.</term> <def>Target B</def> <term>3.</term> <def>Target D</def> </deflist> </legend>
Target xml-fragment: <legend> <definitionList> <definitionListItem> <listItemTerm>1.</listItemTerm> <listItemDefinition> <para>Target A</para> </listItemDefinition> </definitionListItem> <definitionListItem> <listItemTerm>2.</listItemTerm> <listItemDefinition> <para>Target B</para> </listItemDefinition> </definitionListItem> <definitionListItem> <listItemTerm>3.</listItemTerm> <listItemDefinition> <para>Target D</para> </listItemDefinition> </definitionListItem> </definitionList> </legend>
Since I have no element to connect to my parent element "definitionListItem", I get into some problems. One element containing all listItemTerms is created when I do not connect anything, but that is not the desired structure. Can I achieve this in MapForce or do I have to write this directly in xslt?
|
|
Rank: Advanced Member
Joined: 12/13/2005 Posts: 2,856 Location: Mauritius
|
Yes, you can do this using the new MapForce feature which allows accessing nodes by name. vlad attached the following image(s):
|
|
Rank: Member
Joined: 9/18/2017 Posts: 10 Location: Sweden
|
Thank you - worked like a charm :-)
|
|
Rank: Newbie
Joined: 9/28/2017 Posts: 6 Location: Germany
|
Hey Gibson335,
are you working on a S1000D Mapping?
|
|
Rank: Member
Joined: 9/18/2017 Posts: 10 Location: Sweden
|
Yes it is. Sorry for the late reply, but my PC just got the better of me for a while...
|
|
Rank: Newbie
Joined: 9/28/2017 Posts: 6 Location: Germany
|
Gibson335 wrote:Yes it is. Sorry for the late reply, but my PC just got the better of me for a while...
Great,
I´m going to open a new thread for this, because in this forum there are no private messages and it is also good to find more people working on the same problems. I think we could profit from each other.
|
|
guest |