great...thanks once again.
-Ed.
On 3/5/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> "How is the filename determined from the locale param eg; if the
> locale is "in_ID", how does it convert internally to look for:
> messages_in.xml?"
>
> Magic!
>
> Programming to parse "language_countryCode_variant", concatenate
> {location} + {each variation of the locale} + ".xml", and test for
> each possible file is easy. The important information is that you do
> not need to program this function because the i18nTransformer already
> handles it.
>
> If the catalogue "name" attribute is "xxx", the i18nTransformer will
> check:
> xxx_in_ID.xml
> xxx_in.xml
> xxx.xml (default)
>
> See the "Usage" section of:
>
> http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/transformation/I18nTransformer.html
>
> The "name" attribute is the file prefix before the locale/language
> identifiers.
> The "location" attributes specify the directories to check without
> specifying the filename.
> Your location attribute might specify
> http://example.com/documentum/i18nfiles/";.
> The documents in that folder need to follow the i18n file-naming
> format to distinguish the locales/languages/default catalogs.
>
> solprovider
>
> On 3/5/08, Edward S <[EMAIL PROTECTED]> wrote:
> > 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, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 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 <[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]
>
>
