With i18 internationalization Workflow Actions adds ALL translations to queue also!!

That said, nodequeue doesn't know anything about translations; if they have different nids, then to nodequeue, they are different nodes. This is NOT an easy thing to 'fix' either, as it requires nodequeue to become very intimate with translations.

This isn't really a bug, it's just that the two modules don't know enough about each other to interact properly.

I believe that it would be correct to say that translations of a node are different nodes. Whether they should be queued... that's a different issue which is being discussed elsewhere (#264138: Show language of node in queue view , #251092: Multilingual Support ). Can we mark this as a duplicate and focus on the other issues?

Gonna close this because there's an i18n nodequeue thing out... if I'm wrong then re-open it.