[Plugin: Global Translator] GT translates main, category, archive pages but not posts

Tags pages are fine too. Posts still untranslated.

From the log:

2010-05-29 19:00:25 [from: 66.249.65.251|Mozilla/5.0] – gltr_get_page_content :: Connecting to engine for url:***
2010-05-29 19:00:25 [from: 66.249.65.251|Mozilla/5.0] – gltr_clean_url_to_translate :: [REWRITEON] self url:*** | url_to_translate:***
2010-05-29 19:00:25 [from: 66.249.65.251|Mozilla/5.0] – gltr_is_connection_allowed :: Allowing connection request: delta=931 secs
2010-05-29 19:00:26 [from: 66.249.65.251|Mozilla/5.0] – gltr_patch_translation_url :: Google Patched: https://translate.google.com/translate_p?hl=en&sl=en&tl=vi&u=***&usg=ALkJrhjj0PhvdLrvyoE-H4JaR8uvF7gmKA
2010-05-29 19:00:31 [from: 66.249.65.251|Mozilla/5.0] – Bad translated content for url: ***

‘Bad translated content’. This is what happens any time it attempts to translate a ‘post’. The translated effort is in the log as well and it looks okay. The main difference between the ‘bad’ one and a ‘good’ one from the cache is that the ‘bad’ one alternates <span> tags of source language and target language – for every sentence of the article.

Is the issue that GT doesn’t expect to receive content like this or is it that GT expects to remove the source language <span> but encounters some problem with ‘posts’?

I might be getting no replies because it’s not in the ‘Plugins’ category – could a moderator move it?

Okay fixed it. A problem with the code – it was assuming that the text ‘<!–FLAG_BAR_BEGIN–>’ would appear in my ‘post’ pages (I think the correct terminology is ‘single-post’) – however it doesn’t. So I changed the code to look for ‘<!– If you\’d like to support WordPress, having the “powered by” link somewhere on your blog is the best way; it\’s our only promotion or advertising. –>’ – Now it seems to be running fine.