Free geodaten international streets 3.00 software for linux

International Components for Unicode provides a Unicode implementation, with functions for formatting numbers, dates, times, and currencies (according to locale conventions, transliteration, and parsing text in those formats).
It provides flexible patterns for formatting messages, where the pattern determines the order of the variable parts of the messages, and the format for each of those variables. These patterns can be stored in resource files for translation to different languages. Included are more than 100 codepage converters for interaction with non-unicode systems.
Main features:
- Text: Unicode text handling, full character properties and character set conversions (500+ code pages)
- Analysis: Unicode regular expressions; full Unicode sets; character, word and line boundaries
- Comparison: language sensitive collation and searching
- Transformations: normalization, upper/lowercase, script transliterations (50+ pairs)
- Locales: comprehensive data (230+) & resource bundle architecture
- Complex Text Layout: Arabic, Hebrew, Indic and Thai
- Formatting and Parsing: multi-calendar and time zone,dates, times, numbers, currencies, messages
Enhancements:
- This is a major release, with new features, new APIs, and many bugfixes in data and code.
- ICU uses and supports Unicode 5.0, which is the latest major release of Unicode.
- CU uses and supports data from Common Locale Data Repository (CLDR) 1.4, which includes many improvements in quality and quantity of data.
- A charset detection framework was added, which provides heuristics for detecting the charset for unlabeled sequences of bytes.
- Other performance and feature enhancements were added.

Geo:Coder:US 1.00 offers a full-feature facility for geocoding US addresses, that is, estimating the latitude and longitude of any street address or intersection in the United States, using the TIGER/Line data set from the US Census Bureau. Geo:Coder:US uses Geo:TigerLine to parse this data, and DB_File to store a highly compressed distillation of it, and Geo:StreetAddress:US to parse addresses into normalized components suitable for looking up in its database.

You can find a live demo of this code at http://geocoder.us/. The demo.cgi script is included in eg/ directory distributed with this module, along with a whole bunch of other goodies. See Geo:Coder:US:Import for how to build your own Geo:Coder:US database.

Consider using a web service to access this geocoder over the Internet, rather than going to all the trouble of building a database yourself. See eg/soap-client.pl, eg/xmlrpc-client.pl, and eg/rest-client.pl for different examples of working clients for the rpc.geocoder.us geocoder web service.

Major Features:

1. Geo:Coder:US->geocode( $string )
   • Given a string containing a street address or intersection, return a list of specifiers including latitude and longitude for all matching entities in the database. To keep from churning over the entire database, the given address string must contain either a city and state, or a ZIP code (or both), or geocode() will return undef.
   • geocode() will attempt to normalize directional prefixes and suffixes, street types, and state abbreviations, as well as substitute TIGER/Line's idea of the "primary street name", if an alternate street name was provided instead.
   • If geocode() can parse the address, but not find a match in the database, it will return a hashref containing the parsed and normalized address or intersection, but without the "lat" and "long" keys specifying the location. If geocode() cannot even parse the address, it will return undef. Be sure to check for the existence of "lat" and "long" keys in the hashes returned from geocode() before attempting to use the values! This serves to distinguish between addresses that cannot be found versus addresses that are completely unparseable.
   • geocode() attempts to be as forgiving as possible when geocoding an address. If you say "Mission Ave" and all it knows about is "Mission St", then "Mission St" is what you'll get back. If you leave off directional identifiers, geocode() will return address geocoded in all the variants it can find, i.e. both "N Main St" and "S Main St".
   • Don't be surprised if geocoding an intersection returns more than one lat/long pair for a single intersection. If one of the streets curves greatly or doglegs even slightly, this will be the likely outcome.
   • geocode() is probably the method you want to use. See more in the following section on the structure of the returned address and intersection specifiers.
2. Geo:Coder:US->geocode_address( $string )
   • Works exactly like geocode(), but only parses addresses.
3. Geo:Coder:US->geocode_intersection( $string )
   • Works exactly like geocode(), but only parses intersections.
4. Geo:Coder:US->filter_ranges( $spec, @candidates )
   • Filters a list of address specifiers (presumably from the database) against a query specifier, filtering by prefix, type, suffix, or primary name if possible. Returns a list of matching specifiers. filter_ranges() will ignore a filtering step if it would result in no specifiers being returned. You probably won't need to use this.
5. Geo:Coder:US->find_ranges( $address_spec )
   • Given a normalized address specifier, return all the address ranges in the database that appear to cover that address. find_ranges() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_ranges() to find the closest match possible in preference to returning nothing. You probably want to use lookup_ranges() instead, which will call find_ranges() for you.
6. Geo:Coder:US->lookup_ranges( $address_spec, @ranges )
   • Given an address specifier and (optionally) some address ranges from the database, interpolate the street address into the street segment referred to by the address range, and return a latitude and longitude for the given address within each of the given ranges. If @ranges is not given, lookup_ranges() calls find_ranges() with the given address specifier, and uses those returned. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.
