Hi Richard >Deciding all requirements before beginning implementation would definitely >be best, but unfortunately this idea ignores reality - in reality customers >decide things too late, or make changes to their decisions after >implementation has begun. OK, usually I see people going multi-language in a later phase having only one language initially, so at least then one would be bound to migrate the content after having a translation bureau fully translating the content. Having usually the 'native' language first, having it as fallback later, is quite simple in the current way things work.
>Migrating existing content (some installations will have 10000s of nodes, with >100000s of properties) is both a pain, and asking for trouble. Maybe a simple Groovy task could fix the migration, could probably be packed with the default admin-central? >If a site goes from multi-language to single-language, there is no need to >remove multi-language completely, you can just remove all languages except >one from the configuration. So you still need to enable the i18n, but you couldn't completely disable it again then, right? And what if you start-out without i18n enabled? Kind regards Marco -- 15 Years of Excellence - http://netcetera.com Marco Glur | [email protected] T +41 44 247 79 20 Netcetera AG | 8040 Zurich | Switzerland | http://netcetera.com >-----Original Message----- >From: [email protected] [mailto:user-list- >[email protected]] On Behalf Of Unger, Richard >Sent: Montag, 3. Oktober 2011 13:54 >To: Magnolia User-List >Subject: AW: AW: [magnolia-user] Troubles with i18n node wrapper > > >Hi Marco! > >Deciding all requirements before beginning implementation would definitely >be best, but unfortunately this idea ignores reality - in reality customers >decide things too late, or make changes to their decisions after >implementation has begun. > >Migrating existing content (some installations will have 10000s of nodes, with >100000s of properties) is both a pain, and asking for trouble. > >If a site goes from multi-language to single-language, there is no need to >remove multi-language completely, you can just remove all languages except >one from the configuration. > >Regards from Vienna, > >Richard > >-----Ursprüngliche Nachricht----- >Von: [email protected] [mailto:user-list-owner@magnolia- >cms.com] Im Auftrag von Marco Glur >Gesendet: Montag, 03. Oktober 2011 13:17 >An: 'Magnolia User-List' >Betreff: RE: AW: [magnolia-user] Troubles with i18n node wrapper > > >In my opinion it should be transparent for i18n support to work according the >well-known java message-resources pattern (no suffix in name=fallback) and >most stable, of course, respecting existing code. > >Maybe valid migration path could be to >a) rename all existing 'base' values that are i18n with the suffix according to >the old fallback language >b) then rename all suffixed from the new fallback language to have no suffix > >The default behavior is anyways not to have Multilanguage, so no need to >reference a certain language in the node-data names with a suffix. >The decision which is the fallback/default locale should instead be taken at the >most early point of setting up a new CMS. > >Another obstacle having a default-suffixing always would be: >How should it work still, when once you remove Multilanguage support for a >site completely, need to migrate the node-datas manually, then? > >I wouldn't see any change of concept here in future. > >Kind regards > >Marco > >-- >15 Years of Excellence - http://netcetera.com > >Marco Glur | [email protected] >T +41 44 247 79 20 >Netcetera AG | 8040 Zurich | Switzerland | http://netcetera.com > > > >---------------------------------------------------------------- >For list details see >http://www.magnolia-cms.com/community/mailing-lists.html >To unsubscribe, E-mail to: <[email protected]> >---------------------------------------------------------------- > > > > > >---------------------------------------------------------------- >For list details see >http://www.magnolia-cms.com/community/mailing-lists.html >To unsubscribe, E-mail to: <[email protected]> >---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
