Posted by awm on January 13, 2011 at 8:29pm
I I tested the i18n module with D7 and it is not working properly. It does not separate the content based on the language. So on the front page, regardless of the user language selection, the content that is displayed is mixed. Now there is a module called language switcher that enables drupal 7 to separate the content based on the language but it has side effects on the content administration section. Say you are on the English front page, then you click on content -> filter by language (other than English) -> the result would: "no content available".
Any thoughts?
Comments
participate development
awm086
There's a lot to do left regarding multilingual sites in D7. Early adopting drupal 7 with multilingual features will always urge you to participate in development of the i18n series module. i18n is in its first alpha which is far from stable and feature complete.
I'm watching with interest.
I'm watching with interest. At some point planning to convert Language Sections and MultiLink to D7, but really busy at the moment and don't want to spend the time until there's demand in the community. Chicken and egg, I know.
Anybody want to hazard a guess to how many multi-language D7 sites will be out there inside of 6 months? As of early January, some thirty thousand sites using i18n, only five of them on D7, and those are quite probably test sites (i18n for D7 is in alpha.)
I've got a new project to work on and would have loved to use D7. But, its multi language (dual language at least) and I think the correct decision is D6. But I'm willing to be convinced otherwise.
Currently part of the team at https://lastcallmedia.com in a senior Drupal specialist role.
I guess it depends on how soon you have to go into production
I went through the same debate over whether to do a new dual-language site in D6 or D7. I decided several times through mid-January that it had to be D6, but finally decided to go with D7. I'm happy with my decision and think that by the time the site is live the key bugs will have been worked out. But I am definitely spending a lot more of my time filing issue reports and tracking down solutions than I would be if I'd gone with D6. And if I had a stricter timeframe for the site I might have had to make a different decision. (We have the luxury of rolling out a simple site and then adding additional functionality later, so as long as I can get basic bilingual functionality working we'll be fine, and that seems very doable.)
But note that between Jan 2 and Jan 23, the number of D7 sites with i18n installed jumped from 5 to 443. The more people who are using it the faster problems will be identified and solved, so I'm getting on board.
i18n status update
Here's some update to this thread with about recent i18n development.
We've been working hard on i18n topics recently.
The i18n camp took place in berlin, thanks to Karsten Frohwein / commpress who initiated it (and thanks sponsors to support it).
http://i18nsprint.drupalevents.de
Gabor, Jose, Dereine, many others and i was there for 5 days and worked during long days on an improvement of the whole D7 multilingual story.
The quality of the collection of i18n modules reached a decent level and we're happy to be ready for the D7 future. There happened amazing improvement since D6. We're using the system now in production and are happy with it with modules like:
http://drupal.org/project/i18n
http://drupal.org/project/i18n_views
http://drupal.org/project/languageicons
http://drupal.org/project/l10n_client
http://drupal.org/project/l10n_update
Note that we have also more modern concepts than previously, like:
http://drupal.org/project/entity_translation
There's still a lot to do to make things even better and we'll continue.
Some additional aspects might be found on my (german) blog:
http://www.md-systems.ch/blog/2011-05/eine-woche-mehrsprachigkeit
Wishing you a lot of fun with your D7 ecosystem.