What Is the Equivalent Code If I Leave Internationalization Out

Question

I have source code for accommodating internationalization using the ResourceBundle. I do not want to use internationlization.
Here is the source code:
static final String OPTION_FILE_NAME  = "mvnplugin_mvnforum_MVNForumConfig";
static String MVNFORUM_HOME = "mvnForumHome";
static
   ResourceBundle res = ResourceBundle.getBundle(OPTION_FILE_NAME);
   MVNFORUM_HOME = res.getString("MVNFORUM_HOME").trim();
   setMVNForumHome(MVNFORUM_HOME);
}If I leave out the internationalization part, should my code be:
static String mfh = "mvnForumHome";
static String MVNFORUM_HOME;
static
   MVNFORUM_HOME = mfh.trim();
   setMVNForumHome(MVNFORUM_HOME);
}Then, I do not know what is so essential about
static final String OPTION_FILE_NAME  = "mvnplugin_mvnforum_MVNForumConfig";Any consequences if I leave this statement out?

Answer 1

Hi Natalie, maybe you need the isolationalism forum (haha, it's my sick sense of humour, don't worry).
But seriously, I recommend that you follow, JN_'s first recommendation. Make your application able to use resource bundles, but just provide one default bundle. Even if you don't think you need, or are interested in internationalization just now, it is a forward thinking way to build your applications. I don' think it adds much complecity either.
I'm also foolish enough to think that expertise in internationalizaion of software looks good on one's resume...
My recent search for a certain kind of software to use in Japan, came up with a list of about 100 vendors, none of whom were able to provide anything suitable for simple translation to Japanese... lost opportunities all round, sad...