perl-XML-Filter-BufferText-1.01-1.22 >
A [Tp9|B"zP/1HPBi@YbϺjAo@
e54p830>Sj5jln
&~s(@.fa_5?`%f
WJC
\#hD2$D>0CkH_^]tK?M].[O1VsIfV= ~25lGˑ+2`B'@>BoZ}V??27f087eb8f5eadbd81079faa25a5e4913012a7f9 64f5d406e8ea3d4fea1747cdacecc8f39bd96b5428873bdd0e9f2df2f5376419 ` [Tp9| eA0` FDTj@:ѷj^(qVwuMa/N`Gh]T(6b+4Yג7~ %G!`Rq/+QPgDRzL3icl_s5)+ɼS.YL~fQy\]!US)0㑧E8դXOC1o9qD`,/Y-7ޑxl5ag,k=G^;1?BUEI8^zp^6ƔqܱI > p >
? d " ' S p t | 7 = D d t
$ T t o ( 8 9 : F G H I X Y \ ] ^ b
r c d e f l u v w L x l y z C perl-XML-Filter-BufferText 1.01 1.22 Filter to put all characters() in one event This is a very simple filter. One common cause of grief (and programmer
error) is that XML parsers aren't required to provide character events in
one chunk. They can, but are not forced to, and most don't. This filter
does the trivial but oft-repeated task of putting all characters into a
single event.
Note that this won't help you cases such as:
blah phubar
In the above case, given the interleaving comment, there will be two
'character()' events. This may be worked around in the future if there is
demand for it.
An interesting way to use this filter, instead of telling users to use it,
is to return it from your handler's constructor, already configured and
all. That'll make the buffering totally transparent to them
('XML::SAX::Writer' does that). [Tsheep04 pSUSE Linux Enterprise 15 SUSE LLC