Hi, sorry for bothering you again,
I tried to use the first solution proposed by Grzegorz, thinking it
could help with a user whose first locale is not one proposed by my
site to fallback to an existing locale :
2007/2/14, Grzegorz Kossakowski <[EMAIL PROTECTED]>:
<map:match pattern="**/images/*.gif">
<map:match type="i18n"
pattern="{system-property:site.home}/images/{2}_*.gif">
<map:read mime-type="image/gif" src="{source}"/>
</map:match>
</map:match>
I didn't forgot to add the <negotiate>true</negociate> tags in the
matcher configuration.
Yet, cocoon doesn't try to match different local to an existing
ressource but instead use the first locale and generate a "ressource
not found" error in the server log.
Was I right to suppose that this methode could fall back to the second
or third or any subsequent locale if no ressource was found with the
first locale(s) ?
Is there a workarround for that problem, because a user with a non
supported locale will see a *realy* ugly site with no picture and some
randoms texts and background colors without understanding what the
site is about ?
Thanks again and have a good day,
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
