I'm creating a xwiki-based system where lots of textual metadata in custom metadata
objects is systematically going to be attached to pages - which are going to be counted in
thousands. When I create a page translation the metadata objects come along - which is
desired - but I am not able to translate the object properties for the language in
question separately. I had to be able to do that too.
Does that mean that I either have to create the metadata classes for every possible
language and attach them to translated pages accordingly or that I for example have to add
an identifying language property for those classes and attach to a page as many instances
of those classes as there are translations for a page? Is there possibly a better way to
accomplish this?
The system I'm creating is btw going to be a translation database and in this case I
would consider it much more usable if the attached objects were dynamically instantiated
for the page translations in question.
Otherwise 1.0b seems so far just great from this point of view!
Thanks in advance for your information!
Petteri
Show replies by date
Good questions!
About the dynamic instantiation, isn't it the default behaviour when you
follow the wizard and create template and sheet for the class?
-----Original Message-----
From: petteri.karttunen(a)kuopionkonservatorio.fi
[mailto:petteri.karttunen@kuopionkonservatorio.fi]
Sent: January 8, 2007 4:40 PM
To: xwiki-users(a)objectweb.org
Subject: [xwiki-users] Object properties' translations
I'm creating a xwiki-based system where lots of textual metadata in
custom metadata objects is systematically going to be attached to pages
- which are going to be counted in thousands. When I create a page
translation the metadata objects come along - which is desired - but I
am not able to translate the object properties for the language in
question separately. I had to be able to do that too.
Does that mean that I either have to create the metadata classes for
every possible language and attach them to translated pages accordingly
or that I for example have to add an identifying language property for
those classes and attach to a page as many instances of those classes as
there are translations for a page? Is there possibly a better way to
accomplish this?
The system I'm creating is btw going to be a translation database and in
this case I would consider it much more usable if the attached objects
were dynamically instantiated for the page translations in question.
Otherwise 1.0b seems so far just great from this point of view! Thanks
in advance for your information!
Petteri