Yes, you can prevent it even if my plugin can't evaluate the correct folder. This can be done by placing a translation template inside the language folder. The name of the file should be:
The files content should be the result of a fresh scan process, so only the untranslated full content should be inside. But it's also enough, if the file only contains a valid pot header like this taken from the WordPress Importer's *.pot file:
# Copyright (C) 2011 WordPress Importer
# This file is distributed under the same license as the WordPress Importer package.
"Project-Id-Version: WordPress Importer 0.5\n"
"POT-Creation-Date: 2011-07-16 15:45:12+00:00\n"
"Content-Type: text/plain; charset=UTF-8\n"
"PO-Revision-Date: 2010-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"