Upayavira <[EMAIL PROTECTED]> wrote:
>
> Out of curiosity, why did you need a custom LocaleAction?
Because default action and such pipeline:
<map:match pattern="somecontent">
<map:generate src="content/{../language}/somecontent.xml"/>
does not allow to control language parameters easyly.
If I had a couple of content files in such parrarel directory
structure:
content/pl/somecontent.xml
content/en/somecontent.xml
content/de/somecontent.xml
I need an action that I'm able to configure with:
a) an array of available languages
b) site default language, when {language} is not within a)
I suppose such logic is possible to be done with a little
help of directory generator and probably some xsl filter,
but I like better simplier solutions :)
--
Tomasz Nowak
Netventure, http://www.netventure.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
