How to Install and Uninstall perl-XML-Filter-BufferText Package on openSUSE Leap

Last updated: November 23,2024

1. Install "perl-XML-Filter-BufferText" package

This guide covers the steps necessary to install perl-XML-Filter-BufferText on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-XML-Filter-BufferText
            
                    
    
    Copied

2. Uninstall "perl-XML-Filter-BufferText" package

This tutorial shows how to uninstall perl-XML-Filter-BufferText on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-XML-Filter-BufferText
            
                    
    
    Copied

3. Information about the perl-XML-Filter-BufferText package on openSUSE Leap

Information for package perl-XML-Filter-BufferText:
---------------------------------------------------
Repository : Main Repository
Name : perl-XML-Filter-BufferText
Version : 1.01-1.22
Arch : noarch
Vendor : SUSE LLC
Installed Size : 5.4 KiB
Installed : No
Status : not installed
Source package : perl-XML-Filter-BufferText-1.01-1.22.src
Upstream URL : http://search.cpan.org/dist/XML-Filter-BufferText/
Summary : Filter to put all characters() in one event
Description :
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).