Re: [Radiant] Content Internationalization
He Yves Yves Dufour wrote: HI Mohit Very interesting ... how did you proceed when entering the articles and setting the different language portions ... no core modification ? (DB records) could this be managed in an extension ? Yves (erwin in brittany dialect..) The solution that I have is discussed in my posts to the mailing list ages ago. This link explains it: [1] The first concept - http://lists.radiantcms.org/pipermail/radiant/2007-September/006364.html [2] The details - http://lists.radiantcms.org/pipermail/radiant/2007-October/006881.html Let me know if you need more information. Cheers, Mohit. 3/12/2009 | 12:26 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Content Internationalization
I created an extension for handling content internationalization. I mentioned it on the mailing list earlier this week: http://lists.radiantcms.org/pipermail/radiant/2009-March/012527.html The extension provides tags like r:translator:title / r:translator:content part=main / Page parts are suffixed with the language abbreviation like such: body_de body_en sidebar_de sidebar_en The extension uses the browser's HTTP_ACCEPT_LANGUAGE to determine the language in which to render the page. Also, a session variable (session[:language]) can be set for a user to override the HTTP_ACCEPT_LANGUAGE header their browser sends. The extension's github repo ( http://github.com/peburrows/translator/tree/master ) has a README with a more extensive explanation. .phil.burrows. He Yves Yves Dufour wrote: HI Mohit Very interesting ... how did you proceed when entering the articles and setting the different language portions ... no core modification ? (DB records) could this be managed in an extension ? Yves (erwin in brittany dialect..) The solution that I have is discussed in my posts to the mailing list ages ago. This link explains it: [1] The first concept - http://lists.radiantcms.org/pipermail/radiant/2007-September/006364.html [2] The details - http://lists.radiantcms.org/pipermail/radiant/2007-October/006881.html Let me know if you need more information. Cheers, Mohit. 3/12/2009 | 12:26 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Content Internationalization
Hi Ben I discussed this issue with a friend of mine involved in many localizations (translation company)... he said exactly what you wrote. Few , actually very few sites needs a true mixin of multi-languages contents: one in which the visitor enter in english and need to get a spanish version of one article... generally, the visitor wants to choose one language and stick to it... It would be better to work on a good initial design in the default language, then buying or building admin tools that help in duplicating the default site, localizing all existing contents to another language, and deploying multi sub-domains , one for each language.. Radiant is lite and simple to use, trying to add in core multi- language capabilities will transform it into a 'refinery' ... better keep it clean, small and green adding extensions... (I have been deeply looking into the Zope/Plone CMS for a customer... an example of refinery) That's what I am going to do for my next customer : default site :en http://www.mycustomersite.com - proxy URL to http://www.mycustomersite.com/en/ duplicate to sub-domain http://fr.mycustomersite.com - proxy URL to http://www.mycustomersite.com/fr/ ,localizing the content .. and so on why not a localization extension wich will had a language bar view and manage all localization parameters erwin On 9 Mar 2009, at 22:59, Ben Still wrote: Hi Doug, We've done a number of sites now that need to cover two or three markets. I thought it might be useful to share this as it's something we've come up against a few times. I realise that you're asking about internationalisation as in having an identical page that can render in different languages. In sites we've worked on, this often also means different prices and product fact sheets etc. The easiest thing from a development perspective is having one site, then make it smart to render out the different flavour depending on URL or cookie. We've run into two issues on that. First is the customer wanting slightly different behaviour or structure on one but not the others. A few changes are manageable, but as you can imagine this can get out of control and become a bit of a nightmare of localisation hacks. The second issue is SEO and localisation. Apparently physical location is a big deal. If you want to rank well with Japanese customers, use a Japanese TLD and host out of a Japanese rather than say a US datacentre. I realise in your example the Spanish version might well be for Spanish rather than English speakers in the US- this example is for different geographic markets. So, faced with those two issues, we typically make several different sites with one code repository. We've found this much easier in the long run. Capistrano manages the updates to each site so code remains the same, but the content is separate. A bit of a drag in that the content editor has to go to different /admins, but allows for flexible changes to structure and content, as well as addressing the SEO issue. Anyway- hope that helps someone at some stage regards Ben Doug Bryant wrote: I'm currently looking at integrating radiant cms into our site. One of the requirements we have coming down the pipeline soon is internationalization. Is there a best practice anyone could suggest for internationalization of the content with Radiant? I ran across a couple of posts from May 2007 about doing this, but am checking because I don't know if this is still the suggested route. Does the rails 2.3 feature of rendering internationalization snippets change any recommendations? (:render :partial = foo would render _foo.en.html or _foo.es.html depending on current locale) http://www.mail-archive.com/radi...@lists.radiantcms.org/ msg04509.html http://www.mail-archive.com/radi...@lists.radiantcms.org/ msg04535.html What I envision is splitting out the content part of our app and integrating it into Radiant. We have someone who would then be able to translate maintain the spanish version of the website. Content does not presently change too frequently, but would it if didn't require a complete application redeploy just to update a some portion of the content. Any suggestions? All feedback is greatly appreciated. Doug === Doug Bryant doug.bry...@milemeter.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Ben Still | Red Ant | office +612 9267 8300 ext 208 | mobile 0425 294 271 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post:
Re: [Radiant] Content Internationalization
Yves Dufour wrote: Hi Ben I discussed this issue with a friend of mine involved in many localizations (translation company)... he said exactly what you wrote. Few , actually very few sites needs a true mixin of multi-languages contents: one in which the visitor enter in english and need to get a spanish version of one article... generally, the visitor wants to choose one language and stick to it... It would be better to work on a good initial design in the default language, then buying or building admin tools that help in duplicating the default site, localizing all existing contents to another language, and deploying multi sub-domains , one for each language.. Radiant is lite and simple to use, trying to add in core multi-language capabilities will transform it into a 'refinery' ... better keep it clean, small and green adding extensions... (I have been deeply looking into the Zope/Plone CMS for a customer... an example of refinery) That's what I am going to do for my next customer : default site :en http://www.mycustomersite.com - proxy URL to http://www.mycustomersite.com/en/ duplicate to sub-domain http://fr.mycustomersite.com - proxy URL to http://www.mycustomersite.com/fr/ ,localizing the content .. and so on why not a localization extension wich will had a language bar view and manage all localization parameters I just have a localization bar that only finds if the article exists in another language (based on the convention that all languages have the same slug with only a different language portion /en/article or /fr/article and so on. It is assumed that /en /fr /jp will have completely different content in my case. Essentially, it is also assumed that the language maintainers are different people. Further, not all content is available in all supported languages. The loss is that the slug will always be in a single language. I use this as demonstrated on: http://t-engine.onghu.com/en/articles/booting-t-engine-from-usb/ (thebar shows 'en' and 'th') On another page: http://t-engine.onghu.com/cn/articles/te-recommended-reading/ it shows 'cn' and 'en' and so on. Cheers, Mohit. 3/10/2009 | 4:08 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Content Internationalization
HI Mohit Very interesting ... how did you proceed when entering the articles and setting the different language portions ... no core modification ? (DB records) could this be managed in an extension ? Yves (erwin in brittany dialect..) On 10 Mar 2009, at 09:08, Mohit Sindhwani wrote: Yves Dufour wrote: Hi Ben I discussed this issue with a friend of mine involved in many localizations (translation company)... he said exactly what you wrote. Few , actually very few sites needs a true mixin of multi-languages contents: one in which the visitor enter in english and need to get a spanish version of one article... generally, the visitor wants to choose one language and stick to it... It would be better to work on a good initial design in the default language, then buying or building admin tools that help in duplicating the default site, localizing all existing contents to another language, and deploying multi sub-domains , one for each language.. Radiant is lite and simple to use, trying to add in core multi- language capabilities will transform it into a 'refinery' ... better keep it clean, small and green adding extensions... (I have been deeply looking into the Zope/Plone CMS for a customer... an example of refinery) That's what I am going to do for my next customer : default site :en http://www.mycustomersite.com - proxy URL to http://www.mycustomersite.com/en/ duplicate to sub-domain http://fr.mycustomersite.com - proxy URL to http://www.mycustomersite.com/fr/ ,localizing the content .. and so on why not a localization extension wich will had a language bar view and manage all localization parameters I just have a localization bar that only finds if the article exists in another language (based on the convention that all languages have the same slug with only a different language portion /en/article or / fr/article and so on. It is assumed that /en /fr /jp will have completely different content in my case. Essentially, it is also assumed that the language maintainers are different people. Further, not all content is available in all supported languages. The loss is that the slug will always be in a single language. I use this as demonstrated on: http://t-engine.onghu.com/en/articles/booting-t-engine-from-usb/ (thebar shows 'en' and 'th') On another page: http://t-engine.onghu.com/cn/articles/te-recommended-reading/ it shows 'cn' and 'en' and so on. Cheers, Mohit. 3/10/2009 | 4:08 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Content Internationalization
Hi Doug, We've done a number of sites now that need to cover two or three markets. I thought it might be useful to share this as it's something we've come up against a few times. I realise that you're asking about internationalisation as in having an identical page that can render in different languages. In sites we've worked on, this often also means different prices and product fact sheets etc. The easiest thing from a development perspective is having one site, then make it smart to render out the different flavour depending on URL or cookie. We've run into two issues on that. First is the customer wanting slightly different behaviour or structure on one but not the others. A few changes are manageable, but as you can imagine this can get out of control and become a bit of a nightmare of localisation hacks. The second issue is SEO and localisation. Apparently physical location is a big deal. If you want to rank well with Japanese customers, use a Japanese TLD and host out of a Japanese rather than say a US datacentre. I realise in your example the Spanish version might well be for Spanish rather than English speakers in the US- this example is for different geographic markets. So, faced with those two issues, we typically make several different sites with one code repository. We've found this much easier in the long run. Capistrano manages the updates to each site so code remains the same, but the content is separate. A bit of a drag in that the content editor has to go to different /admins, but allows for flexible changes to structure and content, as well as addressing the SEO issue. Anyway- hope that helps someone at some stage regards Ben Doug Bryant wrote: I'm currently looking at integrating radiant cms into our site. One of the requirements we have coming down the pipeline soon is internationalization. Is there a best practice anyone could suggest for internationalization of the content with Radiant? I ran across a couple of posts from May 2007 about doing this, but am checking because I don't know if this is still the suggested route. Does the rails 2.3 feature of rendering internationalization snippets change any recommendations? (:render :partial = foo would render _foo.en.html or _foo.es.html depending on current locale) http://www.mail-archive.com/radi...@lists.radiantcms.org/msg04509.html http://www.mail-archive.com/radi...@lists.radiantcms.org/msg04535.html What I envision is splitting out the content part of our app and integrating it into Radiant. We have someone who would then be able to translate maintain the spanish version of the website. Content does not presently change too frequently, but would it if didn't require a complete application redeploy just to update a some portion of the content. Any suggestions? All feedback is greatly appreciated. Doug === Doug Bryant doug.bry...@milemeter.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Ben Still | Red Ant | office +612 9267 8300 ext 208 | mobile 0425 294 271 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
