You have set up a website where multilanguage content submission and display was a requirement? What was the workflow specified by the customer? How were relations between different languages defined? Did you have all content translated? Was translation into specific languages a requirement for publication? Did you translate all navigation and even site level images? What was special about that project?

An internationalization use case consists of the requirements you faced, the user workflow you needed to support, and the interface you provided to the user. We are not interested in dirty implementation details (modules, PHP code, CSS) at this stage, only higher level information about how you built up multilingual content, interface, navigation and site design. You don't even need to talk about Drupal projects. If you have any other use cases to share, which you experienced out of Drupal, we are interested. The goal of the above questions are only to start you up, don't let them stop you from sharing your story in greater detail.

You can either post a new story to this group or comment on this story with your use case. Thanks for sharing!

As part of our voyage to build up a solid base for Drupal core i18n, it is important to see, how other systems approach this problem. Maybe you have used some other system which has incredible i18n capabilities, or you have heard of one? Tell us the story, or just post a link to this system (as a comment), which we should learn from. I plan on setting up some of those you suggest (those that seem like the most valuable in this field), and write up my experiences, as well as the workflows, capabilities, features we can learn from.

I have started some "step-by-step" handbooks on running drupal on alternative databases (those that are non-standard-drupal).
So far, I have just started Oracle. When I have time, I will try and do the MS SQL one also. I'd love some crituqes on getting this polished off and included in the Drupal.org handbooks.

http://eb3it.com/oracle_handbook

At the Events 2.0 presentation DWW took notes during the session. Most of the presentation was to provide context for the Revised Event Spec – published here earlier.

Huge shout out to DWW for taking such detailed notes - I've gone through and tried to edit a bit so that people who were not there would have a little more context - DWW - if I've screwed something up please don't hesitate to point it out....

Drivers for Events 2.0 -

There is not a lot of functionality within the Drupal modules around Events.
Some of the modules don't “play well with others” and are not being maintained

Direction Forward:

CCK
Signup
RSVP
SendMail
Workflow
Actions

I'm working on having this new DrupalCon in Barcelona, next September 2007. So here it is this new group which I hope it will help me out.

The dates I'm working on are the 20th, 21st and 22nd of September 2007 which will give us some time to look around, go to the beach.... Any firsts thoughts on this?

French and Dutch have been added to groups.drupal.org so you can now browse this site using those languages. Many thanks to everyone who is helping. All the languages we have now installed are the following:

English
Brazilian Portuguese
Catalan
Danish
Dutch
French
German

These are the only languages we have in the 4.7 branch of the cvs for the organic groups module. If you want this site be 'your language' aware, please translate the .po file for og and I will be able to add it.

Besides that, keep working on the translation of all the other modules and submit your changes to the cvs. None of the languages we are using here cover more than a 60% of the drupal strings! If you want to help with this job, look for your language in http://drupal.org/project/Translations and contact the translation coordinator.

What?

A few days ago, I compiled a list of all the node review modules I could find at the time, and wrote up an article comparing them: http://www.lullabot.com/articles/a_review_of_node_review_modules. The amount of overlap in these modules is, quite frankly, stunning. Yet they all do slightly different things. Node Review handles multiple axes. Simple Vote merely stores the aggregate score for a node. User Review allows you to place a comment with your vote. Vote Up/Down handles a simple "yes/no" style of voting.

It occurred to me that if we took a step back, we might be able to develop "one voting module to rule them all." Rather than having to keep implementing these new voting modules because others "almost" do what we want but not quite.

I've looked briefly at customvote.module, which looks as though it endeavors to be that tool. But I'm thinking something slightly different: a voting API field for CCK.

Since part of the purpose of this group is to track views development, I thought I would share my solution for creating flexible date range arguments for the Date module.

Creating arguments for date fields is hard because there are so many possible ways people might want to use them. You may need to find a full date or a part of a date or you may want to look for a date + duration or maybe specify that the duration will start on the current date or some other date, etc. etc. In creating arguments for dates I have been finding that the list of arguments in views gets longer and longer, but no matter how many you create, someone will always come back and ask for another type of argument.

The new form API has some terrific features for Ecommerce. Specifically, I think the checkoutapi can be fully removed. In its place, we do one form with #multistep = TRUE. Default ecommerce will have a couple pages in that form just like we do today. Contrib modules that want to hook into checkout do so with hook_form_alter(). Seems cleaner IMO.

There are probably other opportunities, but that one jumps to mind first.