Name:           perl-Encode-ZapCP1252
Version:        0.33
Release:        1%{?dist}
Summary:        Encode::ZapCP1252 Perl module
License:        GPL+ or Artistic
Group:          Development/Libraries
URL:            http://search.cpan.org/dist/Encode-ZapCP1252/
Source0:        http://www.cpan.org/authors/id/D/DW/DWHEELER/Encode-ZapCP1252-%{version}.tar.gz
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch:      noarch
BuildRequires:  perl >= 0:5.006002
BuildRequires:  perl(Module::Build)
BuildRequires:  perl(Test::More) >= 0.17
BuildRequires:  perl(Test::Pod) >= 1.41
Requires:       perl(Test::Pod) >= 1.41
Requires:       perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version))

%description
Have you ever been processing a Web form submit, assuming that the incoming
text was encoded in ISO-8859-1 (Latin-1), only to end up with a bunch of
junk because someone pasted in content from Microsoft Word? Well, this is
because Microsoft uses a superset of the Latin-1 encoding called "Windows
Western" or "CP1252". So mostly things will come out right, but a few things--
like curly quotes, m-dashes, ellipses, and the like--will not. The
differences are well-known; you see a nice chart at documenting the
differences on [Wikipedia](http://en.wikipedia.org/wiki/Windows-1252).

%prep
%setup -q -n Encode-ZapCP1252-%{version}

%build
%{__perl} Build.PL installdirs=vendor
./Build

%install
rm -rf $RPM_BUILD_ROOT

./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;

%{_fixperms} $RPM_BUILD_ROOT/*

%check
./Build test

%clean
rm -rf $RPM_BUILD_ROOT

%files
%defattr(-,root,root,-)
%doc Changes META.json README
%{perl_vendorlib}/*
%{_mandir}/man3/*

%changelog
* Tue Feb 07 2012 Dave Cross <dave@mag-sol.com> 0.33-1
- Specfile autogenerated by cpanspec 1.78.