cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: Internationalization
Date Fri, 06 Oct 2000 13:23:28 GMT
I think the features of java.text.MessageFormat can handle most if not
all of theses issues. The additional dynamic features that may be
required when translating to a new language are essentially related to
the expression of plural.

Maybe we should model the arguments of MessageFormat as XML whith the
help of the xml:lang attribute ?

Something like :
  <text xml:lang="fr">Sur le disque "{1}", il {0,choice,0#n'y a aucun
fichier|1#y a un fichier|1#y a {0,number,integer} fichiers}.</text>
  <text xml:lang="en">There {0,choice,0#are no files|1#is one file|1#are
{0,number,integer} files} on disk "{1}"</text>

This implementation puts all translations in a single source file. If
you prefer to have one dictionary file per language, maybe we could use
XLink references ?

Another additional idea : with C2, we could pre-filter each multilingual
file into serveral monolingual files, thus avoiding the overhead of
applying the translation transformer a each request.

My .02 euro.


Peter Verhage a écrit :
> Conny Krappatsch wrote:
> > In english one would say: We are a {team} of {4}.
> > In german you say: Wir sind ein {4}er-{team}.
> Problem is you can't always know this before you make it... Maybe for a
> few languages, but when you add a new language, it still can be
> different from the above, so then you have to make some more elements
> dynamic for example... Then you still have to edit the original page to
> make it a little more dynamically... :/ What I mean to say is that you
> should not have to point to the dynamic elements of the text. But if you
> would not, it's a lot more difficult to implement, I know... I don't
> know if there is a perfect way to do it..
> Peter
> --
> Peter Verhage       <>
> BV - information technology
> -  0118 41 50 54

View raw message