Two plus signs in Swedish date_fmt locale

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1002987/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Status changed to 'Confirmed' because the bug affects multiple users.

So it seems. But is date_fmt used anywhere? The "%C" conversion specifier seems to be used for something else by both strftime() and g_date_time_format().

The date_fmt variable seems to be used by the date command; if I write date in a terminal this is what I get:
tis 19 mar+ 2013 18.54.+35 CET

Ditto; I get the same format when using date.

Also verified it by creating my own locale file. My custom locale, a copy of sv_SE minus the plus signs (so to speak) makes date output the correct format.

This bug was fixed in the package langpack-locales - 2.13+git20120306-9

---------------
langpack-locales (2.13+git20120306-9) raring; urgency=low

  * debian/patches/debian-submitted-bz9725-locale-sv_SE.diff:
    Correction of date_fmt in sv_SE:
    - Incorrect '+' characters removed (LP: #1002987).
    - Time separator changed to ':' to be consistent with t_fmt and
      d_t_fmt.
 -- Gunnar Hjalmarsson <email address hidden> Wed, 20 Mar 2013 12:47:00 +0100

Hi Seb,

Thanks for the upload.

This change affects the output of the date() command, and can break people's scripts that parse that output. Making the change in a stable release seems not to be a good idea, so I close the Precise task.