Hello again,
I've had several looks at Text::Filter, and I've decided not to base my
module on it – it's almost exactly orthogonal, so deriving from it would
gain very little but add a dependency.
I'm going with Text::Lossy again; thanks again though.
I'm building a distribution out of this, using ExtUtils::MakeMaker. I'm
including a (Unix-filter-like) script which applies this module to given
texts. However, I wouldn't want to require everyone who installs the
module to also install the script.
How can I best handle this? Make it accessible to everyone while not
adding it to "installed exe-files"? So far, I'm including the script in
the manifest, inside a "script" directory, but don't have it as part of
Makefile.PL.
Thanks for inputs,
Ben Deutsch
On 12/20/2012 04:26 AM, Brian Katzung wrote:
Ben,
How about creating Text::Filter::LowerCase and Text::Filter::Unpunctuate
as derived classes of Text::Filter?
- Brian
On 2012-12-19 13:56, Ben Deutsch wrote:
Hello,
I'm writing a small module to apply "lossy" filters to text, to enable
better subsequent lossless compression. For example, "Hello, World!"
would become "hello, world!" with the "lowercase" filter, or "Hello
World" with the punctuation removal filter. This does not apply the
actual compression, it just reduces the entropy of the text in question.
As a working title, I'm using
Text::Lossy
as the module name. But "Text" is quite a large and well-known
top-level namespace, so I'm asking if this is a good fit, and if not,
what I might call the module instead.
One thing I do *not* want to do is place it in the "Acme" namespace –
the module may sound a bit silly, but it strives to do exactly what it
says on the tin: every filter reduces the entropy while still
retaining most of the meaning. For example, reducing the entire text
to the empty string (while great for compression) is straight out.
Thanks for your time,
Ben Deutsch
