I purposely didn't add any multi-lingual support into reactor. I don't think its reactor's responsibility.
You're right on that, I agree - I may have been a bit hasty to suggest otherwise.
My plans for i18n was to add content keys into the xml, rather than the actual message. For example:
<teacherId>
<label>TeacherIdLabel</label>
<comment>TeacherIdComment</label>
<notProvided>TecherIdNotProvided</notProvided>
.. etc..
</teacherId>
You can still use the Dictionary.getValue("teacherId.label") to get this key, which you can pass to whatever you use for internationalization.
Yes, but... that seems a bit too "heavy" for me...
More thoughts? Keep em' commin'.
How about a system similar to Java resource bundles: calling getDictionary with an optional parameter to specify the locale would get you the content of a xml file with the specified locale as extension/part of the name/... No parameter? Then you get the (current) default... That way, you don't break the current practice, yet allow for extension where necessary.
Keep up the good work (worrying about i18n is nitpicking, I know)
Wouter
Keep up the good work (worrying about i18n is nitpicking, I know)
Wouter
-- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
