Submission guidelines not translateable

This works for me. Possibly related I couldn't translate the form string above the help. Luckily, I just hid that field and used the help field as the title.

The documentation for t() indicates that user content should not pass through t():

You should never use t() to translate variables, such as calling

t($text); 

, unless the text that the variable holds has been passed through t() elsewhere (e.g., $text is one of several translated literal strings in an array). It is especially important never to call

t($user_text); 

, where $user_text is some text that a user entered - doing that can lead to cross-site scripting and other security problems.

In this case, the string goes through filter xss admin which prevents JavaScript from being entered as a translation or as a user value.

Does t() really circumvent admin_xss_filter()?

As far as I can tell, since the string passes through filter_xss_admin(), its safe to use t() function in this case.

There are lines of code not 3 lines below this one where user text is run through t(); Perhaps we should fix both?

I'm familiar with the code for a Drupal global variable translation, but this is a local function variable only used to temporarily store a string for output. So, I'm not sure how to approach translating that if not the t(); function.

To fix this would have to check module_exists for entity_translation and module_exists for the tid approach to translation and then check to see which version of translation is being used by the node then load the translated node through tid if it's the tid approach or load the entity translation by the current interface language if it's the entity_translation approach just prior to the "['content']['help'] code in function formblock_get_block($type)

this way you'd not have to use the t function at all.