Thanks for the fix.
I cannot agree with your opinion that it is easier to translate the single file.
The idea is how the translation is being performed.
If the translation is performed by copying the english file and translating all the strings in it one-by-one without looking at the pages they are present on - of course, you are right. But in my opinion it's really impossible to produce accurate translation of the page in such a way.
When I perform the translation I do the following. I open 2 browser windows: with the original and the translated variants of the page. I look at the page and think how to translate these strings in the context of this particular page to make the whole translation accurate. After that I find the specified string in the resource file and enter the translated version.
In this case it's much easier to find the string in the small file than to find it in a big one.
It's also easier not to forget any help or error messages not visible by default - as the file is much smaller, I can see that there are some untranslated strings on this form easier.
Plus, when using separate files:
1. Issues like naming convention violation mentioned above become impossible because of no need of this naming convention.
2. If you do not see the string in the short file you can be sure it is not stored in resources - now I need to find all such strings in the big file and make sure they belong to other pages (because of the possibility of naming convention to be violated).
3. It's easier to translate separate feature modules without translating the whole portal (if I do not need all the modules). If I write my own feature module, I can provide some translations to it without violating the portal translation convention. It's also easier to see if some new modules are not translated at all.
It's all my IMHO. :)