Why do the plugin resource paths include the localization prefix?
Good question... As far as I know, the plugin's resource paths should not include the localization prefix. The resources are being called via PHP in the most direct way possible:

craft()-&gt;templates-&gt;includeJsResource('smartmap/js/smartmap.js');
craft()-&gt;templates-&gt;includeCssResource('smartmap/css/smartmap.css');


I'm not entirely sure, but I suspect this may be a Craft bug. I've reached out to Pixel &amp; Tonic in order to fully diagnose the problem. If the plugin code needs to be corrected, I will implement a fix as soon as we can figure out what's going on.