AW: i18n

Hi Pierre,

thank you very much for the help. I think conf/client/resources is a
good neutral place for the resource files.
I translated messages with keys already existing for crud, navigate and
register
and send them as zip file.

A policy for property key names would certainly be usefull.
One way could be to have a shortname for each application/model/class
that is defined in an Interface with only static final names, implemented by
classes that use the messages. This would centralize the messagekeys for the
application.

Uta

-----Ursprüngliche Nachricht-----
Von: keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org
[mailto:keelgroup-keelframework.com-admin-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org]Im
Auftrag von Raoul Pierre
Gesendet: Dienstag, 26. Juli 2005 17:11
An: developers-6VIttnCrOeJXNEnpj1eHPNi2O/[email protected]
Betreff: Re: [Keelgroup] i18n


Uta,

>I am using a keel setup with cocoon and it works all well. Now
>I would like to intgrate the latest version of crud from the CVS HEAD
>to use the i18n features. To use this I had to migrate to the maven
>build system and I tried to build crud with maven jar. It gives me
>a set of compilation errors complaining about the getMessage function
>not found. How can I get hold of the latest crud version?
>
>
You need to updated dependencies with keel-core as the getMessage
functions are defined in StandardLogEnabledModel and
ThreadedLogEnabledModel.

>I translated the Messages in Struts to German Resource bundle for crud.
>Has anybody got experience how to bind this to cocoon?
>
>
Can't help about Cocoon.

But I think that conf/client/struts is not the right place to put the
properties files. I'd prefer something more neutral like
conf/client/resources. Any comments?

>How can I commit the translated file to the keel project?
>
>
If you send them to me, I'll do it. Did you translate only messages
already with key or did you add new keys?

Other point: what about a policy for property key names? There is some
specific keel rules about first part of them (schema name with dot for
entity metadata). But I think it would be usefull to use some common rules.

Note: next week I hope to begun transfer treatment of dynamic messages
from StrutsClientConnector to AbstractWebappClientConnector.

Pierre