cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward S" <sumi...@gmail.com>
Subject Re: 2.1.9 - Internationalization transformer (i18n)
Date Wed, 05 Mar 2008 14:15:39 GMT
thanks solprovider.
if http works, we should be able to do it.

had another question, how is the filename determined from the locale param.
eg; if the locale passed is in_ID, how does it convert internally to look
for: messages_in.xml ?


-S2.


On 3/4/08, solprovider@apache.org <solprovider@apache.org> wrote:
>
> 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 <suminub@gmail.com> 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: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>

Mime
View raw message