29 Sep
2011
29 Sep
'11
2:25 a.m.
On 09/28/2011 04:09 AM, Gerritjan Koekkoek wrote:
As I understand, to internationalize I can use
workaround as described on page advised by Vincent;
Op 28 sep. 2011, om 09:51 heeft Vincent Massol het volgende geschreven:
Yes.
On Sep 28, 2011, at 9:45 AM, Thomas Mortagne wrote:
I have one page and for each language I add a object (having a language code field
in attribute) (mutiple objects on ONE page(?)) On Wed, Sep 28, 2011 at 9:29 AM, Gerritjan
Koekkoek
<gerritjankoekkoek(a)gmail.com> wrote:
See also documentation at
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica…
And especially:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica…
Hi,
I'm trying some basic functionality on a multilanguage Wiki (3.1)
I create a class
I create the default Class sheet and add a object on it (like suggested in the default)
I create the default Class template and add a object on it (like suggested in the
default)
Then I create a object;
It creates a page containing the object, I use the inline form editor to enter some data
and save.
Now I want to create a translation in another language?
How should I do that?
Translation is not supported for objects unfortunately. See
http://jira.xwiki.org/browse/XWIKI-69. In the sheet I have display code that selects the
object based on context (language code) in browser
Yes.
What should I do to also get 'natural' results
in livetable and lucene search
So when context is language 'nl' both only will look at objects with language
attibute set to 'nl'
For the livetable you'd have to use a custom result generator.
For lucene, it's more complex. Normally if you search for a Dutch word,
you shouldn't hit English words that often, so the filtering happens
naturally. If you want a perfect index, you'd have to patch the Lucene
plugin to index things differently, either as different Lucene
Documents, one for each language, or put the text extracted from the
objects in different fields (right now they're all put in the full text
content field), and customize the query parser to search in only one of
these fields at a time, depending on the context language.
>
> Thanks
> -Vincent
>
>>> The inline form editor does not have a "translate option", when I
create a translation with the wiki editor i'm probably
>>> create a new wiki document with a different language, but it seems to point
to the SAME object. when I change the content of the object in the other language, these
changes also show when I navigate back to the english page
>>>
>>> It looks like I should instantiate a new object of the class, but then the
page language is still 'en'
>>> And how do we manage then that these objects still relate to each other? If I
change the english version of a record this should be related to the content of the
translations!
>>>
>>> Gerritjan
--
Sergiu Dumitriu
http://purl.org/net/sergiu/