key specification by word match does not work as expected

[Hauke Laging]

Hello,

ijust read this in the man page:

###########################
By word match.
All  words  must  match exactly (not case sensitive) but can appear in any  
order in the user ID or a subjects name.  Words are any sequences of letters, 
digits, the underscore and all characters with bit 7 set.

+Heinrich Heine duesseldorf
###########################

So I tried:

start cmd:> gpg --list-keys ="Hauke Laging <hauke at laging.de>"
pub   1024D/0xECCB5814 2005-09-05
uid         [ uneing.] Hauke Laging <hauke at laging.de>
[...]

BUT:
start cmd:> LC_ALL=C gpg --list-keys +"Hauke Laging"
gpg: error reading key: No public key

Right before sending this mail I noticed that it is the quotes:

start cmd:> gpg --list-keys +Hauke Laging
pub   1024D/0xECCB5814 2005-09-05
uid         [ uneing.] Hauke Laging <hauke at laging.de>
[...]

I find this strange because non-quoting of arguments is generally unusual. 
Furthermore key selection can occur in the options part of the command line 
though I admit that word match is probably mostly used for finding a key 
instead of for specifying it in another command.

Next step of insight:
Leaving out the quotes does not solve that problem but makes it worse:
+Hauke Laging
without quotes is not understood by gpg as "Find all UIDs which contain the 
words 'Hauke' and 'Laging'" but as an OR relation of "Find all UIDs that 
contain Laging" and whatever.

Even stranger:
start cmd:> gpg --list-keys +lalala Laging
works (finds all the UIDs with "Laging") but doesn't the other way round:

start cmd:> LC_ALL=C gpg --list-keys lalala +Laging
gpg: error reading key: No public key

start cmd:> LC_ALL=C gpg --list-keys +Hauke
gpg: error reading key: No public key


Hauke
-- 
☺
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 555 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20120927/c0024f2d/attachment-0001.pgp>