Software-Engineering Martin Fabiani

Sitemap (Navigation ohne JavaScript)

Impressum: Martin Fabiani, Röderbergweg 104, D-60485 Frankfurt, Tel: +49 (69) 49084808, E-Mail: info (at) fabiani.net, USt-IdNr: DE217298609

Codebeispiele zu Perl

Automatisches Verlinken von Urls

Sehr einfach geht es mit dem Modul URI::Find::Schemeless. Es ist vom Modul URI::Find abgeleitet, welches hingegen nur URIs der Form http://www.fabiani.net/ oder mailto:martin@fabiani.net erkennt. URI::Find::Schemeless ist da sehr viel freier, und erkennt auch Uris der Form www.fabiani.net oder ftp.suse.com.

Hier ein kleines Codebeispiel:


01: #! /usr/bin/perl
02: use strict;
03: use warnings;
04: use URI::Find::Schemeless;
05: use HTML::Entities qw(encode_entities);
06: 
07: my $text = q~
08:     hallo dies ist keine.url
09:     dies ist aber eine: www.fabiani.net
10:     ftp.irgendwas.de/test/thisfile mailto:martin@fabiani.net oder so
11:     yeah martin@fabiani.net http://www.fabiani.net/
12:     ~;
13: 
14: 
15: # neues URI::Find::Schemeless-Objekt erstellen und ihm als Callback
16: # die Aktion mitgeben, die fuer jede gefundene URI ausgefuehrt werden
17: # soll:
18: 
19: my $finder = URI::Find::Schemeless->new
20:     ( 
21:       sub {
22:       my ($uri, $originalUri) = @_;
23: #        return qq~<a href="$uri" target="_newpage">$originalUri</a>~;
24:       
25:       return 
26:           q/<a href="/ . encode_entities("$uri") . q/">/ .
27:           encode_entities($originalUri) . q~</a>~;
28:       }
29:       );
30: 
31: # hier beginnt die eigentliche Suche und (in unserem Fall) Ersetzung:        
32: my $howManyFound = $finder->find(\$text);
33: 
34: # schauen wir uns doch das Ergebnis an:
35: print "$howManyFound URIs found\n";
36: print "$text\n";

Leider gehört die Modulgruppe URI::Find noch nicht zu den Standardmodulen.Falls der Provider sie nicht installieren will (z.B. mit: perl -MCPAN -e "install 'URI::Find'") , kann man sich die benötigten Dateien irgendwo in sein Verzeichnis kopieren (z.B. nach cgi-bin/lib) und es dann im Perlscript, welches in cgi-bin liegt, mit den folgenden Codezeilen laden:


1: BEGIN {
2:   use FindBin qw($Bin);
3:   use lib "$Bin/lib";
4: }
5: use URI::Find;

Siehe dazu auch die Tips&Tricks zu Modulen

Man sollte URI::Find keine HTML-Dokumente geben, weil es sonst bei Links eventuellen Blödsinn macht, wenn man nicht sehr aufpasst

Dokumentation zu URI::Find:

NAME
URI::Find - Find URIs in arbitrary text

SYNOPSIS
require URI::Find;

my $finder = URI::Find->new(\&callback);

$how_many_found = $finder->find(\$text);

