Support alternative translation files layouts

I know the documentation [1] is pretty clear on the directory layout that is necessary for Launchpad to automatically import translations from branches. However, it happens pretty often (more and more I should say) that I find a project that could benefit from Launchpad translations, but that don't comply with Launchpad's requirement, and I'm not that enthusiast to have to ask a project to change it's internal structure to fit to LP. This is usually a pretty weird way to introduce you to a new project (i.e. people you don't know):

======== START SAMPLE EMAIL ========

Hi, I see your project is looking for new translations!
I would like to propose to help you reach more translators by setting up your project on Launchpad. However, you will have to change the following :
Move all your .po files that are currently like this:
www/locale/nl_NL/LC_MESSAGES/django.po

to the base of your www/locale directory, and change the name of the .po file to contain the language name, like this:
www/locale/nl.po

You also need to have the translation template in the same directory, like this:
www/locale/<PROJECTNAME>.pot

Hope you can manage to do those changes!
Please tell me if you'd need help to perform those steps, I'd be more than happy to help you.

======== END SAMPLE EMAIL ========

I am pretty convinced that the LP infrastructure would be able to adapt to this kind of structure. I don't know if it is Django-specific, but it would be nice if the discussion about supporting alternative directory structures could be had (if it hasn't already?)

In this structure, you have the same metadata than in a flat structure, you know they are for language nl_NL (keep only letters before the underscore if needed), and all the languages are in the folder that's "../.." relative to the first "LC_MESSAGES" you encounter when scanning the branch. And if the problem is to export the .po files, I suppose adding a field in the LP database to store where to export the .po file back could be an possibility.

I am sure you smart guys can find a way to make this work, if you really want it ;) It would help get more projects on LP, more translations and thus more translators, potentially for other projects. The reason why I'm bringing this up is that I really like the translation platform you've built, and the incredible community of translators that's around it. Improving it to support additional project structures would be a nice step forward!

Please take a minute and think of this. It doesn't need to happen in the next version, I'd already be happy if you could discuss it in your next development cycle kick-off meeting!

Thanks!

[1] https://help.launchpad.net/Translations/YourProject/ImportPolicy?action=show&redirect=Translations%2FImportPolicy#Sample%20directory%20layout