From: ptkwt@... (Phil Tomson) Date: 2004-04-27T04:24:08+09:00 Subject: Re: Approaches to localization? In article , Peter C. Verhage wrote: >> Does this seem like a reasonable approach? >> Has anyone used alternate approaches? > >It does sound very heavy to me. In the Java world the widely used method >for localization is storing strings in simple properties files (or in >simple classes). I think they are even more easy to understand than XML >and far more lightweight. An example could be the following: > >buttonlabels.next=Next-> >buttonlabels.cancel=Cancel >etc. > >As you can see, you can create the same kind of hierarchy (as you did >using XML) using the above dot notation. > This is an interesting idea, however, I can't assume that the customer will have people who know Ruby in the future when I'm gone. Currently, I'm the only one in the group who does Ruby and I'm developing this particular app on my own. While I am supposed to do some training to bring others up to speed, it may not come before the budget axe falls (something rumored to be hanging over our heads). So if they've got this XML file that can be edited that's probably a big advantage over having them go through the Ruby code. Also, with the XML file approach all of these strings are in one location and they're easy to find when it comes time for them to edit. Phil