From: Chad Perrin <code@...>
Date: 2011-07-01T07:51:03+09:00
Subject: Re: A File Renamer

--9zSXsLTf0vkW971A
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> 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.
>=20
> 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.

--=20
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]

--9zSXsLTf0vkW971A
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)

iEYEARECAAYFAk4M+hwACgkQ9mn/Pj01uKWgjACgiAV5Ts9KJODl03OIKD3FIllA
88sAn3DdoE8VW7ErC967wRyo+g7wxCWN
=KMSk
-----END PGP SIGNATURE-----

--9zSXsLTf0vkW971A--