From: Mike Bethany <mikbe.tk@...>
Date: 2011-07-01T08:23:41+09:00
Subject: Re: A File Renamer

--0016e6480e08ea46e704a6f630a2
Content-Type: text/plain; charset=ISO-8859-1

Good point. OP would have to answer that question. The scope changes the
problem dramatically but I wonder if it's not reasonable to assume the files
will be named by humans. Once you put humans into the mix you're going to
have problems... all hail our computer overlords!


On Thu, Jun 30, 2011 at 6:51 PM, Chad Perrin <code@apotheon.net> wrote:

> On Fri, Jul 01, 2011 at 06:37:58AM +0900, Mike Bethany wrote:
> > On Thu, Jun 30, 2011 at 5:15 PM, Johnny Morrice wrote:
> > >
> > > The file name cannot be trusted any more than the meta data.
> >
> > I totally agree. Not only can people incorrectly name files but they
> > can use h4x0r l33t15h in the file names thus totally obfuscating the
> > real name. Not to mention how you will differentiate between the spam
> > parts fo the file name and the real name and the order in which they
> > come.
> >
> > I think the problem, while it *sounds* simple, is hugely complex. It's
> > a CS Master or PhD Thesis level project, not a "new to OO" kind of
> > thing.
>
> How sure are we that filenames provided by *others*, scraped from the
> Internet, are even part of the real problem domain for this case?  Maybe
> the filenames *can* be trusted for the theoretical use case we face.
>
> --
> Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
>

--0016e6480e08ea46e704a6f630a2--