Ard Schrijvers <a.schrijvers <at> hippo.nl> writes: > I18n is actually mapping from key to value, so you could easily use i18n for > what you want.
I think you talk on cross purposes here. An XML catalogue is for mapping ids to different resources; most commonly used for mapping public identifier like "//W3C//DTD XHTML 1.0 Transitional//EN" to different system ids like "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";. An XML parser would be forced to load this DTD from the remote site while with an XML catalogue you can point it to the local version of the file. Cocoon comes itself with a lot of catalogue stuff [1]. I remember somebody else reported a problem with the resolving against the catalogue or source resolving in general inside XSLT a while ago. I'd consider it as a bug in Cocoon anyway. Unfortunately I never worked that low level with the XML stuff (JAXP). Joerg [1] http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/ src/webapp/WEB-INF/entities/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
