The i18n Transformer looks good for dealing with internationalization,
however...

I am very confused regarding HOW i get the appropriate country_locale
parameters passed dynamically?
I am reading the "Cocoon developers handbook" which samples do not seem to
work with cocoon 2.1.4.
I configure sitemap with:

<map:transformer name="i18n"
src="org.apache.cocoon.transformation.I18nTransformer">
     <catalogue-name>messages</catalogue-name>
     <catalogue-location>translations</catalogue-location>
     <untranslated-text>untranslated</untranslated-text>
     <cache-at-startup>true</cache-at-startup>
</map:transformer>

then add it to pipeline:

<map:match pattern="*">
        <map:generate src="blah/{1}.xml"/>
         <map:transform type="i18n"/>
         <map:serialize/>
</map:match>

In this book it's stated that adding the request parameter of
"?locale=fr_ca" should display the appropriate translation automatically,
but it does not function this way as far as i can see. (and yes - I do have
the correct xmlns in my source doc, and messages/translations set up
correctly)

I do not see anything here that deals with sending through the locale /
country based on the users browser setting or OS settings... Help!

Thank You all Cocoon users for your feedback.

Dean West

----- Original Message -----
From: "Joerg Heinicke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 10, 2004 5:07 PM
Subject: Re: Cocoon and Internationalization


> On 10.05.2004 21:55, Dean West wrote:
>
> > I have been tasked with internationalization for the company I work for,
and
> > since we already use Cocoon in our current appliction - I am thinking
that
> > the "I18n Transformer" should do the job?
> >
> > I like the concept of the I18n Transformer because it seperates the
> > different langues into their own source XML documents... this SEEMS to
be
> > way more efficient than having 1 xml source doc with a plethora of
> > "xml:lang" tags for each language translation.
> >
> > Can anyone offer their expertise on this subject (best practices)?  - it
> > just seems really heavy on the xml engine to have to parse huge xml
files
> > (containing all language translations).
>
> Yes, you should use multiple files. They offer as additional value the
> fallback from the language_country_variant to language_country to
> language to default if a key is missing in the more detailed variant.
> Did you read the documentation on I18nTransformer? I think it explains
> the details very well:
> http://cocoon.apache.org/2.1/userdocs/transformers/i18n-transformer.html
> The documentation on the wiki can probably not add much more, but the
> URL is: http://wiki.cocoondev.org/Wiki.jsp?page=I18NTransformer
>
> Joerg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to