# One translation string was skipped because it contains disallowed HTML. #7 translation strings were skipped because they contain disallowed HTML.
Ok, i think there are some HTML tags not supported, but which are them?
Thanks!
# One translation string was skipped because it contains disallowed HTML. #7 translation strings were skipped because they contain disallowed HTML.
Ok, i think there are some HTML tags not supported, but which are them?
Thanks!
Comments
Comment #1
psicomante commentedComment #2
gábor hojtsyDrupal core works this way. You do not get this error from l10n_server right, but when importing the translation to Drupal? See http://api.drupal.org/api/function/locale_string_is_safe/6 for the list of allowed tags. Drupal core strings pass this for sure. Do you have a module which does not?
Comment #3
psicomante commentedWhen importing the "all-in-one" po file of Drupal core in Drupal 6.13 i get that error. And if i export the CVS package i get this error
http://drupal.org/node/539670
THanks Gàbor.
Comment #4
gábor hojtsyhttp://drupal.org/node/539670 has a clear error message on your modules-filter.po, so there you have an issue. Look into there and see whether you see anything unusual around line 58 as the error message says. I think the two errors can be related.
Comment #5
psicomante commentedFound the issue!
Comment #6
gábor hojtsyUhm, but what dangerous tags would be in this text? I see none. Also, the error above says 7 such messages were found with dangerous tags.
Comment #7
psicomante commentedehm i don't know. I see there are other 6 identical msgstr errors in others files.
Comment #8
psicomante commentedforgot one thing: see at "\n". It misses in the translated string. I was wondering if there is a way to search these problems in l10n_server.
Comment #9
gábor hojtsyTheoretically, we have code in l10n_server for exactly this, so when you submit a translation, the beginning and ending whitespace on the translation is first stripped and then added as in the source string. Not sure why it did not apply here. Maybe we only do that when you enter text on the UI and not when you import?
Comment #10
psicomante commentedi'm using the SQL query
Comment #11
psicomante commentedi found others string in that exported .po that doesn't match the "is_safe" verification.
and other two...
Anyway i must added the "\n" in the l10n_server UI manually. Now it should work. I think we should make some test, because i don't know if the user doesn't add the "\n" at the top, l10n_server add it automatically.
Thank you for support.
Comment #12
gábor hojtsy#1020842: Error messages when importing translated strings fails are not helpful at all is about providing better error messages for this (among fixing some core strings). Marking as a duplicate.