{actors} token has only singular

Currently ACTORS mean these 10 phrases (no one has NUM context possibility): http://www.geni.com/tr8n/phrases?section_key=&search={actors}&a...

Seconding Lauri's request, this issue is very relevant in the Swedish translations as well.

The {actors} token can also be controlled by the list contextual rule. You need to turn it on in the language administrator tools, unless I'm misunderstanding you.

Private User - we can't add missing context rules (like count/num) to {actors} even via language administration page...

SOLVED!

Language Manager shall activate List Rules for your language at Language Management Page and all problems for "actors" and "targets" are solved.
Best example:
{targets} received gifts from {actors}
will give 4 different phrases:
actors contains one element and targets contains one element
actors contains one element and targets contains at least two elements
actors contains at least two elements and targets contains one element
actors contains at least two elements and targets contains at least two elements

Any tokens that end in "actors", "targets" or "list" are considered as list based tokens and will have an option for context rules. So all these would be list tokens: {actors}, {targets}, {user_list}, {family_list}... and many other tokens...

As you mentioned, the context rules are configured by the language managers. In different language the rules will be different. For example, in Russian, we only need the following 4 rules:

1. one element - is male
2. one element - is female
3. one element - has an unknown gender
4. at least two elements

But in Hebrew, this may go to a more complicated scenario as the sentence translation may depend on the genders of the users in the list:

1. one element - is male
2. one element - is female
3. one element - has an unknown gender
4. at least two elements - all male
5. at least two elements - all female
6. at least two elements - mixed genders

Some language managers decided to make their language rules simpler and always treat unknown genders as males. You could do it, if your language allows for it. All you have to do, is modify the rules to say:

1. one element - is female
2. one element - is not female
3. at least two elements

Well, same concept applies to the gender rule, which is by default is based on 3 options (male, female, unknown), but you could make it into two options.

Hope this makes sense.