Thanks for tracking that down. On Tue, Apr 10, 2012 at 11:03:49AM -0700, Mark Diggory wrote: [snip] > I speculate heavily that reimplementing this 300 lines of code to support > JAVA ResourceBundles (either properties based or XML based) rather than > cocoons messages.xml format would get us the ability to use the same i18n > messages tags in XMLUI on the messages.properties files in dspace-api and > so-on.
Sounds good. But, considering that there is interest in an enhanced-for-translation format and XML is soooo malleable, what if we went the other way: create an XMLResourceBundle that the stock Java can just use without touching existing code? Properties.loadFromXML() could do most of the work, if we define it conformably with the Properties DTD. That is: find or invent a namespace containing elements that translation support facilities can use for all the things that translators want to do but aren't relevant to the code that uses their work, and overlay it on the Cocoon format or something like it. If we do it right, we can give that to the translation community and not have to maintain it. Or probably there is already something we can readily transform to/from the forms we need. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgpef6d9rGiuY.pgp
Description: PGP signature
------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
