The "location" attribute should specify a Source -- any protocol should work. (See my recent post about discovering which protocols are valid.) So the catalogue definitions could include: location="http://example.com/catalog_en.xml"; (website) location="cocoon://translation/catalog_en.xml" (Cocoon root pipeline) location="documentum://catalog_en.xml" (if you write a DocumentumSourceFactory -- currently imaginary.)
HTH, solprovider On 3/4/08, Edward S <[EMAIL PROTECTED]> wrote: > had a quick question on the internationalization transformer. > Currently, it reads the catalog from the files stored in a directory under > the webapp. (translations folder) ...and this is configured using the > location attribute/element. > > My question is, is it possible to read this...using a URL to some other > website or a url that is actually another cocoon call? > if not, then whats the best way to do it? > > we were thinkin of keeping all the translation files in documentum instead > of a folder in the webapp. > thanks > Ed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
