we work with the Arbortext Editor 6.1 and want to copy e.g. lists from a Winword document into the xml file. With a dcf file we can control how the Editor inserts this fragments into xml.
Everything works like bold, italic and paragraphs. But in numbered lists we would like to insert the number as an attributeValue.
This is a list in Word:
If we copy this list and insert into our xml file in Arbortext Editor, we get following structure:
As you can see there is always "1." as attribute value inside the <item>-tag. This is because we have following entry in our dcf-file:
Do you have an idea, if it is possible to insert the number which is countered in word into a xml attribute with an dcf-file?
We hope you can help us. Thank you in advance for your help.
I think that you do not want the attribute "attributeValue" set for the <Item> element, as styling in the style sheet would auto-number the list automatically.
no, we do not want this as auto-number in the style. We want to get the numbering from word as the value of the attribute "numberingtext" in our element <item>.
I can't think of a way to do this by default with the Core Editor.
You would start by creating contexts for item in list with an attribute test for the role attribute in the parent (list).
This way, you can set the gentext for each type of list numbering mechanism you may use.
Then, get rid of the attributevalue defined to item in the DCF.
Now, when you paste in a list from Word, it will default to the 1. numbering, but all you need to do is change the role to one of your other definitions, and the stylesheet will update the gentext. For example, your other definitions may be A., a., I., etc
Does this sound workable?
thank you for your help. We will try your suggestion.
Did the response from Rafael assist you with resolving your issue?
If so, could you mark the response as correct, so the community knows how to resolve the issue.
If none of the responses resolved the issue, but you did resolve it, then could you add a comment about how you resolved the issue and mark it as correct?
unfortunately we still not find a solution for our issue.