Ajout d'un man sous de forme de pod

Le numero de version calcul� a partir du tag CVS peut contenir des lettres!

1 files changed, 76 insertions, 3 deletions

diff --git a/Perl/Zinc.pm b/Perl/Zinc.pm
index 4415f2b..525c656 100644
--- a/Perl/Zinc.pm
+++ b/Perl/Zinc.pm
@@ -17,12 +17,12 @@ use vars qw($VERSION);
 # the following line initialize $VERSION to either the tag used for
 # CVS checkout -r tag_x_y_z
 #   (typically at package creation) or the file revision
-# if no tag has been used typically $VERSION is initialized to
+# if no tag has been used $VERSION is initialized to
 # the file revision number
 my $TAG= q$Name$;                 # this line is automagically modified by CVS
 my $REVISION = q$Revision$ ;  # this line is automagically modified by CVS
-($VERSION) = $TAG =~ /^\D*([\d_]+)/ ;
-if (defined $VERSION and $VERSION ne "_") {
+($VERSION) = $TAG =~ /^\D*(\d+[\w]+)/ ;
+if (defined $VERSION) {
     $VERSION =~ s/_/\./g;
 }
 else {
@@ -48,4 +48,77 @@ Tk::Methods("add", "addtag", "anchorxy", "bbox", "becomes", "bind", "cget",
 	    "treset", "trestore", "tsave", "type", "verticeat");
 
 1;
+
 __END__
+
+=head1 NAME
+
+Tk::Zinc - TkZinc is a kind of Canvas which proposes many new functionnalities
+
+=for category Tk Widget Classes
+
+=head1 SYNOPSIS
+
+I<$zinc> = I<$parent>-E<gt>B<Zinc>(?I<options>?);
+
+=head1 DESCRIPTION
+
+I<Zinc> widget is very similar to Tk Canvase in that it supports
+structured graphics. Like the Canvas, TkZinc implements items used to
+display graphical entities. Those items can be manipulated and bindings can be
+associated with them to implement interaction behaviors. But unlike the
+Canvas, TkZinc can structure the items in a hierarchy (with the use of
+group items), has support for affine 2D transforms (i.e. translation, scaling, and
+rotation), clipping can be set for sub-trees of the item hierarchy, the item set
+is quite more powerful including field specific items for Air Traffic systems and
+new rendering techniques such as transparency and gradients.
+
+Since the 3.2.2 version, TkZinc also offers as a runtime option, the support
+for openGL rendering, giving access to features such as antialiasing, transparency,
+color gradients and even a new, openGL oriented, item type triangles.
+
+TkZinc full documentation is available as part of the Zinc software as a
+pdf file, B<refman.pdf> and html pages B<refman/index.html>.
+
+As a complement to the reference manual, small Perl/Tk demos of TkZinc are
+also available through a small application named zinc-demos, highly inspired
+from the widget application included in Tk. The aim of these demos are both
+to demonstrates the power of TkZinc and to help newcomers start using
+TkZinc with small examples.
+
+=head1 WHERE CAN I FIND TkZinc?
+
+TkZinc is available as source in tar.gz format or as Debian or RedHat/Mandrake
+packages at http://www.openatc.org/zinc or http://freshmeat.net/projects/zincisnotcanvas/
+
+=head1 AUTHOR
+
+Patrick Lecoanet <lecoanet@cena.fr>
+
+=head1 COPYRIGHT
+
+Zinc has been developed by the CENA (Centres d'Etudes de la Navigation
+Aérienne) for its own needs in advanced HMI (Human Machine Interfaces or Interactions).
+Because we are confident in the benefit of free software, the CENA delivered this
+toolkit under the GNU Library General Public License.
+
+This code is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+Library General Public License for more details.
+
+Parts of this software are derived from the Tk toolkit which is copyrighted
+under another open source license by The Regents of the University of California
+and Sun Microsystems, Inc. The general polygon clipper, GPC, is copyrighted by
+the Advanced Interfaces Group, Department of Computer Science, University of
+Manchester. GPC can't be used for commercial purposes without an agreement and a monetary
+contribution to the University of Manchester. Please contact them at gpc@cs.man.ac.uk
+It is possible to use Zinc without including GPC, it is a compile time decision. The GL
+font rendering is derived from Mark Kilgard code described in `A Simple OpenGL-based
+API for Texture Mapped Text' and is copyrighted by Mark Kilgard under an open source license.
+
+=head1 SEE ALSO
+
+L<Tk(1)>, L<zinc-demos(1)>.
+
+=cut