When I made a translation of this release and imported this to my Drupal site the logs said there where three strings that couldn't be translated as they contain illegal HTML. The strings are these:

#: includes/date.inc:284
msgid "<Not specified>"

#: includes/date.inc:289
msgid "<None>"

#: includes/date.inc:252
msgid "<none>"

Just remove the brackets or change them to ().

And there is also one more string that can't be translated but I don't know how to solve this:
#: js/signup_edit_form.js:0
msgid "Edit"

CommentFileSizeAuthor
#2 date.inc_.patch1.14 KBmagnus
#2 date.inc_1.patch1.17 KBmagnus

Comments

dww’s picture

dww
we/he/they
commented

I wrapped the stuff you pasted inside <code> tags so we can actually see what you're talking about...

I was going to mark this "won't fix", since core does the same. However, looks like core does the following:

'<'. t('none') .'>'

(from taxonomy.module, for example). So yeah, I guess we could do the same here. Feel free to provide a patch.

Cheers,
-Derek

magnus’s picture

magnus commented
Version: 6.x-1.0-rc6 » 6.x-1.x-dev
Assigned: Unassigned » magnus
Status: Active » Needs review
StatusFileSize
new date.inc_1.patch1.17 KB
new date.inc_.patch1.14 KB

Here comes two patches to choose from.
The first patch replaces the brackets and the second one embeds them like:
'<'. t('none') .'>'

magnus’s picture

magnus commented
Status: Needs review » Reviewed & tested by the community

This is two very simple patches to choose from. That's why I marked it RTBC myself.

ezra-g’s picture

ezra-g commented
Title: Not translatable strings » Untranslatable strings in date.inc
Status: Reviewed & tested by the community » Fixed

I went with the patch that follows core's use of t(). Committed. Thanks!

http://drupal.org/cvs?commit=470410

ezra-g’s picture

ezra-g commented
Version: 6.x-1.x-dev » 6.x-2.x-dev
Status: Fixed » Patch (to be ported)
ezra-g’s picture

ezra-g commented
Issue summary: View changes

wrapped in so you can actually see what they're talking about...