I think it's just as easy to screw up an XML file manually as it is to screw up an WDDX file manually. Let's face it... I hope that anyone staring at an XML or WDDX file is somewhat of a developer. Do you really expect the end user with no development skills at all to stare at an XML file and know what the hell it means? expect it to be human readable? With that being said, fine, I understand the purpose of it all - and always have since the first post was made. I'm playing devil's advocate here. I don't deal with i18n at all, haven't need to since my previous job. Thus... those 'newbies' on the list that are lurking and watching should take this into consideration. Do you need all the extra work, etc. or can you get away with a simple script file that's included.
Thanks,
~Todd
At 10:51 PM 3/25/2003 +0100, you wrote:
Hi,
I don't think that simple XML configuration files are overkill compared to WDDX...
Configuration files should be easily "human" readable and editable.
WDDX was not designed to be "human" readable and editable, it is way of representing and exchange complex data between web applications.
By editing a WDDX manually, you'll take the risk to corrupt the WDDX format.
As for using cfscript for i18n, this is what we were using in our CF5-based application.
The problem is that anyone could break the application by inserting "bad" characters in the cfscript variable definitions or by forgetting the ; at the end of the line...
Usually i18n bundle files are not translated by developers.
You won't have any risks with .properties files (which are just plain .txt files).
Benoit Hediard
www.benorama.com
Todd Rafferty ([EMAIL PROTECTED]) - http://www.web-rat.com/
Team Macromedia Volunteer for ColdFusion
http://www.macromedia.com/support/forums/team_macromedia/
http://www.devmx.com/
