I have the exact same issue.. What did you decide for your problem?
I'm trying to decide now what the best approach is. Two of my options were
exactly the ones you describe to improve your design, but the one that I
currently have is a template, which looks like this:
var someData= {
My application's supposed to support both English,Simpilify
Chinese,Traditional Chinese,and even Vietnamese. The great I18N feature of
Wicket helps me solve many i18n problems.
The only remains is how to do i18n of javascript.
Due to the initial design, we put some of messages in the .js file,like
We use approach 1. We do not pull messages from Wicket resources, they
are just static in the file. The link to the correct js file is however
created by a dynamic component that uses the current Locale.
You could go with approach 2, but to me it sounds like a lot of work.
Regards,
Erik.