7. Geo:Coder:US->find_segments( $intersection_spec )
   • Given a normalized intersection specifier, find all of the street segments in the database matching the two given streets in the given locale or ZIP code. find_segments() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_segments() to find the closest match possible in preference to returning nothing. You probably want to use lookup_intersection() instead, which will call find_segments() for you.
8. Geo:Coder:US->lookup_intersection( $intersection_spec )
   • Given an intersection specifier, return all of the intersections in the database between the two streets specified, plus a latitude and longitude for each intersection. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.

Requirements: Perl

InterXim project is an international, locale-independent X11 XIM server.

It translates ASCII key sequences to Unicode.

The converter uses the Yudit kmap files to transform the ASCII string to Unicode KeySym.

123 Travel Search is an extension which creates 3 small travel search icons on the bottom of your browser.

Creates 3 small travel search icons on the bottom of your browser. When clicking on them, they will create a little search box which allows you to enter your travel details once and then select the providers you want to see.

International users will see a metasearch. Depending on where the user is from, the search will be redirected to show merchants that can handle the purchase request.

Template::Plugin::Datum is a Perl module with TT2 plugin that converts international date format to German date format.

SYNOPSIS

[% USE Datum %]

von: [% 20030101 | datum %] -> 01.01.2003
bis: [% 2003-12-31 | datum %] -> 31.12.2003

Zeitstempel: [% 20031212143000 | datum %] -> 12.12.2003 14:30:00

This plugin converts international date format (year-month-day) to German date format (day.month.year).

Recognized formats are:

yyyy-mm-dd (2003-12-31)
yyyymmdd (20031231)
yyyymmddHHMMSS (20031231143000) date and time

Telephony::CountryDialingCodes is a Perl module that can convert international dialing codes to country codes and vice versa.

SYNOPSIS

# Usage method 1 (using object methods):
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $country_code = NL;
print "The dialing access code for country $country_code is " . $o->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = $o->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";


# Usage method 2 (using class methods):
use Telephony::CountryDialingCodes;
my $country_code = NL;
print "The dialing access code for country $country_code is " . Telephony::CountryDialingCodes->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = Telephony::CountryDialingCodes->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";

# Extracting an intl dialing code from an intl phone number:
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $dialing_code = $o->extract_dialing_code(+521234567890);
# $dialing_code will contain 52.

This class exports a method for determining a countrys international dialing code, and another method for doing the reverse: i.e. determining the country code(s) that belong(s) to a given international dialing code.

You can call these methods as class methods or you can create an object and call these methods as object methods. The difference is that if you call them in object context that the internal lookup tables are freed when the object is destroyed, otherwise if you call the methods in class context, then the internal lookup tables are global and will persist for the lifespan of the current process. Its not really a big deal which approach you choose, so for the sake of style, use the object method approach if you have no clue which is better.

Epoch JavaScript Calendar and DatePicker runs on all major browsers and features a fast user interface, multiple date selection, flat or popup modes, CSS styling, automatic date formatting, full object-oriented design, and more. Epoch DHTML JavaScript Calendar is available in over a dozen major international languages.
Main features:
- Fast loading and initialization
- Intuitive, customizable interface
- Compatible with all Modern Browsers - see compatibility chart below.
- Can display as a Flat or Popup (DatePicker) calendar
- Automatic Date Formatting - US, European, or create your own!
- Multiple-Date selection - by clicking on calendar cells or the day & week headings.

sqlDESKTOP is a computerized manual filing system arranged just like an ordinary office with pictures of real cabinets and real folders. You can arrange by project, by department or whatever makes sense to you.
sqlDESKTOP doesnt tell you how to organize, it lets you do things your own way. Documents are easy to find because you dont have to remember the exact name of the document or where you put it. Instead, you can visually locate what you are looking for in a familiar office environment and click on it.
Main features:
- Marketing report (Microsoft Word file)
- sales forecast (star office file)
- Resellers agreements (data shared with his salesmen team)
- Photos of company plant (Album photo)
- Order records (database query)
- E-commerce site (Internet Web page)
- Press release (Email sent to journalists)
- Customers feedback forum (Internet Newsgroup)
Enhancements:
- MySQL release 5, SqlServer 2005 (the free version of SqlServer), DB2, Oracle, and Derby - Cloudscape are supported.
- A server component was added for small networks without a DBA: sqlDESKTOPserver.
- The Derby - Cloudscape database is embedded with sqlDESKTOPserver.
- A back up feature was added for the single user version.
- Support for digital photos was improved.
- You can save a photo with bulk talk or in comics format into a JPEG file.
- You can mail a photo with bulk talk or in comics format directly to traditional email client application.