Free filtering software for linux

XML::Filter::Tee can send SAX events to multiple processor, with switching.

SYNOPSIS

my $t = XML::Filter::Tee->new(
{ Handler => $h0 },
{ Handler => $h1 },
{ Handler => $h2 },
...
);

## Altering the handlers list:
$t->set_handlers( $h0, $h1, $h2, $h3 );

## Controlling flow to a handler by number and by reference:
$t->disable_handler( 0 );
$t->enable_handler( 0 );

$t->disable_handler( $h0 );
$t->enable_handler( $h0 );

## Use in a SAX machine (though see L and
## L for a more convenient way to build a machine
## like this):
my $m = Machine(
[ Intake => "XML::Filter::Tee" => qw( A B ) ],
[ A => ">>log.xml" ],
[ B => *OUTPUT ],
);

XML::Filter::Tee is a SAX filter that passes each event it receives on to a list of downstream handlers.

Its like XML::Filter::SAXT in that the events are not buffered; each event is sent first to the tap, and then to the branch (this is different from XML::SAX::Dispatcher, which buffers the events). Unlike XML::Filter::SAXT, it allows its list of handlers to be reconfigured (via "set_handlers") and it allows control over which handlers are allowed to receive events. These features are designed to make XML::Filter::Tee instances more useful with SAX machines, but they to add some overhead relative to XML::Filter::SAXT.

The events are not copied, since they may be data structures that are difficult or impossibly to copy properly, like parts of a C-based DOM implementation. This means that the handlers must not alter the events or later handlers will see the alterations.

XML::Filter::Dispatcher::Compiler can compile rulesets in to code.

SYNOPSIS

use XML::Filter::Dispatcher::Compiler qw( xinline );

my $c = XML::Filter::Dispatcher::Compiler->new( ... )

my $code = $c->compile(
Package => "My::Filter",
Rules => [
a/b/c => xinline q{warn "found a/b/c"},
],
Output => "lib/My/Filter.pm", ## optional
);

Most of the options from XML::Filter::Dispatcher are accepted.

NOTE: you cannot pass code references to compile() if you want to write the $code to disk, they will not survive. If you want to eval $code, this is ok.

METHODS

xinline

Hints to X::F::D that the string is inlinable code. This is a requirement when using the compiler and is so far (v.52) ignored elswhere. In xinlined code, $self refers to the current dispatcher and $e refers to the current events data. Or you can get that yourself in $_[0] and $_[1] as in a normal SAX event handling method.

compile

Accepts options that extend and override any previously set for the duration of the compile(), including the ruleset to compile.

SyslogScan::Daemon::SpamDetector::Filter contains filter reports.

SYNOPSIS

plugin SyslogScan::Daemon::SpamDetector as sd_
sd_plugin SyslogScan::Daemon::SpamDetector::Filter status spam match SpamAssassin field relayname acceptfirst 1 accept (?:bdynamicb|badsld*b|bcableb|.dhcp.|.dyn.) deny . debug 0

SyslogScan::Daemon::SpamDetector::Filter looks at spam reported via SyslogScan::Daemon::SpamDetectors process_spam_match() function. It acts as a filter and can block reports.

This module can be used with the SyslogScan::Daemon::SpamDetector::SpamAssassin module and the SyslogScan::Daemon::SpamDetector::BlockList module to prevent too many sites from being blocked. The configuration in the "SYNOPSIS" is an example of how to do this.

CONFIGURATION PARAMETERS

The following configuration parameters are supported:

debug

Debugging on (1) or off (0).

logname

A string to prepend to debug and log output. (Default: FILTER)

status

What kind of report are we looking at? Choices are: ham, spam, or idmap. (Default: spam). When called from SyslogScan::Daemon::SpamDetector::BadAddr, the status will be badaddr.

match

What kind of match are we looking at? Each module that makes reports sets this parameter. Current choices are: SpamAssassin, Postfix, Sendmail, SpamSink, and various BadAddr::*. A regualar expression match is done on this field. No default.

field

Which field from %info will we examine with the accept and deny regular expressions? No default.

accept

What is the regular expression for passing this filter?

deny

What is the regular expression for being rejected by this filter?

acceptfirst

Check the accept expression first? (Default: 1).

Chess::PGN::Filter is a Perl extension for converting PGN files to other formats.

SYNOPSIS

use Chess::PGN::Filter;

filter(source => $pgn,filtertype => XML);
OR
my %substitutions = (
hsmyers => Myers, Hugh S (ID),
);

my @exclude = qw(
WhiteElo
BlackElo
EventDate
);

filter(
source => $pgn,
filtertype => TEXT,
substitutions => %substitutions,
nags => yes,
exclude => @exclude,
);
OR
filter(
source => $pgn,
filtertype => DOM,
);
OR
$dom = filter(
source => $pgn,
filtertype => DOM,
verbose => 0,
);

This is a typical text in one side, different text out the otherside filter module. There are as of this writing, the following supported choices:

