** Changed in: gnome-panel
Importance: Unknown = Low
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: gnome-panel (Ubuntu)
Status: Incomplete = Triaged
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
** Changed in: gnome-panel
Status: Unknown = New
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I forwarded it upstream
** Changed in: gnome-panel
Importance: Undecided = Unknown
Bugwatch: None = GNOME Bug Tracker #565168
Status: New = Unknown
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug notification
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.
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug notification because you are a member
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?
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug
could someone send it upstream at bugzilla.gnome.org?
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
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
any news about this?
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
may someone having this issue forward it upstream? i'm leaving this as
incomplete until that, thanks.
** Changed in: gnome-panel (Ubuntu)
Status: New = Incomplete
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://bugs.launchpad.net/bugs/74670
You received this bug
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.
--
GNOME Clock has duplicate 0x20's on single-figure dates
https://launchpad.net/bugs/74670
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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.
--
GNOME Clock
Thank you for your bug. Very minor detail, I'm not sure that's a bug,
why one space would be nicer?
** Changed in: Ubuntu
Sourcepackagename: None = gnome-panel
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
** Also affects: gnome-panel (upstream)
Importance:
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
14 matches
Mail list logo
