On Mon, 2009-11-16 at 13:29 +0100, Matteo Pelucco wrote: > Jan Haderka ha scritto: > > um, what part of "the mechanism" doesn't work? > > Try to explain what you wanted to achieve and what you did to get it and > > how it "didn't work" ... maybe we can find out what the problem is. > > OK, let me explain. > > 1) I enable i18n on magnolia instance: > > <config> > cserver / i18n / content / class = > info.magnolia.module.extendedtemplatingkit.i18n.ETKI18nContentSupport > server / i18n / content / enabled = true > > 2) add italian language support and fallback > server / i18n / content / fallbackLocale = it > server / i18n / content / locales / it (new node, copied from en with > changed locale ND) > > 3) go back on a page (the page alread has title and title_en > nodeDatas... ) and call it with > > A) http://host:port/context/it/path-to-page.html --> white page > B) http://host:port/context/en/path-to-page.html --> white page > C) http://host:port/context/path-to-page.html --> page in italian > > I expected to see page title in english (B) and italian (A). C is ok. > > My questions are: > > 1) What I missed?
The ETKI18nContentSupport doesn't work that way. As I mentioned earlier, it is site based instead. So the extra element you need to configure there is one site definition per language (and set that language in given site definition) and then maintain multiple trees of content (one per language) So what you end up with is: /casa_pagina (set to use site: default_it) /home_page (set up to use site: default_en) Underneath you can then use exactly same elements like calendar etc. and they will automatically use the proper language. So to do what you want (have a multiple lang. support _per_paragraph_ ) you need to use DefaultI18nContentSupport instead (I believe I mentioned it in my earlier mail as well, but maybe it was not clear enough) > 2) A site in ETK can be multilanguage? So that I can have UNDER THE SAME > website TREE all the localized versions of a site? Yet again, no, you can't. You can use ETK and DefaultI18nContentSupport to achieve what you want, but you can't use ETKI18nContentSupport to do this. ETKI18ContentSupport is there to solve a bit different problem. What you want is already handled by the DefaultI18ContentSupport. Seems like many more people are lately interested in the multiple langs per paragraph support or its just much more unclear then having different langs in different trees. To figure out which one it is, can you people please vote at http://poll.pollcode.com/zhrV Thanks, Jan > > Thansk for your help. > Matteo > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