DESCRIPTION
This module does one thing: Finds URIs and URLs in plain text. It finds
them quickly and it finds them all (or what URI::URL considers a URI to
be.) It only finds URIs which include a scheme (http:// or the like),
for something a bit less strict have a look at URI::Find::Schemeless.

Public Methods

new
my $finder = URI::Find->new(\&callback);

Creates a new URI::Find object.

&callback is a function which is called on each URI found. It is
passed two arguments, the first is a URI::URL object representing
the URI found. The second is the original text of the URI found. The
return value of the callback will replace the original URI in the
text.

find
my $how_many_found = $finder->find(\$text);

$text is a string to search and possibly modify with your callback.

Protected Methods

I got a bunch of mail from people asking if I'd add certain features to
URI::Find. Most wanted the search to be less restrictive, do more
heuristics, etc... Since many of the requests were contradictory, I'm
letting people create their own custom subclasses to do what they want.

The following are methods internal to URI::Find which a subclass can
override to change the way URI::Find acts. They are only to be called
inside a URI::Find subclass. Users of this module are NOT to use these
methods.

uri_re
my $uri_re = $self->uri_re;

Returns the regex for finding absolute, schemed URIs
(http://www.foo.com and such). This, combined with
schemeless_uri_re() is what finds candidate URIs.

Usually this method does not have to be overridden.

schemeless_uri_re
my $schemeless_re = $self->schemeless_uri_re;

Returns the regex for finding schemeless URIs (www.foo.com and such)
and other things which might be URIs. By default this will match
othing (though it used to try to find schemeless URIs which started
with "www" and "ftp").

Many people will want to override this method. See the
URI::Find::Schemeless manpage for a subclass does a reasonable job
of finding URIs which might be missing the scheme.

uric_set
my $uric_set = $self->uric_set;

Returns a set matching the 'uric' set defined in RFC 2396 suitable
for putting into a character set ([]) in a regex.

You almost never have to override this.

cruft_set
my $cruft_set = $self->cruft_set;

Returns a set of characters which are considered garbage. Used by
decruft().

decruft
my $uri = $self->decruft($uri);

Sometimes garbage characters like periods and parenthesis get
accidentally matched along with the URI. In order for the URI to be
properly identified, it must sometimes be "decrufted", the garbage
characters stripped.

This method takes a candidate URI and strips off any cruft it finds.

recruft
my $uri = $self->recruft($uri);

This method puts back the cruft taken off with decruft(). This is
necessary because the cruft is destructively removed from the string
before invoking the user's callback, so it has to be put back
afterwards.

schemeless_to_schemed
my $schemed_uri = $self->schemeless_to_schemed($schemeless_uri);

This takes a schemeless URI and returns an absolute, schemed URI.
The standard implementation supplies ftp:// for URIs which start
with ftp., and http:// otherwise.

is_schemed
$obj->is_schemed($uri);

Returns whether or not the given URI is schemed or schemeless. True
for schemed, false for schemeless.

Old Functions


The old find_uri() function is still around and it works, but its
deprecated.

EXAMPLES
Simply print the original URI text found and the normalized
representation.

my $finder = URI::Find->new(
sub {
my($uri, $orig_uri) = @_;
print "The text '$orig_uri' represents '$uri'\n";
return $orig_uri;
});
$finder->find(\$text);

Check each URI in document to see if it exists.

use LWP::Simple;

my $finder = URI::Find->new(sub {
my($uri, $orig_uri) = @_;
if( head $uri ) {
print "$orig_uri is okay\n";
}
else {
print "$orig_uri cannot be found\n";
}
return $orig_uri;
});
$finder->find(\$text);

Turn plain text into HTML, with each URI found wrapped in an HTML
anchor.

use CGI qw(escapeHTML);

$text = "<pre>\n" . escapeHTML($text) . "</pre>\n"; # siehe Anmerkung*
my $finder = URI::Find->new(
sub {
my($uri, $orig_uri) = @_;
return qq|<a href="$uri">$orig_uri</a>|;
});
$finder->find(\$text);

CAVEATS, BUGS, ETC...
RFC 2396 Appendix E suggests using the form '<http://www.foo.com>' or
'<URL:http://www.foo.com>' when putting URLs in plain text. URI::Find
accomidates this suggestion and considers the entire thing (brackets and
all) to be part of the URL found. This means that when find_uris() sees
'<URL:http://www.foo.com>' it will hand that entire string to your
callback, not just the URL.

NOTE: The prototype on find_uris() is already getting annoying to me. I
might remove it in a future version.

SEE ALSO
<URI::Find::Schemeless>, <URI::URL>, <URI>,
RFC 2396 (especially Appendix E)

AUTHOR
Michael G Schwern <schwern@pobox.com> with insight from Uri Gutman, Greg
Bacon, Jeff Pinyan, Roderick Schertler and others.

Currently maintained by Roderick Schertler <roderick@argon.org>.


*) Die Verwendung von escapeHTML im obigen Beispiel ist leider nicht korrekt, weil da eventuell URLs kaputt gemacht werden. Als besseres Beispiel siehe meinen Code...

Dokumentation URI::Find::Schemeless

NAME
URI::Find::Schemeless - Find schemeless URIs in arbitrary text.

SYNOPSIS
require URI::Find::Schemeless;

my $finder = URI::Find::Schemeless->new(\&callback);

The rest is the same as URI::Find.

DESCRIPTION
URI::Find finds absolute URIs in plain text with some weak heuristics
for finding schemeless URIs. This subclass is for finding things which
might be URIs in free text. Things like "www.foo.com" and
"lifes.a.bitch.if.you.aint.got.net".

The heuristics are such that it hopefully finds a minimum of false
positives, but there's no easy way for it know if "COMMAND.COM" refers
to a web site or a file.

AUTHOR
Original code by Roderick Schertler <roderick@argon.org>, adapted by
Michael G Schwern <schwern@pobox.com>.

Currently maintained by Roderick Schertler <roderick@argon.org>.

SEE ALSO
<URI::Find>

 


Letztes Update dieser Seite: Sunday, 16-Jan-2005 22:47:28 CET