Posted by boris mann on September 21, 2006 at 3:23pm
We had a discussion as part of GovCamp talking about multi-lingual issues and needs for Drupal.
- Dries: review core patches
- Dev Seed: set up demo, coders corner
- Dev Seed: tell stories about situations we've been in -- site recipes, scenarios, use cases
- Dev Seed: can make bandwidth to lead i18n
- Boris: Google hand waving
- Bart: write up a spec of requirements...in English and Dutch
Categories: action items, multi-lingual, translations
Comments
I think we should first
I think we should first collect, evaluate, and categorize a set of use cases for i18n. Part of the confrontation around i18n is IMHO due to the fact that we can't agree on each others use cases. This in turn is again partially due to the fact we don't fully understand other people's use cases.
It would be nice to have a big chart where the use cases are broken up into small pieces and we can see which use case will require the same items.
Afterwards we should have a clearer vision on where to start implementing this.
Having listened to Jose's
Having listened to Jose's talk and even more the questions which were asked afterwards I firmly believe that this is the most important thing to do: Collect requirements and try to get most people to agree on a useful set of them that can be tackled first. Some of the requirements seemed a bit obscure too.
I also think it is important
I also think it is important to gather enough information so the requirements could be set.
I have little experience with Drupal but i already tried to set up a multilinguel site... with not much succes. I have severall cases that i can write down and contribute but how can i give the cases to the community? How can i "post" them?
You could simply post them
You could simply post them here or create an issue on drupal.org and attach them.
Looks like...
...the next Montreal meetup will have some folks working on this.
Is there a particular format that would be helpful? Any existing use cases for something else we could take a look at and shamelessly steal...er, borrow from? ;)
I'll see what i can do
I work together with Bart on the specs... i'll see what i can do to create a usefull use case so you guys can take a look at it...