This information is taken from the following source.
1. Get root access (I use the ssh approach (ssh root@localhost))
2. cd /usr/share/osso-clock/
3. nano wdb-parsed.txt (you can use vi if you want but I've installed and prefer nano over vi)
4. Here is my home city info:
Regina|CA|Canada|America/Regina|285|262|en_CA
(City name)|(Country initials)|(Country)|(Time zone)|(x co-ordinate on clock image)|(y co-ordinate on clock image)|(Default language)
5. Save and your done
Now you will need to add your city's name into OS2008. This info comes from the following post.
1. cd /usr/share/local/(enter language here mine is en_CA)/LC_MESSAGES/
2. Copy osso-cities.mo from this location to a Linux box
* If the file does not exist then grab the file from another language (I had to grab en_US)
3. msgunfmt osso-cities.mo -o osso-cities.po
4. nano osso-cities.po (or vi osso-cities.po if you prefer vi over nano)
5. Add the following 4 lines (the blank spaces are important!)
msgid "osso_db_city_regina"
msgstr "Regina"
6. msgfmt osso-cities.po -o osso-cities.mo
7. Copy osso-cities.mo back to your PDA and overwrite the old file.
This in theory should work for Regina (fixing the name display problem)
Even though I am a Brit, I assume you use en_US :P
I currently use en_UK but I would prefer to use en_CA. I noticed in the the folder that there was a bunch of .mo files. What do I need to use to edit them? I could just look for the entry I need to change in there.
I think someone should create a project at either Google code or Sourceforge and keep an up to date location DB. That way people will only have to download a zip/rar rather then enter in thousands of locations.
There should be at least one (but no more then 3) locations per administrative district. Example each Canadian Province and Territory should have it's capitol (including Ottawa) in there plus any other major cities like Vancouver, Calgary, Saskatoon, Brandon, Thunder Bay, Sudbury, Sault Ste Marie, London, Montreal, Moncton, Cape Breton, and Labrador City.
The zip/rar would most likely be unzipped from /usr/share/ so that we could hit both wdb-parsed.txt and the appropriate osso-cities.mo files.
Why? The point, as far as I can see, is one per time zone; therefore, one in US Eastern, and one in Canadian Eastern, because DST may differ, but not one for each US state in Eastern. (I think this is accomplished from the factory.)
To me, it's just a cool tweak to be able to put my very own hometown on, but if I'm not going wild with that, any city guaranteed to be the same offset from UTC is close enough... so the 3-max seems pointless.
Why? The point, as far as I can see, is one per time zone; therefore, one in US Eastern, and one in Canadian Eastern, because DST may differ, but not one for each US state in Eastern. (I think this is accomplished from the factory.)
To me, it's just a cool tweak to be able to put my very own hometown on, but if I'm not going wild with that, any city guaranteed to be the same offset from UTC is close enough... so the 3-max seems pointless.
I like to know where different cities near me are. Besides there is at least on city per nation in Europe for the map. Each province and state in Canada and the US is similar to that and as such show have equal representation. The other advantage of this project would be that down the line when DST goes out of fashion, individual provinces and states that abolish DST would have their info updated. A little work now would save a lot of work later on.
I dunno 'bout Canada, they're wierd up there. In the US, though, states don't have the autonomy regarding time zones that European nations do. The Federal government is in charge of it, so they're not really similar.
When DST goes out of fashion? ROFL.
I'm from Indiana, where we used to have straight-up time; UTC -0500, no ifs, ands, or buts. Our governor, Mitch, railroaded DST through here, so we could "be like every one else" and "save lots of money on energy". Well, we are like everyone else now; we waste time switching any clocks not synchronized automatically, for a net loss in money. (And it's not like the parks who could save money on outdoor lighting couldn't have changed their hours without changing the clocks, I suppose.)
Much as I'd like to fantasize about rationality, no state is really going to change to be different from everyone else. Moreover, at least in the US, all Mitch could do was make a Federal agency review our time zone, and send a recommendation along. No bureaucrat in Washington has either the brains or the intestines to approve a state abolishing DST, even if some legislature and governor were smitten with enough sense to send up such a recommendation.
The amount of work, it seems, would be the same either way, as it's the same number of provinces... but I think it's unlikely we need it at all from that perspective, politics being as decoupled from rationality as it is.
Still, I do appreciate the info, and if you do get such a project set up, I'd probably contribute an entry or two for Indiana...
In the US, though, states don't have the autonomy regarding time zones that European nations do. The Federal government is in charge of it, so they're not really similar.