GNOME Clock has duplicate 0x20's on single-figure dates

[Alexander Jones]

I suspect this is because libc formats dates for monospace text display.

Example, today is 6 December 2006.

My clock is quite clearly reading "Wed·Dec··6,·17:45", and it looks a bit stupid. (Aside the fact that it's an American date format and my locale was supposed to be English/GB, but that's another bug.)

[Sebastien Bacher (seb128)]

Thank you for your bug. Very minor detail, I'm not sure that's a bug, why one space would be nicer?

[Alexander Jones (alex-weej)]

Because it would be consistent with itself. In a monospace terminal, the width of a space is equal to the width of a digit, so dates line up in, e.g. "ls". This isn't the case with variable-width fonts and it just looks silly to have inconsistent spacing between, e.g. "Fri··9·Feb,·17:42" and "Sat·10·Feb,·17:42".

[Chris Rose (chris-vault5)]

I agree with Alex here - the extra space seems a little pointless. I can understand why its there if you use a monospace font for the clock - to stop the clock expanding / contracting when the date changes. Not many people do however. It stands out now its been pointed out, heh.

[Alexander Jones (alex-weej)]

I think it's just that the stock date format string is designed for monospace terminals, and we're just borrowing that stuff for the clock.

[Pedro Villavicencio (pedro)]

may someone having this issue forward it upstream? i'm leaving this as incomplete until that, thanks.

[Pedro Villavicencio (pedro)]

any news about this?

[Alexander Jones (alex-weej)]

Still an issue. In general, date and time strings are generated all
over GNOME with simple gettext tokens. I don't see this going away
until we add stuff to GLib.

The band-aid solution for Clock Applet is to collapse multiple spaces
into 1 space, as there is no strftime token that prints the
day-of-month without padding.

[Pedro Villavicencio (pedro)]

could someone send it upstream at bugzilla.gnome.org?

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Maybe the additional space is there, because of bug https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/159323 and it there instead of the missing leading zero?

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Forget my last comment...

My clock is reading "Sa, 06. Dez, 12:16" , so instead of a whitespace numbers lower than 10 have a leading zero.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

I forwarded it upstream