perl-XML-Filter-BufferText-1.01-1.22 >  A [Tp9|B "zP/1HPBi@YbϺjAo@ e 54p830>Sj5jln &~s(@.fa_5?`%f W JC \#hD2$D>0CkH_^]tK?M ].[O1VsIfV= ~25lGˑ+2`B'@>BoZ}V??27f087eb8f5eadbd81079faa25a5e4913012a7f964f5d406e8ea3d4fea1747cdacecc8f39bd96b5428873bdd0e9f2df2f5376419`[Tp9|eA0` FDTj@:ѷj^ (qV wuMa/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" ' Spt| 7=Dd t    $Tto(89:FGHIXY\] ^ b rc d e f l u v w Lx ly z     Cperl-XML-Filter-BufferText1.011.22Filter to put all characters() in one eventThis 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).[Tsheep04pSUSE Linux Enterprise 15SUSE LLC GPL-1.0+ or Artistic-1.0https://www.suse.com/Development/Libraries/Perlhttp://search.cpan.org/dist/XML-Filter-BufferText/linuxnoarch !AA$AA큤$[T[T?ڠ[T[T?l9E.G5\RpknWP2c \sr]:uSAQ)&Nx8&q_ϛ f?zZ#ճb"U!\Z^vL4d7)F$V(%T@ڪ0,a'2S.j'սo&?VOn5LMI#MMFDUI /Lj|20^aln4R$^xK(,x#]уc-zL]f"BmL#?u~Cmau5,%7ɦqX1C6EO-W$op-a";"c~bq_MjQy[-}'.'ʵKkCkcmGk5AjKv>b#s BmGX^5I: P{_pGPY c"$H˯E-Vx[T ܗ*zP۟H7%Mz\w9c`9#By Jem=D=s*j AD5"-*hMFlԿ^qdiD6]u1 0|!9/h HT{V*6w"/Aw hNrV“E4r+>iԲWvz]AgSI׉Qy00`@Lzr@្_5W: ΠEGX^֨ \Zj#uc}_$/n$A>=d~3ɉd d,-g]?''GF,X'TG|<5qФ*xWy|TqJ*CB q}8Vևp<"G}#>{8hJT B+O>t&YKV GY_Lc)e%m]CWctC¨^!cӬypeS>;&t &R K+^G=R<[hAx̒겵srvحs+CE]E< hVG4ZʔQn#\%-n"͒N!zJi* /W/$gE#~|t*d䲸_/OnU!TZ2;bvIʝ {К"+Ks8-z<16p YZ