I can file a separate issue if this is too off-topic, but how would the configurable rules UI handle a language where words are modified according to gender?
For example, with my horrible Spanish language skills, I know that it's standard to sometimes say un/una depending on the gender of the item.
In the case of "Joe submitted [un/una] [node type]," I'm not sure that the current system would handle the gender change. I suppose a lightweight solution in this case could be to say un(a) -- I would like to see how systems like Facebook handle this case.
One option is to have a token for un/una that is evaluated based on the target type.
Comments
Comment #1
IceCreamYou CreditAttribution: IceCreamYou commentedFor your example, you could use the PHP input evaluator if you're comfortable with that sort of thing, or you could create separate Rules for different gendered node types.
A little bit more difficult situation is for a message like "You followed Joe." In a language where you would need a gender-specific pronoun to describe Joe, you have to have a profile option for users' gender in order to correctly construct that sentence. In a case where you don't have that option or a user hasn't filled it out (or has selected an option other than "male" or "female") there is no satisfactory solution. Most translations will usually just default to the male pronoun.