Hello Alessandro, If you distinguish your content hierarchically, why would you need different extractors? Normally, when we have multiple languages, and it is seperated by structure, all you need, is to account for it in the frontend you are using.
If you have multiple languages within one document, you can take a look at [1] Regards Ard [1] http://www.hippocms.org/display/CMS/Hippo+Repository+ConfigurableXMLCont entExtractor > > I'm adding multi-language in an existing site. > The site was built with Hippo CMS and Hippo repository. > > I'm focusing on the repository: > > The original structure contains only this branch: > > /default/files/default.preview/content/nl > > and I've just added a new English branch > > /default/files/default.preview/content/en > > The actual extractors index all the content because is like this: > <extractor > classname="nl.hippo.slide.extractor.HippoSimpleXmlExtractor" > uri="/files" content-type="text/xml"> > > The attribute uri="/files" is too generic therefore the > property like this: > > <instruction property="title" namespace="http://hippo.nl/cms/1.0"; > xpath="/document/content/general-item/title"/> > > contains english and dutch element. > > Moreover, I found in indexer.xml several <property> that use > org.apache.lucene.analysis.nl.DutchAnalyzer. > > Hope someone can help me with some tips on multi-languages repository. > > Thanks in advance > > Alessandro > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
