You would need to add file I/O error handling, and perhaps handle cases of missing tags. I assumed an input file named data. I assumed that the value inside <h1>...</h1> was used in the file name, because there is no reference to 'test' in the file, and perhaps you meant 'text' instead. But despite the caveats, this does something like you wanted: 

#! /usr/bin/perl -w
use strict;

my $text;
if (open INPUT, '<data')
{
  local $/;
  $text = <INPUT>;
  close INPUT;
}

while ($text =~ /<\?split \?>(.*?)(?=<\?split \?>)/sg)
{
  my $fragment = $1;
  my ($h1) = $fragment =~ /<h1>(.*?)<\/h1>/is;
  my ($from, $to) = $fragment =~ /<no>(.*?)<\/no>/isg;

  if (open OUTPUT, ">${h1}-nr${from}to${to}.xml")
  {
    print OUTPUT $fragment;
    close OUTPUT;
  }
}

exit 0;

[download]

In reply to Re: Splitting XML file on Processing Instructions by pbeckingham
in thread Splitting XML file on Processing Instructions by Wappel

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.