What is a proper way for naming of message properties in i18n?

Question

We do have a website which should be translate into different languages. Some of the wording is in message properties files ready for translation. I want now add the rest of the text into these files.

What is a good way to name the text blocks?

<view>.<type>.<name> 

We mostly have webpages and some of the elements/modules are repeating on some sites.

Answer 1

As far as I know, no "standard" exists. Therefore it is pretty hard to tell what is proper and what is improper way of naming resource keys. However, based on my experience, I could recommend this way:

property file name: <module>.properties resource keys: <view or dialog>[.<sub-context>].<control-type>.<name> 

We may discuss if it is proper way to put every strings from one module into one property files - probably it could be right if updates doesn't happen often and there are not so many messages. Otherwise you might think about one file per view.

As for key naming strategy: it is important for the Translator (sounds like film with honorable governor Arnold S. isn't it?) to have a Context. Translation may actually depend on it, i.e. in Polish you would translate a message in a different way if it is page/dialog/whatever title and in totally different way if it is text on a button.

One example of such resource key could be:

preferences.password_area.label.username=User name 

It gives enough hints to the Translator about what it actually is, which could result in correct translation...