Merge with Worldclock

I've been aware of this duplication, but kind of ignored it. Here we go:
Here's a list of features that are present in Worldclock, that are not in Clock.

1. Multiple times displayed in a table
2. Display of shortened timezone name (Worldclock displays "Germany", where the accurate PHP timezone name is "Europe/Berlin")
3. Display of a Daylight Savings Time marker
4. Display of a footnote

And features that are present in Clock, but not in Worldclock:

Note that 1., 2., and 4., from the Worldclock list can be replicated with Clock and MultiBlock. That requires a bit of config (and 1 line of CSS to make it look just like Worldclock), though. 3. Can be implemented by implementing the theme function provided by clock, but that's not really feasible.

2., 3., and 4. from the Clock list are really just aesthetics, they are not really important for the actual display.

I think the problem is that these two modules each have a valid use-case and a merged module would have to provide for both use-cases.
I have thought about this before and did not come to any conclusion on how to solve this.

Oh, 1. from the Clock list, is actually not true. Worldclock supports updating via JS. I didn't know that. ...
Probably would have solved me a lot of work, to copy their JavaScript.

Updating the list above.
Also adding a new feature for Clock: Ability to configure settings via block admin.

Pointed the maintainers of World Clock here at #717574: Merge with Clock module?

Bump and getting this out of my face/queue.

Nothing happened in months. I guess this is a won't fix. Feel free to re-open if you see this differently.

#859216: WorldClock and Clock modules differences/similarities