non ascii armor file sigs

[Jacob Perkins]

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?

-- 
Jacob Perkins <jap1 at users.sourceforge.net>
seahorse
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : /pipermail/attachments/20021211/3f1abef0/attachment.bin