I don't know if this is being considered, but 1) Classlib has lots of java internationalization needs, and some native internationalization needs
2) DRLVM has lots of native internationalization needs, and some java needs (kernel classes). So it seems clear to me we need to at least try for a common approach. geir Salikh Zakirov wrote: > Andrew Zhang wrote: >> Vladimir Gorr wrote: >>> namely, ICU4C or >>> LOG4CXX or combination of them. > > log4cxx is already used in DRLVM. It does not provide localization services. > >> If only for i18n, icu4c is prefered. > > So, would the following solution be acceptable to all? > > 1 mark the localizable strings with _() in .cpp files > 2 write a tool to extract localizable messages from .cpp files > and autogenerate ICU4C .txt resource bundles. > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
