Free postal addresses software for linux

Geo::StreetAddress::US is a Perl extension for parsing US street addresses.

SYNOPSIS

use Geo::StreetAddress::US;

my $hashref = Geo::StreetAddress::US->parse_location(
"1005 Gravenstein Hwy N, Sebastopol CA 95472" );

my $hashref = Geo::StreetAddress::US->parse_location(
"Hollywood & Vine, Los Angeles, CA" );

my $hashref = Geo::StreetAddress::US->parse_address(
"1600 Pennsylvania Ave, Washington, DC" );

my $hashref = Geo::StreetAddress::US->parse_intersection(
"Mission Street at Valencia Street, San Francisco, CA" );

my $normal = Geo::StreetAddress::US->normalize_address( %spec );
# the parse_* methods call this automatically...

Geo::StreetAddress::US is a regex-based street address and street intersection parser for the United States. Its basic goal is to be as forgiving as possible when parsing user-provided address strings.

Geo::StreetAddress::US knows about directional prefixes and suffixes, fractional building numbers, building units, grid-based addresses (such as those used in parts of Utah), 5 and 9 digit ZIP codes, and all of the official USPS abbreviations for street types and state names.

AddressTangler is a PHP function that helps you protect email addresses that you need to add to a web page from spam bots.
The project uses a simple HTML/CSS trick: The email address is divided into groups of letters, then each group is placed on a table cell, but not sequentially. If a bot browses the HTML code or strips out all the tags from it, it wont find the email address (which is shown correctly when the browser displays the page) but instead a mixed set of groups of letters.
The address, even if correctly displayed, cannot be selected nor copied/pasted. It must be manually typed.
How to use it
It is quite easy to use this function. You only need to give it the email address as a parameter, and it will return the HTML TABLE code.
Remember to copy the at.php file to your webpage folder and add a line like this to the beginning of your PHP code:
require "at.php";
Also remember to add the CSS definition for the table cells to the page with class "at_r1" as follows:
TD.at_r1 {vertical-align:bottom;}
(Note: since the result is a simple HTML table, you dont need to use this function if your page is made with just HTML. You can simply copy the HTML code written on this page and correct it according to the email address that you need to display.)
Version restrictions:
- Keep in mind that not only spam bots will have trouble detecting the email address: the text-to-speech software used by blind users will likely also be affected.
- So, if you plan to make your email address accessible to them, you must provide a second way to publish it. At the present time, this is out of the scope of this project. (perhaps in the future...)
- A possible solution could be to try to describe the address. But even if this results in a high security level, it would be hard to implement it into an automatic function. Also, it could be annoying to hear and complex to understand when used with addresses that make use of many random numbers and letters.

Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822.

SYNOPSIS

use Mail::RFC822::Address qw(valid validlist);

if (valid("pdw@ex-parrot.com")) {
print "Thats a valid addressn";
}

if (validlist("pdw@ex-parrot.com, other@elsewhere.com")) {
print "Thats a valid list of addressesn";
}

Mail::RFC822::Address validates email addresses against the grammar described in RFC 822 using regular expressions. How to validate a user supplied email address is a FAQ (see perlfaq9): the only sure way to see if a supplied email address is genuine is to send an email to it and see if the user recieves it. The one useful check that can be performed on an address is to check that the email address is syntactically valid. That is what this module does.

This module is functionally equivalent to RFC::RFC822::Address, but uses regular expressions rather than the Parse::RecDescent parser. This means that startup time is greatly reduced making it suitable for use in transient scripts such as CGI scripts.

valid ( address )

Returns true or false to indicate if address is an RFC822 valid address.

validlist ( addresslist )

In scalar context, returns true if the parameter is an RFC822 valid list of addresses.

In list context, returns an empty list on failure (an invalid address was found); otherwise a list whose first element is the number of addresses found and whose remaining elements are the addresses. This is needed to disambiguate failure (invalid) from success with no addresses found, because an empty string is a valid list

Google::Adwords::Address is a Google Adwords Address object.
SYNOPSIS
use Google::Adwords::Address;
my $address = Google::Adwords::Address->new
->addressLine1(first street)
->city(Paris)
->companyName(My company)
->countryCode(FR)
->emailAddress(my@example.com);
This object should be used with the AccountService API calls
METHODS
Mutators (read/write)
- addressLine1
- addressLine2
- city
- companyName
- countryCode
- emailAddress
- faxNumber
- name
- phoneNumber
- postalCode
- state

