Free tz software for linux

DateTime::TimeZone::Tzfile is a Perl module that contains tzfile (zoneinfo) timezone files.

SYNOPSIS

use DateTime::TimeZone::Tzfile;

$tz = DateTime::TimeZone::Tzfile->new("/etc/localtime");

if($tz->is_floating) { ...
if($tz->is_utc) { ...
if($tz->is_olson) { ...
$category = $tz->category;
$tz_string = $tz->name;

if($tz->has_dst_changes) { ...
if($tz->is_dst_for_datetime($dt)) { ...
$offset = $tz->offset_for_datetime($dt);
$abbrev = $tz->short_name_for_datetime($dt);
$offset = $tz->offset_for_local_datetime($dt);

An instance of this class represents a timezone that was encoded in a file in the tzfile(5) format. These can express arbitrary patterns of offsets from Universal Time, changing over time. Offsets and change times are limited to a resolution of one second.

This class implements the DateTime::TimeZone interface, so that its instances can be used with DateTime objects.

Bazaar-NG (or bzr) is a project of Canonical to develop an open source distributed version control system that is powerful, friendly, and scalable.
Version control means a system that keeps track of previous revisions of software source code or similar information and helps people work on it in teams.
bzr is still at a fairly early stage of development but has been self-hosting since March 2005 with no loss of data.
bzr is the next-generation distributed version control.
Main features:
- Written in Python (but nevertheless fast and easy to install.)
- Runs on Linux, Windows and Mac OS X, or any system with a Python interpreter. (Primarily tested on Ubuntu.)
- Free software, released under the GNU GPL.
- Designed to play well with others: can be called by IDEs, editors, web tools, GUIs, etc through either a Python API or a shell interface, and possibly a C interface in the future. Can support workflow/process tools built on top.
- The user interface is simple and familiar to people with experience from CVS or Subversion: add, mv, diff, status, commit, log, merge, etc all do what you would expect.
- Offers a choice between centralized and decentralized work within a single project: when in the office, you can work on a shared central branch. For experimental changes or offline work you can make a branch on your laptop and merge back in later.
- Preserves history; any previous revision can be recreated. History can be GPG-signed to protect against man-in-the-middle attacks, bad mirrors, server intrusion or data corruption.
- Just one .bzr directory at the top of the tree; it doesnt clutter the tree or get in your face. No wierd ++file--names--0.
- Tracks file and directory renames and merges across them.
- Powerful Python plugin system for adding new commands, protocols, formats, or site policy.
Enhancements:
- merge now takes --uncommitted, to apply uncommitted changes from a tree.
- Moderate performance improvements, particularly on large trees.
- Compatability with diffutils 2.8.4. bzr uncommit preserves pending merges.
- Active FTP support has been fixed.
- TZ=UTC is handled properly when reading/writing revisions.
- GPG_TTY is used to allow gpg --cl to work with gpg-agent in a pipeline (passing text to sign in on stdin).
- External diff does the right thing for binaries even in foreign languages.

Contacts is a stand-alone address book application for the ROX Desktop. There is an extra package for users of other freedesktop.org compliant environments.
You can use Contacts to view and create vCard business cards. Contacts creates a vCard for every contact and stores it in a central directory in your home folder. A reasonable subset of rfc2426 has been implemented.
Main features:
Tabs
- There are two tabs, one for home, one for work related data.
Drag & Drop Loading
- You can load a vCard by dragging it onto Contacts.
- You can add a sound, photo or logo the same way. Contacts figures out by filetype which is which. Drag an image onto the "Home" tab if you want it to be added as a photo. To add a logo image, switch to the "Work" tab before dragging!
Searching
- Use the toolbar entry for searching contacts.
Extended Attributes
- Contacts saves the cards with extended attributes on Linux and Solaris, if supported by the filesystem:
- user.mime_type = text/directory
- user.creator = Contacts
My Card
- You can tell Contacts which card is yours: "Menu->My Card->This is my card"
- At any later time you can easily load your card by pressing "Alt-M" or from
- "Menu->My Card->Open my card"
PGP
- Contacts supports embedded public PGP keys.
- They can be exported from a vCard to a file, or directly imported into your keyring.
Live Toolbar
- The presence of NOTE, KEY, SOUND, PHOTO, LOGO, GEO/TZ properties is indicated by toolbar icon.
- Info about those properties is available through the icon tooltip. Click to edit!
- You add them in the first place via menu and short-cuts or dragn drop, respectively.
Birthday Notification
- Nearing birthdays are indicated by the color of a birthday cake in the toolbar:
- Next birthday more than a week away
- Next birthday within seven days
- Next birthday tomorrow
- There is a birthday today
- When there is no birthdate recorded for any of your contacts, no cake is shown.

Date::Manip is a date manipulation routines.

SYNOPSIS

use Date::Manip;

$version = DateManipVersion;

$date = ParseDate(@args);
$date = ParseDate($string);
$date = ParseDate($string);

@date = UnixDate($date,@format);
$date = UnixDate($date,@format);

$delta = ParseDateDelta(@args);
$delta = ParseDateDelta($string);
$delta = ParseDateDelta($string);

@str = Delta_Format($delta,$dec,@format);
$str = Delta_Format($delta,$dec,@format);

$recur = ParseRecur($string,$base,$date0,$date1,$flags);
@dates = ParseRecur($string,$base,$date0,$date1,$flags);

$flag = Date_Cmp($date1,$date2);

$d = DateCalc($d1,$d2 [,$errref] [,$del]);

$date = Date_SetTime($date,$hr,$min,$sec);
$date = Date_SetTime($date,$time);

$date = Date_SetDateField($date,$field,$val [,$nocheck]);

$date = Date_GetPrev($date,$dow,$today,$hr,$min,$sec);
$date = Date_GetPrev($date,$dow,$today,$time);

$date = Date_GetNext($date,$dow,$today,$hr,$min,$sec);
$date = Date_GetNext($date,$dow,$today,$time);

$name = Date_IsHoliday($date);

$listref = Events_List($date);
$listref = Events_List($date0,$date1);

$date = Date_ConvTZ($date);
$date = Date_ConvTZ($date,$from);
$date = Date_ConvTZ($date,"",$to);
$date = Date_ConvTZ($date,$from,$to);

$flag = Date_IsWorkDay($date [,$flag]);

$date = Date_NextWorkDay($date,$off [,$time]);

$date = Date_PrevWorkDay($date,$off [,$time]);

$date = Date_NearestWorkDay($date [,$tomorrowfirst]);

&Date_Init();
&Date_Init("VAR=VAL","VAR=VAL",...);
@list = Date_Init();
@list = Date_Init("VAR=VAL","VAR=VAL",...);

The above routines all check to make sure that Date_Init is called. If it hasnt been, they will call it automatically. As a result, there is usually no need to call Date_Init explicitely unless you want to change some of the config variables (described below). They also do error checking on the input.

The routines listed below are intended primarily for internal use by other Date::Manip routines. They do little or no error checking, and do not explicitely call Date_Init. Those functions are all done in the main Date::Manip routines above.

Because they are significantly faster than the full Date::Manip routines, they are available for use with a few caveats. Since little or no error checking is done, it is the responsibility of the programmer to ensure that valid data (AND valid dates) are passed to them. Passing invalid data (such as a non-numeric month) or invalid dates (Feb 31) will fail in unpredictable ways (possibly returning erroneous results). Also, since Date_Init is not called by these, it must be called explicitely by the programmer before using these routines.

In the following routines, $y may be entered as either a 2 or 4 digit year (it will be converted to a 4 digit year based on the variable YYtoYYYY described below). Month and day should be numeric in all cases. Most (if not all) of the information below can be gotten from UnixDate which is really the way I intended it to be gotten, but there are reasons to use these (these are significantly faster).

$day = Date_DayOfWeek($m,$d,$y);
$secs = Date_SecsSince1970($m,$d,$y,$h,$mn,$s);
$secs = Date_SecsSince1970GMT($m,$d,$y,$h,$mn,$s);
$days = Date_DaysSince1BC($m,$d,$y);
$day = Date_DayOfYear($m,$d,$y);
($y,$m,$d,$h,$mn,$s) = Date_NthDayOfYear($y,$n);
$days = Date_DaysInYear($y);
$days = Date_DaysInMonth($m,$y);
$wkno = Date_WeekOfYear($m,$d,$y,$first);
$flag = Date_LeapYear($y);
$day = Date_DaySuffix($d);
$tz = Date_TimeZone();

Time::Format is a Perl module for easy-to-use date/time formatting.

SYNOPSIS

use Time::Format qw(%time %strftime %manip);

$time{$format}
$time{$format, $unixtime}

print "Today is $time{yyyy/mm/dd}n";
print "Yesterday was $time{yyyy/mm/dd, time-24*60*60}n";
print "The time is $time{hh:mm:ss}n";
print "Another time is $time{H:mm am tz, $another_time}n";
print "Timestamp: $time{yyyymmdd.hhmmss.mmm}n";
%time also accepts Date::Manip strings and DateTime objects:
$dm = Date::Manip::ParseDate(last monday);
print "Last monday was $time{Month d, yyyy, $dm}";
$dt = DateTime->new (....);
print "Heres another date: $time{m/d/yy, $dt}";
It also accepts most ISO-8601 date/time strings:
$t = 2005/10/31T17:11:09; # date separator: / or - or .
$t = 2005-10-31 17.11.09; # in-between separator: T or _ or space
$t = 20051031_171109; # time separator: : or .
$t = 20051031171109; # separators may be omitted
$t = 2005/10/31; # date-only is okay
$t = 17:11:09; # time-only is okay
# But not:
$t = 20051031; # date-only without separators
$t = 171109; # time-only without separators
# ...because those look like epoch time numbers.
%strftime works like POSIXs strftime, if you like those %-formats.
$strftime{$format}
$strftime{$format, $unixtime}
$strftime{$format, $sec,$min,$hour, $mday,$mon,$year, $wday,$yday,$isdst}

print "POSIXish: $strftime{%A, %B %d, %Y, 0,0,0,12,11,95,2}n";
print "POSIXish: $strftime{%A, %B %d, %Y, 1054866251}n";
print "POSIXish: $strftime{%A, %B %d, %Y}n"; # current time
%manip works like Date::Manips UnixDate function.
$manip{$format};
$manip{$format, $when};

print "Date::Manip: $manip{%m/%d/%Y}n"; # current time
print "Date::Manip: $manip{%m/%d/%Y,last Tuesday}n";
These can also be used as standalone functions:
use Time::Format qw(time_format time_strftime time_manip);

print "Today is ", time_format(yyyy/mm/dd, $some_time), "n";
print "POSIXish: ", time_strftime(%A %B %d, %Y,$some_time), "n";
print "Date::Manip: ", time_manip(%m/%d/%Y,$some_time), "n";

This module creates global pseudovariables which format dates and times, according to formatting codes you pass to them in strings.

The %time formatting codes are designed to be easy to remember and use, and to take up just as many characters as the output time value whenever possible. For example, the four-digit year code is "yyyy", the three-letter month abbreviation is "Mon".

The nice thing about having a variable-like interface instead of function calls is that the values can be used inside of strings (as well as outside of strings in ordinary expressions). Dates are frequently used within strings (log messages, output, data records, etc.), so having the ability to interpolate them directly is handy.

Perl allows arbitrary expressions within curly braces of a hash, even when that hash is being interpolated into a string. This allows you to do computations on the fly while formatting times and inserting them into strings. See the "yesterday" example above.

The format strings are designed with programmers in mind. What do you need most frequently? 4-digit year, month, day, 24-based hour, minute, second -- usually with leading zeroes. These six are the easiest formats to use and remember in Time::Format: yyyy, mm, dd, hh, mm, ss. Variants on these formats follow a simple and consistent formula. This module is for everyone who is weary of trying to remember strftime(3)s arcane codes, or of endlessly writing $t[4]++; $t[5]+=1900 as you manually format times or dates.

Note that mm (and related codes) are used both for months and minutes. This is a feature. %time resolves the ambiguity by examining other nearby formatting codes. If its in the context of a year or a day, "month" is assumed. If in the context of an hour or a second, "minute" is assumed.

The format strings are not meant to encompass every date/time need ever conceived. But how often do you need the day of the year (strftimes %j) or the week number (strftimes %W)?

For capabilities that %time does not provide, %strftime provides an interface to POSIXs strftime, and %manip provides an interface to the Date::Manip modules UnixDate function.

If the companion module Time::Format_XS is also installed, Time::Format will detect and use it. This will result in a significant speed increase for %time and time_format.

WWW::Google::SiteMap::URL is URL Helper class for WWW::Google::SiteMap.

This is a helper class that supports WWW::Google::SiteMap and WWW::Google::SiteMap::Index.

METHODS

new()

loc()

Change the URL associated with this object. For a WWW::Google::SiteMap this specifies the URL to add to the sitemap, for a WWW::Google::SiteMap::Index, this is the URL to the sitemap.

changefreq()

Set the change frequency of the object. This field is not used in sitemap indexes, only in sitemaps.

lastmod()

Set the last modified time. You have to provide this as one of the following:

a complete ISO8601 time string

A complete time string will be accepted in exactly this format:

YYYY-MM-DDTHH:MM:SS+TZ:TZ
YYYY - 4-digit year
MM - 2-digit month (zero padded)
DD - 2-digit year (zero padded)
T - literal character T
HH - 2-digit hour (24-hour, zero padded)
SS - 2-digit second (zero padded)
+TZ:TZ - Timezone offset (hours and minutes from GMT, 2-digit, zero padded)

epoch time

Seconds since the epoch, such as would be returned from time(). If you provide an epoch time, then an appropriate ISO8601 time will be constructed with gmtime() (which means the timezone offset will be +00:00). If anyone knows of a way to determine the timezone offset of the current host that is cross-platform and doesnt add dozens of dependencies then I might change this.
an ISO8601 date (YYYY-MM-DD)

A simple date in YYYY-MM-DD format. The time will be set to 00:00:00+00:00.

a DateTime object.

If a DateTime object is provided, then an appropriate timestamp will be constructed from it.

a HTTP::Response object.

If given an HTTP::Response object, the last modified time will be calculated from whatever time information is available in the response headers. Currently this means either the Last-Modified header, or tue current time - the current_age() calculated by the response object. This is useful for building web crawlers.

Note that in order to conserve memory, any of these items that you provide will be converted to a complete ISO8601 time string when they are stored. This means that if you pass an object to lastmod(), you cant get it back out. If anyone actually has a need to get the objects back out, then I might make a configuration option to store the objects internally.

If you have suggestions for other types of date/time objects or formats that would be usefule, let me know and Ill consider them.

priority()

Set the priority. This field is not used in sitemap indexes, only in sitemaps.

delete()

Delete this object from the sitemap or the sitemap index.

lenient()

If lenient contains a true value, then errors will not be fatal.