I think it would be a good idea to provide a fallback for localized views.
Imagine your sourceLanguage is "en_us" and you would like to provide german views. You could place them within a "de_de" subdirectory. Someone visiting your website from austria, who might have "de_at" configured as preferred language would end up with the english default view, although the "de_de" localization might be better suited for him.
So, if a fallback existed, one could place the views under a general "de" subdirectory and everyone visiting the website with a preferred language like "de_de", "de_at", "de_ch", … would be serverd these views instead of the english ones.
I just came across that, because IE8 seems to be preconfigured with a preferred language "de" instead of "de_de" which is the one I'm using with FireFox.
You cannot trust the language preference from end users.
If you have an application supporting multiple languages, you should know what languages it supports. Then given a user language preference, you may resolve it into a known language. You should performance this process using your own procedure.
Well, the point is: 99.9% of the words might be the same in germany, austria and switzerland. so it does not make any sense to maintain different translation files for 3 regions just because of a few words. the point is, that the austrian (de_at) translation just defines a few keys and should fall back to "de" if no regional translation exists.