but there is a "little" difference between localization of an executable PSPad application and localization of HTML webpages...;-) You're right that there must be a known identificator of any text value you need to display coded in the app and corresponding declarative file like the ini you described, where the values are assigned to these identificators - but it is a common principle. If you are able to move your static html pages into generated ones like recommended PHP or ASP(X) or similar, then you could incorporate it to the scripts itself. There are frameworks that can do that, so just look for them. In the other case (you has to stay with static html) I would prefer AJAX fullfilling. First look for user language preference via JavaScript and then pick the corresponding XML language definition (you have to prepare it before) asynchronously and use it (load to right places into html).
-- Vany <http://forum.pspad.com/read.php?6,52318,52335> PSPad freeware editor http://www.pspad.com
