you are right, including globalization in the design of an application, or even
more of a web-application infrastructure, makes things much simpler and
cleaner. since OACS has already been designed (cough, cough), and mostly
implemented, we'll just have to suffer through the pain of building it in after
the fact.
i built the globalization infrastructure for ACS Java, so i have some experience
with this stuff. i think we should use this thread to design and plan
(logistically) the retrofit of globalization into OACS.
i am not familiar with the globalization infrastructure in OACS currently, i know
of acs-reference, but not of its capabilities. why don't we start by cataloging
everything that is in OACS currently and how we can use it.
