Nadia,



At 02:25 PM 5/2/2005, you wrote:
I think I found the solution all by my little self.



I changed the key to:



<xsl:key name="p"
match="node()[following-sibling::processing-instruction('xm-insertion_mark_end')]"

use="generate-id(preceding-sibling::processing-instruction('xm-insertion_mark_start')[1])"/>



and the "apply-templates" to...

That's grand but I don't think it'll work. (Sorry I'm not able to dig 
deeper today.)



The new key definition is effectively the same as the old one, except it 
only matches nodes followed by an insertion_mark_end. So in this case:



<?xm-insertion_mark_start?>
<a/>
<b/>
<?xm-insertion_mark_end?>
<c/>
<?xm-insertion_mark_start?>
<d/>
<e/>
<?xm-insertion_mark_end?>

The 'c' node is included with the group including <a/> and <b/> (since like 
them it does indeed have a following-sibling insertion_mark_end, just not 
the same one).



This, at least, is going to mess you up.



(I see other things that probably won't work as expected, but they are 
tortuous to explain.)



Accordingly, I'd *at least* recommend stress-testing this against a few 
"pathological" cases so you know what you're getting into.



Cheers,
Wendell


======================================================================
Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================