This does seem more like a localisation error, and as such, I reported it over at the Localization forum (however (un)necessary it might be).

Perhaps /one/ of these venues will get the message through! :]