Thank you very much for the response. Is going with separate trees for language a better option for doing i18n? I mean of course that we have the benefit of not duplicating the work in the dialogs, just in the content structure. Are there any other benefits (not only for i18n, but generally)?
Regards, Andon On Wed, Nov 11, 2009 at 9:30 AM, Jan Haderka <jan.hade...@magnolia-cms.com> wrote: > > On Tue, 2009-11-10 at 17:35 +0100, Andon Sikavica wrote: >> If I eneble the DefaultI18nContentSupport all the links are prefixed >> with the proper language code, exactly as I wanted. But, also the dms >> links to the resources are prefixed and they aren't resolved >> afterward. Any suggestions about this? > > More explanation then suggestion: You are running into: > http://jira.magnolia-cms.com/browse/MAGNOLIA-2899 > and > http://jira.magnolia-cms.com/browse/MGNLDMS-170 > > which will be both fixed in Magnolia 4.2 and DMS 1.4.1 respectively. > ... the only thing that is still open even with those fixes is if you > would like to have multiple localized versions of the binary file "per > document" (e.g. same as what the wiki explains how to do for fields in > the paragraphs). If you want to try implement such feature you would > need to update the edit dialog of the documents ... and probably do it > in some smart way so you can keep adding languages dynamically ... if > you go that way, feel free to ask for more guidance in the dev list, > specially if you think of contributing it back. > > BTW, both of the above fixes are already in the 4.2-m1 and 4.2-beta1 > releases if you want to try them out. > > Cheers, > Jan > >> >> Regards, Andon >> >> >> On Mon, Nov 9, 2009 at 12:43 PM, Jan Haderka >> <jan.hade...@magnolia-cms.com> wrote: >> > >> > OTOH if you want to achieve what is described in the wiki page you >> > mentioned in your original posting (multi lang per paragraph support), >> > you just change the i18n/content/class back to DefaultI18nContentSupport >> > and use it as described in that wiki page with one site configuration. >> > When defining multiple language locales with country codes, make sure >> > that for each defined language you have also one without the country >> > code. >> > >> > Cheers, >> > Jan >> > >> > On Fri, 2009-11-06 at 16:56 +0100, Zdenek Skodik wrote: >> >> Hi Bobi, >> >> >> >> it's the same like with STK. Every STK page is based on >> >> the same site definition (STK/config/site). With ETK you >> >> can create as much site configurations as you would like >> >> (ETK/config/site, there is a default site definition as >> >> an example). To get it working you need to register your >> >> templates/paragraphs there and just select an appropriate >> >> site definition for your site, open its Home page and >> >> click on the Page Info button. A dialog will open where >> >> you can select the site definition to use. >> >> >> >> - >> >> Best regards, >> >> >> >> Zdenek Skodik >> >> Magnolia International Ltd. >> >> >> >> Magnolia® - Simple Open-Source Content Management >> >> >> >> >> >> On Pá, 2009-11-06 at 16:09 +0100, Bozidar Ilievski wrote: >> >> > Hi. >> >> > >> >> > To enable i18n, I followed the instructions on this wiki page: >> >> > http://wiki.magnolia-cms.com/display/WIKI/Introduction+to+I18nContentSuppo >> >> > rt >> >> > >> >> > With the config/server/i18n/content/class property set to >> >> > info.magnolia.cms.i18n.DefaultI18nContentSupport, >> >> > the multi language mechanism works ok. >> >> > >> >> > Then, I installed magnolia EE 4.1.1 (with the Extended templating kit >> >> > module included). >> >> > >> >> > With the ETK module installed the property under: >> >> > Config/server/i18n/content/class >> >> > was changed to: >> >> > info.magnolia.module.extendedtemplatingkit.i18n.ETKI18nContentSupport. >> >> > >> >> > Now, if I insert the language in the URL just after the context path >> >> > (http://localhost:8080/de/home.html), I receive 404 from the server. >> >> > >> >> > So my question: how can I enable the multi language support within the >> >> > Extended templating kit module? >> >> > >> >> > Regards, >> >> > Bobi. >> >> > >> >> > ---------------------------------------------------------------- >> >> > For list details see >> >> > http://www.magnolia-cms.com/home/community/mailing-lists.html >> >> > To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> >> >> > ---------------------------------------------------------------- >> >> >> >> >> >> ---------------------------------------------------------------- >> >> For list details see >> >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> >> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> >> >> ---------------------------------------------------------------- >> > >> > >> > ---------------------------------------------------------------- >> > For list details see >> > http://www.magnolia-cms.com/home/community/mailing-lists.html >> > To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> >> > ---------------------------------------------------------------- >> > >> > >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> >> ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
