non ascii armor file sigs

[Jacob Perkins]

--=-tk8XY7gV/RbbG5+9Ywv9
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Should gpg be able to verify a non ascii armor detached signature?  For
example, I have a file foo.  I can make two detached sigs, one armored
(foo.asc) and the other not (foo.gpg).  gpg --verify foo.asc is fine,
but gpg --verify foo.gpg gives:
gpg: no signed data
gpg: can't hash datafile: file open error

I'm using gpgme-0.3.14 (seahorse) to do the sigs, and it will verify
both fine.
Is this normal behavior or should signatures always be armored?

--=20
Jacob Perkins <jap1@users.sourceforge.net>
seahorse

--=-tk8XY7gV/RbbG5+9Ywv9
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA992D6mq/Go6uOlQ4RAgGVAJ0WsSyf2JktH9ORsPoj/cEVfapzNwCfWLQb
9unq1x8nfkIud3oywa2gYSM=
=7qvt
-----END PGP SIGNATURE-----

--=-tk8XY7gV/RbbG5+9Ywv9--