Hi Fred,
and thank you for pointing out this.
We actually have this issue with more than one LHF Fonts and we try to fix them one by one. The family name shown on our site is in most cases read from an existing binary font file. There are many cases (10ths) of LHF fonts having this issue: Either they refer to a font which doesn't exist on LHF site, or the font exist but it's slightly different one! We haven't spotted the source of this problem (it happens only with LHF fonts) so the only solution is to fix them one by one, when somebody spots the difference and tell us about it.
Thanks again!