While agree it would be easier to maintain and to translate if we reduced the keys, however for several reasons I don't want to re-factor that right now.
While it is true that many features use the same labels for update and cancel buttons, they are different buttons in different places and I don't rule out the possibility that in some cultures it may be desireable to translate them differently in different places due to their usage context. If we combine them then its easier to maintain but this is no longer possible.
Sometime in the near future I plan some other re-factoring that will also require re-factoring resource files. What I plan to do is make it possible to have a minimal installation of mojoportal with no features except the html module. To do that I will first be creating a set of projects:
mojoPortal.Features.Data (5 versions)
then I will move the poll and survey into those projects and implement the missing data layers for those features
after that I will move most of the other features like Blog, Forums, Links etc out of the main projects and into this set of projects. At that time my plan is to re-factor the resources into per feature files like BlogResources.resx, ForumResources.Resx etc
So, for the time being I would prefer if you can just tranlsate them as they are. You can sort them by value and update all the same values with the same transalation.