RFC822 Address Parser Library provides application developers with a complete parser for RFC822 addresses. Not only can you use the library to verify that RFC822 addresses are syntactically correct, you can also have an address split up into its semantic parts, what is needed when deciding where to route an address to, etc.
What is quite unique is that librfc822 does indeed parse all address types allowed by the standard. That includes such weird things as "address groups" or addresses with whitespace and comments throw in. Take a look at this beast to get an idea:
testing my parser : peter.simons@gmd.de,
(peter.)simons@rhein.de ,,,,,
testing my parser ,
it rules < @peti.gmd.de,@listserv.gmd.de:simons @ cys .de >
;
,
peter.simons@acm.org
That is indeed a legal e-mail address in RFC822 messages. It contains five separate addresses, which are grouped together. Heres the parsed result:
peter.simons@gmd.de
simons@rhein.de
simons@ieee.org
< @peti.gmd.de,@listserv.gmd.de:simons@cys.de >
peter.simons@acm.org
simons@rhein.de
simons@rhein.de
simons@rhein.de
In case you wonder: The strange looking address thats listed fourth is a so called "routing address" -- and yes, thats a legal e-mail address, too. These were popular in the early days of the Internet. Back then, every mail server that relayed an e-mail put its own address into this construct so that bounces could be routed the same way back that they originally went.
The address says that the mail should be send to the host peti.gmd.de, then to listserv.gmd.de, and from there it should be delivered (using any route) to the address simons@cys.de. These days, such addresses can hardly be used, because nobody relays for other recipients anymore. Still, these are legal.
librfc822 provides you with several routines that parse the different flavours of e-mail addresses as defined in the standard. The results will be placed in a rfc822address structure and returned. If constructs are parsed that may contain multiple addresses, you can pass a "committer" class to the function, which is called every time a correct address is found and may append it to a container of your choice.
Enhancements:
- The library has been re-released under an all-permissive license.

HTML TIDY is a free utility to fix mistakes made while editing HTML and to automatically tidy up sloppy editing into nicely layed out markup. It also works great on the atrociously hard to read markup generated by specialized HTML editors and conversion tools, and can help you identify where you need to pay further attention on making your pages more accessible to people with disabilities.
When editing HTML its easy to make mistakes. Wouldnt it be nice if there was a simple way to fix these mistakes automatically and tidy up sloppy editing into nicely layed out markup? Well now there is! Dave Raggetts HTML TIDY is a free utility for doing just that. It also works great on the atrociously hard to read markup generated by specialized HTML editors and conversion tools, and can help you identify where you need to pay further attention on making your pages more accessible to people with disabilities.
Tidy is able to fix up a wide range of problems and to bring to your attention things that you need to work on yourself. Each item found is listed with the line number and column so that you can see where the problem lies in your markup. Tidy wont generate a cleaned up version when there are problems that it cant be sure of how to handle. These are logged as "errors" rather than "warnings".
Dave Raggett has now passed the baton for maintaining Tidy to a group of volunteers working together as part of the open source community at Source Forge. The source code continues to be available under an open source license, and you are encouraged to pass on bug reports and enhancement requests at http://tidy.sourceforge.net.
If you find HTML Tidy useful and you would like to say thanks, then please send me a (paper) postcard or other souvenir from the area in which you live along with a few words on what you are using Tidy for. It will be fun to map out where Tidy users are to be found! My postal address is given at the end of this file.
The W3C public email list devoted to HTML Tidy is: . To subscribe send an email to html-tidy-request@w3.org with the word subscribe in the subject line (include the word unsubscribe if you want to unsubscribe). The archive for this list is accessible online. If you would like to contact the developers, or you just want to submit an enhancement request or a bug report, please visit http://tidy.sourceforge.net.
Tidy can now perform wonders on HTML saved from Microsoft Word 2000! Word bulks out HTML files with stuff for round-tripping presentation between HTML and Word. If you are more concerned about using HTML on the Web, check out Tidys "Word-2000" config option! Of course Tidy does a good job on Word97 files as well!
Main features:
- Missing or mismatched end tags are detected and corrected
- End tags in the wrong order are corrected
- Fixes problems with heading emphasis
- Recovers from mixed up tags
- Getting the

---

in the right place
- Adding the missing "/" in end tags for anchors
- Perfecting lists by putting in tags missed out
- Missing quotes around attribute values are added
- Unknown/Proprietary attributes are reported
- Proprietary elements are recognized and reported as such
- Tags lacking a terminating > are spotted