[xsl] MSXML w:p tag causing problems

Subject: [xsl] MSXML w:p tag causing problems
From: Andy Carr1 <CARRA@xxxxxxxxxx>
Date: Tue, 20 Feb 2007 12:25:40 +0000

I am constantly running into problems caused by the w:p MSXML Tag. The 
problem is that Word treats every text entry as a w:p and does not 
distinguish between Headers, Lists and any other type of textual entry... 
which is reeeaaally annoying.

When there are a number of list items in Word you get something like this:

      <w:pStyle w:val="ListTextStyle" />
         <wx:t wx:val="1." />
         <wx:font wx:val="Times New Roman" />
      <w:t>Some text</w:t>
      <w:pStyle w:val="ListTextStyle" />
         <wx:t wx:val="2." />
         <wx:font wx:val="Times New Roman" />
      <w:t>Some more text</w:t>
</w:p>    ... and so on ..

Now my problem is I need to group these type of lists under a single 
<List> tag so I would get something like this:

   <ListItem>Some text</ListItem>
   <ListItem>Some more text</ListItem>

In theory I could use the <xsl: for-each-group> function to do the job, 
but the added complication is that I am already using this function to 
group another w:p tag further up the node tree which is a Heading and the 
w:p list items are children of this Heading.

The <xsl:for-each-group> used for the Heading, processes it children by 
<xsl:apply-templates select="current-group" /> and I only want to create 
the <List> tag once for the first w:p list item but not for successive 

So I can't find a way of solving this problem without creating a <List> 
tag for every w:p list item.

Can anyone help......PLEASE...


Andy Carr
IT Specialist
Tel: Internal - 298037 External - 01252 558037
Mail Point  M1C IBM Application Services
Meudon House, Meudon Avenue, Farnborough, GU14 7NB
(Notes) Andy Carr1/UK/IBM@IBMGB 

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Current Thread