Problem w/ languages - "und" in fields w/ "translated" nodes

I've run into some problems w/ the field being added as "und" (as marked as translatable => FALSE) and the language-detection throughout wf_field.inc relies the node's language which is a *clear* bug.

Reverting the code to 'und' is fairly easy, but could break BC; plus making this field translatable, could allow for concurrent workflows in different languages.

Haven't been able w/ D7.8 to have language-specific wf_fields attached (changing translatable => TRUE etc. hasn't shown any effect).