I've noticed that Translated blocks are being treated differently to "original language" blocks. For example, one block on my site, the content in English is rendered with <p> tags by Drupal, but the translated Korean language content is missing the <p>.
See in the top right hand corner there is an address? This is a block that I have added to the header section in "Blocks". The content is translated into Korean using the language interface.
Example (www.jpguitarland.com.au/drupal-6.10/):
English data:
37/160 Rowe Street, Eastwood NSW
Phone: (02) 9858 3210
Fax: (02) 9482 1003
E-mail: skhjames@jpguitarland.com.au
Korean data:
37/160 Rowe Street, Eastwood NSW
전화기: (02) 9858 3210
팩스: (02) 9482 1003
이메일: skhjames@jpguitarland.com.au
You'll see that neither of these has a <p> tag, but I find that in the final code that Drupal renders, the English version is wrapped in<p>, but the Korean version isn't.
Comments
Comment #1
jose reyero commentedComment #2
hass commentedSounds like a duplicate of #368173: Full HTML Blocks cannot be translated and has been fixed in core 6.13 by #352121: locale_string_is_safe() is not suitable for user provided text in non-default textgroups