1. XML -- Converts from .pgn to .xml using the included pgn.dtd as the validation document. This is for the most part a one to one transliteration of the PGN standard into XMLese. It does have the additional virtue of allowing positions to be encoded within the XML output. These are generated by an embedded NAG of {0} and automatically (user controlled) at the end of each game. As a kind of adjunct to the position diagrams, pgn.dtd optionally allows each move to include its FEN string. This allows scripted animation for web pages generated this information.
2. TEXT -- Although the PGN standard is widely available, many program that generate .pgn do so in an ill-formed way. This mode is an attempt to normalize away the various flaws found in the wild! This includes things like game text all on a single line without a preceding blank line. Or castling indicated with zeros rather than the letter O. There is at least one application that carefully indents the first move! The list of oddities is probably as long as the list of applications.
3. DOM -- A Document Object Model (DOM) makes for a very convenient interim form, common to all other filter types. Useful in both the design and debugging phases of filter construction. By way of self-documentation, here is an example of a single game that shows all of the obvious features of the DOM:

$VAR1 = {
Tags => {
Site => Boise (ID),
Event => Cabin Fever Open,
Round => 1,
ECO => ?,
Date => 1997.??.??,
White => Barrett Curtis,
Black => Myers Hugh S,
Result => 1-0
},
Gametext => [
{
Movenumber => 1,
Epd => rnbqkbnr/pppppppp/8/8/4P3/8/PPPP1PPP/RNBQKBNR b KQkq e3,
Movetext => e4
},
{
Movenumber => 2,
Epd => rnbqkbnr/ppp1pppp/8/3p4/4P3/8/PPPP1PPP/RNBQKBNR w KQkq d6,
Movetext => d5
},
{
Movenumber => 3,
Epd => rnbqkbnr/ppp1pppp/8/3pP3/8/8/PPPP1PPP/RNBQKBNR b KQkq -,
Movetext => e5
},
{
Movenumber => 4,
Comment => Playing ...Bf5 before closing the c8-h3 diagonal has some positive features.,
Epd => rnbqkbnr/ppp2ppp/4p3/3pP3/8/8/PPPP1PPP/RNBQKBNR w KQkq -,
Movetext => e6
},
{
Movenumber => 5,
Epd => rnbqkbnr/ppp2ppp/4p3/3pP3/3P4/8/PPP2PPP/RNBQKBNR b KQkq d3,
Movetext => d4
},
{
Movenumber => 6,
Comment => Time to think like a Frenchie - c7-c5!,
Epd => r1bqkbnr/ppp2ppp/2n1p3/3pP3/3P4/8/PPP2PPP/RNBQKBNR w KQkq -,
Movetext => Nc6,
Rav => [
{
Movenumber => 6,
Epd => rnbqkbnr/pp3ppp/4p3/2ppP3/3P4/8/PPP2PPP/RNBQKBNR w KQkq c6,
Movetext => c5
}
]
},
.
.
.
{
Movenumber => 29,
Comment => (Bxe5) Black could still kick for a while if he had played ...Bxe5.,
Epd => r1bq1rk1/2p1npb1/2n1p2P/pp1pP1p1/3P2P1/2P4Q/PP2BP2/RNB1K2R b KQ -,
Movetext => h6
}
]
};

XML::Filter::Dispatcher::AsStructHandler Perl module can help you convert SAX stream in to simple, data-oriented structure.

SYNOPSIS

## Ordinarily used via the XML::Filter::Dispatchers as_data_struct()
## built-in extension function for XPath

This SAX2 handler builds a simple hash from XML. Text from each element and attribute is stored in the hash with a key of a relative path from the root down to the current element.

The goal is to produce a usable structure as simply and quickly as possible; use XML::Simple for more sophisticated applications.

The resulting data structure has one hash per element, one scalar per attribute, and one scalar per text string in each leaf element.

Warnings are emitted if any content other than whitespace is discarded.

The root element name is discarded.

If you are using namespaces, you must pass in the Namespaces option, otherwise not. Using namespaces without a Namespaces option or vice versa will not work.

Only start_document(), start_element(), characters(), end_element(), and end_document() are provided; so all comments, processing instructions etc., are discarded.

Pod::POM::View::HTML::Filter Perl module can use filters on sections of your pod documents.

SYNOPSIS

In your POD:
Some coloured Perl code:

=begin filter perl

# now in full colour!
$A++;

=end filter

=for filter=perl $A++; # this works too

This should read C :

=begin filter foo

bar foo bar

=end filter
In your code:
my $view = Pod::POM::View::HTML::Filter->new;
$view->add(
foo => {
code => sub { my $s = shift; $s =~ s/foo/bar/gm; $s },
# other options are available
}
);

my $pom = Pod::POM->parse_file( /my/pod/file );
$pom->present($view);
/* Perl colouring styles */ .c { color: #228B22;} /* comment */ .cm { color: #000000;} /* comma */ .co { color: #000000;} /* colon */ .h { color: #CD5555; font-weight:bold;} /* here-doc-target */ .hh { color: #CD5555; font-style:italic;} /* here-doc-text */ .i { color: #00688B;} /* identifier */ .j { color: #CD5555; font-weight:bold;} /* label */ .k { color: #8B008B; font-weight:bold;} /* keyword */ .m { color: #FF0000; font-weight:bold;} /* subroutine */ .n { color: #B452CD;} /* numeric */ .p { color: #000000;} /* paren */ .pd { color: #228B22; font-style:italic;} /* pod-text */ .pu { color: #000000;} /* punctuation */ .q { color: #CD5555;} /* quote */ .s { color: #000000;} /* structure */ .sc { color: #000000;} /* semicolon */ .v { color: #B452CD;} /* v-string */ .w { color: #000000;} /* bareword */ -->
The resulting HTML will look like this (modulo the stylesheet):
# now in full colour!
$A++;
$A++; # this works too

This should read bar bar bar:

bar bar bar