Module development and code questions

I'm trying to understand how to create a moderation queue that is content-type and category aware.

My problem is that I'm a number of 'editors' each in charge of moderating a section of the site.
When a story tagged with a term is submitted I'd like it to be moderated by the editor in charge of
moderating that term. I want to have only one user role for editors and I'd like to have a simple UI to
associate users to terms and content types. Moreover since these editors can change often, I'd like
to have one role with permission to update this list.

The work-flow should be:
- a contributor submit a story associated with a term that is not-published and in moderation by default
- an email is sent via the action module to the editor(s) associated with this content type and term
- by using the modr8 module, the editor associated with this term has access to the moderation
queue containing this particular story
- the story is approved, and email is sent via the action module to the author, the story status is changed
to publish.

I'm thinking of writings a small module to implement this UI and then use the ACL module to change
permissions accordingly (basically a node in moderation should only be visible to a specific group of
users/editors).

My question:
- Is this a good way of attaching this problem ?

i wrote a node . Now i want to grant permission for 2 group. Except Administrator ,user in group A has 2 rights : create,write,view,delete . user in group B can only view.
How can i do it ?

It is my understanding that the i18 contrib module is going to become part of Drupal core starting with version 6 or 7. (Someone please tell me if this is not the case.)

For those of us using (or who, like myself, are about to start using) the current i18 contrib module, is it safe to assume that there will be a fairly smooth upgrade from Drupal 5 with i18 (as a contrib mod) to Drupal 6 (with i18 in core)?

Hi there,
I don't know if there's some kind of this module yet which I imagine:

I have a plant-related drupal in progress and wished to have this feature:
Users should be able to create a new type of content, i.e. called 'plant file'.
There they should have several fields (to edit them and add new ones in the admin panel would be useful): name, origin, water, etc. and every user should be able to add a picture of this plant (is it dangerous to save masses of pics in the 'files'-folder?). Automatic node aliases like http://example.org/drupalpath/plant/latin_name appreciated. In the end, no plant should there be twice and single fields not filled in yet should offer the opportunity to add sth. afterwards (those which are already filled not, only the admin should edit these), but multiple line fields like in a wiki should be editable for users all the time. Also users should have a possibility to check a plant, then it should be displayed in the profile as "my plants" and in a favourite-plant-checkbox they can check what's shown in the profile under favourite plants. And then (I'm megalomaniac) in the profile should be displayed how much plants a user has added, how much fields of whatsoever he/she has edited or added and how much / which pics he/she has contributed.

Maybe there's a nice module yet or the right combination makes it possible.

Thanks for any ideas! :D

I've noticed that for some reason IE submits forms on my drupal site twice. It's horrible because some nodes created with this browser are automatically created twice! User registration form is submitted twice and drupal tries to create two accounts for one form submit!
Any ideas how to prevent this? can this be my theme's issue that automatically replaces submit buttons with images?

for form submission i use combination of html and javascript - this is because funny drupal behavior that checks the value of submit button :/
so my submit button-images look like this:

The new aggreagator gives me stuff like this: 'Big' and 'Little':

Is there any way I can fix that?