cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mato Mira, Fernando" <Fernando.Matom...@dialog.com>
Subject RE: multiple catalogue search
Date Thu, 05 Jun 2003 07:09:22 GMT
> -----Original Message-----
> From: Konstantin Piroumian [mailto:kpiroumian@apache.org]
> Sent: Thursday, June 05, 2003 7:40 AM
> To: cocoon-dev@xml.apache.org
> Subject: Re: multiple catalogue search
> 
> 
> From: "Mato Mira, Fernando" <Fernando.Matomira@dialog.com>
> > > From: Christian Haul [mailto:haul@dvs1.informatik.tu-darmstadt.de]
> > >
> > > On 04.Jun.2003 -- 01:36 PM, Mato Mira, Fernando wrote:
> > > > Hello,
> > > >
> > > >   Continuing with my work on customization, I'd like to be
> > > able to search
> > > > multiple catalogs,
> > > > so if the customized web name is "foo" I'd like to be 
> able to do:
> > > >
> > > > 1. search translation in appropriate file of 
> "messages_foo" catalog
> > > > hierarchy
> > > > 2. If no entry is found, search translation in 
> appropriate file of
> > > > "messages" catalog hierarchy
> > > >
> > > > Even more than two catalogs hierarchies could be used, to
> > > accomodate for
> > > > domain-specific jargon, eg:
> > > >
> > > > 1. search messages_novartis hierarchy
> > > > 2. search messages_biochemical hierarchy
> > > > 3. search messages hierarchy
> > >
> > > If you were using InputModules for the look up (unfortunately, you
> > > don't tell us how / what you search and what happens with 
> the result),
> > > you could create a new instance of the ChainMetaModule with an
> > > arbitrary number of other modules ie. XMLFileModules each one
> > > associated with one XML file for lookup. The first module that
> > > contains a value for the key will be used, otherwise the list is
> > > searched in the given order.
> >
> > I thought it was clear this was an I18nTransformer issue.
> >
> 
> Don't quite understand what does it mean e.g. messages_biochemical
> hierarchy, but if you want to use multiple catalogs and 
> search for a message
> one-by-one then you should take a look at i18n transformer 
> configuration in
> i18n samples. Not sure that it is what you are looking for, 
> but thanks to
> Bruno now we can have one default and several other 
> catalogues used with the
> same pipeline.

I don't want to search messages one by one, I want to transform a whole
document like this (I used the term hierarchy as in the documentation):

1. Find one catalog among
   message_novartis_language_country_variant.xml
   message_novartis_language_country.xml
   message_novartis_language.xml
   message_novartis.xml (I wouldn't use this so as not to mix languages)

   and search

2. If key not found, find one catalog among
   message_biochemical_language_country_variant.xml
   message_biochemical_language_country.xml
   message_biochemical_language.xml
   message_biochemical.xml (I wouldn't use this so as not to mix languages)

   and search

3. If key not found, find one catalog among
   message_language_country_variant.xml
   message_language_country.xml
   message_language.xml
   message.xml 

   and search


Of course the ideal would be:

Search existing message catalogs until a hit found:
   message_novartis_language_country_variant.xml
   message_biochemical_language_country_variant.xml
   message_language_country_variant.xml
   message_novartis_language_country.xml
   message_biochemical_language_country.xml
   message_language_country.xml
   message_novartis_language.xml
   message_biochemical_language.xml
   message_language.xml
   message_novartis.xml
   message_biochemical.xml 
   message.xml 

   

Mime
View raw message