pecomato-0.0.15/ 0000755 0001752 0001752 00000000000 10677223051 012373 5 ustar devel devel pecomato-0.0.15/doc/ 0000755 0001752 0001752 00000000000 10677223051 013140 5 ustar devel devel pecomato-0.0.15/doc/DISCLAIMER.t2t 0000600 0001752 0001752 00000001323 10677223051 015176 0 ustar devel devel
%!encoding: iso-8859-1
%!includeconf: txt2tags.rc
= DISCLAIMER =
Copyright (C) 2005-2007 Tristan Chabredier.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
This program 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 General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
pecomato-0.0.15/doc/INSTALL.t2t 0000644 0001752 0001752 00000023364 10677223051 014711 0 ustar devel devel
%!encoding: iso-8859-1
%!includeconf: txt2tags.rc
= PECOMATO - INSTALLATION =
== GNU/Linux installation ==
Available packages for GNU/Linux systems:
- sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
be used if unzip and unrar are installed).
- binary archives for glibc 2.2 x86 32bit, successfully tested on RedHat 7.0
to 9, RHEL 2.1 to 3, Fedora Core 1 and 2, SuSE 7.1 to 9.1, Mandrake 10.x.
Other distros are untested yet.
- binary archives for glibc 2.4 x86 32bit, successfully tested on FC5.
Other distros are still untested.
- binary RPMs and sources RPM built on RH7 (glibc 2.2 x86 32bit) and FC5
(glibc 2.4 x86 32bit), those packages have no distro-specific dependencies
excepted the glibc, so they can be used on other rpm-based systems.
=== Installing from the sources ===
Pre-requisites: installing pecomato from the sources requires a common
GNU/Linux system to be configured, including the traditional toolchain for
ANSI C development (GNU make 3.79, gcc, binutils, etc.). Python 1.5 mininum is
required to generate the documentation. Perl 5 minimum and CVS access are
necessary to build the sources archives (for packagers).
Unpack the sources archive, enter the sources directory then:
```
$ make -f Makefile.linux
$ make -f Makefile.linux install
```
This will install all files in dist-linux/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.
=== Installing from a binary archive ===
Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.
=== Installing from a RPM ===
Prefer RPMs if your system is RPM-based and a RPM is available for your distro.
``` $ rpm -ivh filename.rpm
or to upgrade an already existing version:
``` $ rpm -Uvh filename.rpm
== Unix installation ==
Available packages for Unix systems:
- sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
be used if unzip and unrar are installed).
- binary archives for IBM Aix 4.3.3 32bit to Aix 5.3 32bit.
- binary archives for FreeBSD 5.4 i386 32bit. FreeBSD port is also available.
- binary archives for HP-UX 11.00 32bit to HP-UX 11.11 32bit.
- binary archives for HP-UX 11.23 64bit (Itanium2).
- binary archives for Sun Solaris 2.6 SPARC 32bit (SunOS 5.6) to Solaris 8
SPARC 32bit (SunOS 5.8).
- binary archives for Sun Solaris 10 Intel (SunOS 5.10 i386 32bit).
- binary archives for GNU/Solaris Nexenta (SunOS 5.11 i386 32bit).
=== FreeBSD specific notes ===
pecomato is available from the ports collection of FreeBSD. Make sure that
the ports are installed on your FreeBSD system, then:
```
$ cd /usr/ports/graphics/pecomato
$ make install distclean
```
pecomato is known to compile on FreeBSD 5.4 up to 7.0, with either gcc 3.x or
gcc 4.x, x86 and amd64.
Other than that, you can install pecomato from the sources or from the
available binary package, see below.
=== Installing from the sources ===
Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers).
Unpack the sources archive, enter the sources directory then:
```
$ make -f Makefile.unix
$ make -f Makefile.unix install
```
This will install all files in dist-unix/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.
=== Installing from a binary archive ===
Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.
== QNX installation ==
Available packages for QNX systems:
- sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
be used if unzip and unrar are installed).
- binary archives for QNX 6.3.0 x86 32bit.
=== Installing from the sources ===
Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers).
Unpack the sources archive, enter the sources directory then:
```
$ make -f Makefile.qnx
$ make -f Makefile.qnx install
```
This will install all files in dist-qnx/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.
=== Installing from a binary archive ===
Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.
== BeOS installation ==
Available packages for BeOS systems:
- sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
be used if unzip and unrar are installed).
- binary archive for BeOS Commercial/Personal Editions 5.0.3 x86 32bit.
- binary packages for BeOS Commercial/Personal Editions 5.0.3 x86 32bit, as
well as a .pkg and a .sea.
=== Installing from the sources ===
Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers).
Unpack the sources archive, enter the sources directory then:
```
$ make -f Makefile.beos
$ make -f Makefile.beos install
```
This will install all files in dist-beos/, it's up to you to install the
binary and doc files to your home or to a system-wide location, so that
pecomato is found on the PATH.
=== Installing from a binary archive ===
Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH.
=== Installing from a package (.pkg, .sea) ===
Open the package, and follow the installation instructions (what to install,
where to install).
== Darwin (MacOS X) installation ==
Available packages for Darwin systems:
- sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
be used if unzip and unrar are installed).
- binary archives for Darwin 7.9.0 powerpc 32bit (MacOS X 10.3.19 aka Panther).
=== Installing from the sources ===
Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers). In other word, you need to install the
Devtools.
Unpack the sources archive, enter the sources directory then:
```
$ make -f Makefile.darwin
$ make -f Makefile.darwin install
```
This will install all files in dist-darwin/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.
=== Installing from a binary package ===
Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.
== Microsoft Windows installation ==
Running pecomato needs a common Windows system to be configured.
Available packages for win32 systems:
- sources archive, as .zip, .rar files and self-extractible .exe (as well as
.tar.gz and .tar.bz2 that can be used with winzip, winrar or from cygwin
or mingw environments for instance).
- binary archives, successfully tested on the following win32 x86 32bit OSes:
NT4+SP6, ME, 2000, XP (vanilla, SP1 or SP2) and 2003. Other versions are
untested yet. Those static binary archives are available as .zip, .rar and
.exe (self-extractible) files.
=== Installing from the sources ===
Pre-requisites: installing pecomato from the sources requires a complete ANSI C
development system to be configured (for instance, MSVC++ 6.x and 7.x aka .NET
s OK, but the MS compiler and nmake are sufficient). The sources can be compiled
from a mingw32 or msys subsystem. Python 1.5 mininum is required to generate the
documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers). Some GNU utilies (grep, sed, etc.) are also
necessary, they are part of many distributions like UnxUtils
(http://unxutils.sf.net/), Cygwin, Mingw32/Msys, SFU.
Unpack the sources. Open a console window (cmd.exe) and enter the sources
directory then:
```
$ nmake -f Makefile.win32
$ nmake -f Makefile.win32 install
```
This will install all files in dist-win32/, it's up to you to install the
binary and/or doc files to your user's home or to a system-wide directory (as
an admin user, following the system), preferably so that pecomato.exe executable
is found on all users' PATH.
=== Installing from a binary package ===
Manually unpack the archive to C:\Program files (for instance) or run the self
extracting package and select the install location.
== Installing on other OSes ==
You might be able to compile from the sources under some other Unices or even
different architectures, possibly with minor adaptations. Please report
successful compilations and send me the necessary changes you've made to make
is compile and run OK :-).
pecomato-0.0.15/doc/LICENSE.t2t 0000600 0001752 0001752 00000104443 10677223051 014653 0 ustar devel devel
%!encoding: iso-8859-1
%!includeconf: txt2tags.rc
= GNU GENERAL PUBLIC LICENSE =
//Version 3, 29 June 2007//
Copyright (C) 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
== Preamble ==
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
=== TERMS AND CONDITIONS ===
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
=== END OF TERMS AND CONDITIONS ===
== How to Apply These Terms to Your New Programs ==
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program 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 General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
Copyright (C)
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
.
pecomato-0.0.15/doc/manpage.t2t 0000644 0001752 0001752 00000014435 10677223051 015212 0 ustar devel devel
%!encoding: iso-8859-1
%!includeconf: txt2tags.rc
= NAME =
pecomato - a portable picture-embedded metadata processor
= SYNOPSIS =
**pecomato** [//OPTION//...] //OP// [//EXPR//] //FILE// [//FILE//...]
**pecomato** [//OPTION//...] //OP// [//EXPR//] //@FILE//
usage of form //OP// //EXPR// only concerns //OP// mode **dump-value**, see below.
use //@file// to read a list of files from that file. the file must contain exactly one
filename to process per line (don't escape anything, filenames are taken as-is).
= DESCRIPTION =
**pecomato** is basically designed to display any kind of information embedded
in picture files, as well as checking, filtering, extracting, removing, adding
and fixing such information. In other words, it's a metadata processor.
It supports the following file formats: //JPEG/JFIF//, //Adobe PSD// and //FFO//, raw //IPTC//.
And it knows about the following metadata formats: //JFIF//, //IPTC//, //Exif//, //Adobe// and
Fotostation. More file and metadata formats might be supported later: //TIFF//,
etc.
One of its main goals is to check the validity of parsed metadata as well as
optionally check the strict compliance to official standards. On another hand,
it aims to provide ways of fixing broken or not compliant chunks as well as
providing general basic functions to manipulate the metadata.
Please visit the program homepage at
//""http://www.mollux.org/projects/pecomato/""//. Thanks for reporting issues at
//""https://www.mollux.org/services/bugzilla/""//.
= OPTIONS =
**general options:**
: **-v**, **--version**
show version number then exit
: **-h**, **--help**
show this usage help then exit
: **--list**
list all supported embedded data structures
: **-l**, **--log-level** //NUM//
define verbosity (see possible values below)
: **-c**, **--check-compliance**
perform full checks to test the strict validity and
compliance of structures to official formats
**filtering and extracting options:**
: **-b**, **--backup**
create backup files of (re)written files if necessary
: **-d**, **--target-dir** //DIRNAME//
target directory for all written files
: **-f**, **--fix**
fix metadata inconsistencies when possible
**extracting options:**
: **-x**, **--extract** //TYPE//
extract and save metadata to a standalone file (see
below for a list of metadata types that can be extracted)
: **-t**, **--ext** //EXTENSION//
define what filename extension to use when writing
metadata that is extracted (default: //.iptc//)
: **-a**, **--append-ext**
append extension to original filename when saving
the extracted metadata (default: replace original file
extension)
**filtering options:**
: **-i**, **--include** //EXPR//
a filter expression describing the datasets to keep
: **-i**, **--include** //@FILE//
or a file containing a list of datasets to keep,
all other datasets will be filtered out.
if not used, all datasets will be kept
: **-e**, **--exclude** //EXPR//
a filter expression describing the datasets to filter out
: **-e**, **--exclude** //@FILE//
a file containing a list of datasets to filter out,
all other datasets will be kept. if not used all
datasets will be kept
: **--edit** //EXPR//
a filter edit expression describing the datasets to add
: **--edit** //@FILE//
or a file containing a list of datasets to add.
datasets won't be inserted if that breaks compliance
to the standards
: **--test**
don't override original file, create *.rewrite file.
this option only affects rewriting of source files
**dump options:**
: **-w**, **--wrap** //NUM//
max column for wrapping (num must be in range
[8-1024]). default is to dump unwrapped
= POSSIBLE OPS =
: **check**
just check embedded data structures
: **dump**
show embedded data (headers only)
: **dump-full**
show all embedded data (including values)
: **dump-value**
show requested value (headers only)
: **filter**
filter embedded data (see **-i**, **-e** and **--edit**)
= DUMP-VALUE EXPRESSIONS =
: IPTC.
same as filter include/exclude expression, see below:
= FILTER INCLUDE/EXCLUDE EXPRESSIONS =
: IPTC.
where can be either:
: all: *
: hexadecimal unary: 0xhhhh
: hexadecimal range: 0xhhhh-0xhhhh
: decimal unary: nnn:nnn
: decimal ranges: nnn:nnn-nnn
: nnn:*
**examples:**
: IPTC.0x0219
: IPTC.0x0300-0x0364
: IPTC.3:0-100
= FILTER EDIT EXPRESSIONS =
: IPTC.=:
where can be either:
: hexadecimal unary: 0xhhhh
: decimal unary: nnn:nnn
where can be either:
: hex
: text
and is:
: hex: [a-zA-Z0-9] pairs
: text: any char (even widechars) on the line is taken as text, until
: a newline is found
**examples:**
: IPTC.0x0200=hex:0002
: IPTC.0x0219=text:this is a keyword
= SUPPORTED METADATA FOR EXTRACTION =
: **iptc**
IPTC datasets
= POSSIBLE LOG LEVELS =
: **0**
quiet, no output at all
: **1**
error messages only (default)
: **2**
warning and error messages
: **3**
informative, warning and error messages
: **4**
all messages including debug ones
= SUPPORTED INPUT FILES =
: **JPEG** files (commonly //.jpeg//, //.jpg//, //.jpe//, //.jfif//, //.jif//)
: **Adobe Photoshop** files (commonly //.psd//, //.pdd//, //.ffo//)
: **FotoStation** files (commonly .//fdp//, //.ipt//)
: standalone **IPTC** metadata (commonly //.iptc//)
= EXIT CODES =
: **0**
normal exit
: **1**
usage error
: **2**
asynchronous signal termination
: **3**
normal exit, with warning(s)
: **4**
normal exit, with error(s)
: **5**
fatal error encountered
= EXAMPLES =
: **Check metadata structures of a JPEG file, only report errors**
``$ pecomato check file.jpg``
= AUTHOR =
Written by Tristan Chabredier //"wwp" //.
= COPYRIGHT =
Copyright (C) 2005-2007 Tristan Chabredier.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
This program 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 General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
pecomato-0.0.15/doc/README.t2t 0000644 0001752 0001752 00000005276 10677223051 014542 0 ustar devel devel
%!encoding: iso-8859-1
%!includeconf: txt2tags.rc
= PECOMATO - RELEASE NOTES =
+ Summary +
PECoMaTo stands for Picture-Embedded COntents MAnipulation TOol.
It is basically designed to display any kind of information embedded in
picture files, as well as checking, filtering, extracting, removing, adding and
fixing such information. In other words, it's a metadata processor.
It supports the following file formats: JPEG/JFIF, Adobe PSD and FFO, raw IPTC.
And it knows about the following metadata formats: JFIF, IPTC, Exif, Adobe and
Fotostation. More file and metadata formats might be supported later: TIFF,
Adobe-specific metadata including XMP, etc.
It aims to be portable (see installation section below). One of its main goals
is to check the validity of parsed metadata as well as optionally check the
strict compliance to official standards. On another hand, it aims to provide
ways of fixing broken or not compliant chunks as well as providing general
basic functions to manipulate the metadata.
This program is subject to copyright. However you can copy, use and distribute
it according to the GNU General Public License (GPL v3 or above). See the
DISCLAIMER and LICENSE doc files for further information. It is free of charge,
as well as open-source (the source is available, feel free to submit patches).
+ Installation +
pecomato builds and runs on various x86, ppc, 32bit and 64bit systems:
GNU/Linux, Microsoft Windows (win32), QNX 6, Darwin (and MacOS X), BeOS 5 and
many Unices (IBM Aix, FreeBSD, HP-UX, Sun Solaris, GNU/OpenSolaris, etc).
Some other systems will probably be supported later (other Unices or
platforms/architectures).
pecomato can be installed from the sources or binary packages or a variety of
self-installers and system-specific package formats (.rpm, .pkg, etc.).
There is no dependency at runtime, and building from the sources requires the
minimal GNU ANSI C development toolchain. See the INSTALL file to know what are
the available packages and how to install them. Building the doc requires
python.
+ Usage +
Simply run pecomato from a console or tty. You can get command-line usage or
further information using:
``` $ pecomato --help
A man page (Unix, GNU/Linux) and a short user guide is also available.
+ Bugs and issues +
See the TODO file to get a clue about what is planned to be added or fixed.
Please report detailed problems and bugs to the author (see the links section
of this document).
+ Links +
- Project main page: http://www.mollux.org/projects/pecomato
- Downloads page: http://www.mollux.org/projects/pecomato/download/
- Bug tracker: http://www.mollux.org/projects/services/bugzilla/
- Author: Tristan Chabredier aka wwp subscript@free.fr
pecomato-0.0.15/doc/TODO.t2t 0000644 0001752 0001752 00000004066 10677223051 014346 0 ustar devel devel
%!encoding: iso-8859-1
%!includeconf: txt2tags.rc
= PECOMATO - TODO =
== for 0.1.0: ==
- write a user manual!
- better support for all Photoshop variants (minor)
- add support for IPTC extended datasets (length >32767)
- filter edit: add --overwrite (matters with records unicity)
and --force-sizing (to crop or pad)
- dump EXIF values (major)
- allow filtering of EXIF fields (major)
- more IPTC fixing abilities (add missing record version dataset, crop/enlarge dataset size
according to what the fixed/max size should be)
- better location/name for the man page ($(PREFIX)/man/1/@PRODUCT@.man)
- fix lock w/ latest version of cvs2cl under win32
- backtrace support (either gdb rehooking or glibc's execinfo)
- NSIS or installbuilder win32 packages
- .deb packages
- add a way to create an iptc or exif chunk when it's not present (for instance, prior to
filter edit)
- add a merge command (merge standalone .iptc or .exv files to higher-level files)
== later: ==
- build fat binaries for OSX (see gcc-fat.sh)
- rewrite a modular/object-like management of structure -> allow recursive load/save or nested data structures
- merging (w/ or w/o overriding), replacing, purging of metadata in a jpeg, from an external file
- fix missing mandatory IPTC (and other) data
- support TIFF and PNG reading (as well as other formats)
- macro language to perform all tasks
- split code in a library and a wrapper
- integrate to 4D thru its plugin API
- Qt4 or GTK+ frontend?
- move generated tmp files in ./
- use _16, _32 types
- comply to C code rules (Parasoft ones, etc.)
- use getopt or any further alternative
- use a better/proper command-line analysis method
- add djvu support
- check if we should mmap reads and writes
== ports: ==
- Darwin x86, OpenDarwin, OpenBeOS, OpenBSD
- MacOS 9?
- more Unices
- Atari, Amiga?
- binary packages (QNX qpr, Solaris 10 pkgmk)
- determine if we should link statically for the binary archives we're providing (at least
the gcc lib)
- become a GNU project, opensource certified
- get rid of gnu-*.[ch] files, see if -D_GNU_SOURCE could help
pecomato-0.0.15/doc/user-manual.t2t 0000644 0001752 0001752 00000000126 10677223051 016023 0 ustar devel devel
%!encoding: iso-8859-1
%!includeconf: txt2tags.rc
= PECOMATO - USER MANUAL =
Todo!
pecomato-0.0.15/doc/Makefile.posix 0000644 0001752 0001752 00000005133 10677223051 015743 0 ustar devel devel include Makefile.posix.inc
all: html txt man pdf
html: $(HTML_DOCS)
txt: $(TXT_DOCS)
man: $(MAN_DOCS)
pdf: $(PDF_DOCS)
install: install-html install-txt install-man install-pdf
install-html: html install-html-dir
for FILE in $(HTML_DOCS); \
do \
$(COPY_FILE) $(HTML_DIR)/$$FILE $(INSTALL_HTML_DIR)/; \
done
install-txt: txt install-txt-dir
for FILE in $(TXT_DOCS); \
do \
$(COPY_FILE) $(TXT_DIR)/$$FILE $(INSTALL_TXT_DIR)/; \
done
install-man: man install-man-dir
for FILE in $(MAN_DOCS); \
do \
$(COPY_FILE) $(MAN_DIR)/$$FILE $(INSTALL_MAN_DIR)/; \
done
install-pdf: pdf install-pdf-dir
for FILE in $(PDF_DOCS); \
do \
$(COPY_FILE) $(PDF_DIR)/$$FILE $(INSTALL_PDF_DIR)/; \
done
install-html-dir:
-$(CHECK_EXIST_DIR) $(INSTALL_HTML_DIR) || \
$(CREATE_DIR) $(INSTALL_HTML_DIR)
install-txt-dir:
-$(CHECK_EXIST_DIR) $(INSTALL_TXT_DIR) || \
$(CREATE_DIR) $(INSTALL_TXT_DIR)
install-man-dir:
-$(CHECK_EXIST_DIR) $(INSTALL_MAN_DIR) || \
$(CREATE_DIR) $(INSTALL_MAN_DIR)
install-pdf-dir:
-$(CHECK_EXIST_DIR) $(INSTALL_PDF_DIR) || \
$(CREATE_DIR) $(INSTALL_PDF_DIR)
uninstall: uninstall-html uninstall-txt uninstall-man uninstall-html-dir uninstall-txt-dir uninstall-man-dir uninstall-pdf-dir
uninstall-html:
-for FILE in $(HTML_DOCS); \
do \
$(DEL_FILE) $(INSTALL_HTML_DIR)/$$FILE; \
done
uninstall-txt:
-for FILE in $(TXT_DOCS); \
do \
$(DEL_FILE) $(INSTALL_TXT_DIR)/$$FILE; \
done
uninstall-man:
-for FILE in $(MAN_DOCS); \
do \
$(DEL_FILE) $(INSTALL_MAN_DIR)/$$FILE; \
done
uninstall-html-dir:
-$(DEL_DIR) $(INSTALL_HTML_DIR)
uninstall-txt-dir:
-$(DEL_DIR) $(INSTALL_TXT_DIR)
uninstall-man-dir:
-$(DEL_DIR) $(INSTALL_MAN_DIR)
uninstall-pdf-dir:
-$(DEL_DIR) $(INSTALL_PDF_DIR)
%.html: %.t2t
-$(CHECK_EXIST_DIR) $(HTML_DIR) || \
$(CREATE_DIR) $(HTML_DIR)
$(PYTHON) $(T2T) -t html -i $< -o $(HTML_DIR)/$@
%.txt: %.t2t
-$(CHECK_EXIST_DIR) $(TXT_DIR) || \
$(CREATE_DIR) $(TXT_DIR)
$(PYTHON) $(T2T) -t txt -i $< -o $(TXT_DIR)/$@
%.man: %.t2t
-$(CHECK_EXIST_DIR) $(MAN_DIR) || \
$(CREATE_DIR) $(MAN_DIR)
$(PYTHON) $(T2T) -t man -i $< -o $(MAN_DIR)/$@
%.pdf: %.t2t
-$(CHECK_EXIST_DIR) $(PDF_DIR) || \
$(CREATE_DIR) $(PDF_DIR)
$(PYTHON) $(T2T) -t html -i $< -o $(PDF_DIR)/$<.html
$(HTML2PS) $(PDF_DIR)/$<.html > $(PDF_DIR)/$<.ps
$(PS2PDF) $(PDF_DIR)/$<.ps $(PDF_DIR)/$@
clean::
-$(DEL_FILE) $(HTML_DIR)/*.html
-$(DEL_FILE) $(TXT_DIR)/*.txt
-$(DEL_FILE) $(TXT_DIR)/*.man
-$(DEL_FILE) $(PDF_DIR)/*.pdf $(PDF_DIR)/*.ps $(PDF_DIR)/*.html
-$(DEL_DIR) $(HTML_DIR)/
-$(DEL_DIR) $(TXT_DIR)/
-$(DEL_DIR) $(MAN_DIR)/
-$(DEL_DIR) $(PDF_DIR)/
distclean: uninstall clean
pecomato-0.0.15/doc/Makefile.win32 0000644 0001752 0001752 00000003634 10677223051 015547 0 ustar devel devel include Makefile.win32.inc
all: html txt man
html: $(HTML_DOCS)
txt: $(TXT_DOCS)
man: $(MAN_DOCS)
install: install-html install-txt install-man
install-html: install-html-dir html
for %f in ($(HTML_DOCS)) do \
$(COPY_FILE) $(HTML_DIR)\%f $(INSTALL_HTML_DIR)\%f
install-txt: install-txt-dir txt
for %f in ($(TXT_DOCS)) do \
$(COPY_FILE) $(TXT_DIR)\%f $(INSTALL_TXT_DIR)\%f
install-man: install-man-dir man
for %f in ($(MAN_DOCS)) do \
$(COPY_FILE) $(MAN_DIR)\%f $(INSTALL_MAN_DIR)\%f
install-html-dir::
$(CHECK_NOT_EXIST_DIR) $(INSTALL_HTML_DIR) \
$(CREATE_DIR) $(INSTALL_HTML_DIR)
install-txt-dir::
$(CHECK_NOT_EXIST_DIR) $(INSTALL_TXT_DIR) \
$(CREATE_DIR) $(INSTALL_TXT_DIR)
install-man-dir::
$(CHECK_NOT_EXIST_DIR) $(INSTALL_MAN_DIR) \
$(CREATE_DIR) $(INSTALL_MAN_DIR)
uninstall: uninstall-html uninstall-html-dir uninstall-txt uninstall-man uninstall-txt-dir uninstall-man-dir
uninstall-html::
-for %f in ($(HTML_DOCS)) do \
$(DEL_FILE) $(INSTALL_HTML_DIR)\%f
uninstall-txt::
-for %f in ($(TXT_DOCS)) do \
$(DEL_FILE) $(INSTALL_TXT_DIR)\%f
uninstall-man::
-for %f in ($(MAN_DOCS)) do \
$(DEL_FILE) $(INSTALL_MAN_DIR)\%f
uninstall-html-dir::
-$(DEL_DIR) $(INSTALL_HTML_DIR)
uninstall-txt-dir::
-$(DEL_DIR) $(INSTALL_TXT_DIR)
uninstall-man-dir::
-$(DEL_DIR) $(INSTALL_MAN_DIR)
$(HTML_DOCS): $*.t2t
$(CHECK_NOT_EXIST_DIR) $(HTML_DIR) \
$(CREATE_DIR) $(HTML_DIR)
$(PYTHON) $(T2T) -t html -i $*.t2t -o $(HTML_DIR)\$@
$(TXT_DOCS): $*.t2t
$(CHECK_NOT_EXIST_DIR) $(TXT_DIR) \
$(CREATE_DIR) $(TXT_DIR)
$(PYTHON) $(T2T) -t txt -i $*.t2t -o $(TXT_DIR)\$@
$(MAN_DOCS): $*.t2t
$(CHECK_NOT_EXIST_DIR) $(MAN_DIR) \
$(CREATE_DIR) $(MAN_DIR)
$(PYTHON) $(T2T) -t man -i $*.t2t -o $(MAN_DIR)\$@
clean::
-$(DEL_FILE) $(HTML_DIR)\*.html
-$(DEL_FILE) $(TXT_DIR)\*.txt
-$(DEL_FILE) $(TXT_DIR)\*.man
-$(DEL_DIR) $(HTML_DIR)
-$(DEL_DIR) $(TXT_DIR)
-$(DEL_DIR) $(MAN_DIR)
distclean: uninstall clean
pecomato-0.0.15/doc/Makefile.inc 0000644 0001752 0001752 00000000450 10677223051 015347 0 ustar devel devel HTML_DOCS = DISCLAIMER.html INSTALL.html LICENSE.html README.html TODO.html manpage.html
TXT_DOCS = DISCLAIMER.txt INSTALL.txt LICENSE.txt README.txt TODO.txt
MAN_DOCS = manpage.man
PDF_DOCS = user-manual.pdf
HTML_DIR = .html
TXT_DIR = .txt
MAN_DIR = .man
PDF_DIR = .pdf pecomato-0.0.15/doc/Makefile.posix.inc 0000644 0001752 0001752 00000000260 10677223051 016507 0 ustar devel devel include ../Makefile.posix.inc
include Makefile.defs
include Makefile.inc
T2T = ../devtools/txt2tags.py --no-rc
HTML2PS = ../devtools/html2ps.pl -f html2ps.cfg
PS2PDF = ps2pdf
pecomato-0.0.15/doc/Makefile.win32.inc 0000644 0001752 0001752 00000000160 10677223051 016306 0 ustar devel devel include ..\Makefile.win32.inc
include Makefile.defs
include Makefile.inc
T2T = ..\devtools\txt2tags.py --no-rc
pecomato-0.0.15/doc/txt2tags.rc 0000644 0001752 0001752 00000000437 10677223051 015252 0 ustar devel devel %!postproc(html): '([0-9]+)' '\2'
%!postproc(html): '' ''
%!postproc(html): ']*>' ''
%!postproc(html): '([a-z0-9\-\.]+)@([a-z0-9\-\.]+)' '\1 (at) \2'
%!postproc(txt): '([a-z0-9\-\.]+)@([a-z0-9\-\.]+)' '<\1 (at) \2>'
pecomato-0.0.15/doc/html2ps.cfg 0000644 0001752 0001752 00000002140 10677223051 015207 0 ustar devel devel BODY {
text-align: justify;
}
A:link {
color: blue;
}
@html2ps {
paper {
type: A4;
}
option {
encoding: "ISO-8859-1";
toc: "bh";
startno: 5;
titlepage: 1;
underline: 1;
number: 0;
colour: 1;
}
toc {
heading: "
Table of Contents
";
}
titlepage {
content: "
The PECoMaTo User Manual
Copyright (c) 2005-2007 Tristan Chabredier
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
This program 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 General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
}
header {
center: "The PECoMaTo User Manual";
}
showurl: 0;
}
pecomato-0.0.15/devtools/ 0000755 0001752 0001752 00000000000 10677223051 014232 5 ustar devel devel pecomato-0.0.15/devtools/txt2tags.py 0000755 0001752 0001752 00000465332 10677223051 016404 0 ustar devel devel #!/usr/bin/env python
# txt2tags - generic text conversion tool
# http://txt2tags.sf.net
#
# Copyright 2001, 2002, 2003, 2004, 2005, 2006 Aurelio Marinho Jargas
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, version 2.
#
# This program 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 General Public License for more details.
#
# You have received a copy of the GNU General Public License along
# with this program, on the COPYING file.
#
########################################################################
#
# BORING CODE EXPLANATION AHEAD
#
# Just read if you wish to understand how the txt2tags code works
#
########################################################################
#
# Version 2.0 was a complete rewrite for the program 'core'.
#
# Now the code that [1] parses the marked text is separated from the
# code that [2] insert the target tags.
#
# [1] made by: def convert()
# [2] made by: class BlockMaster
#
# The structures of the marked text are identified and its contents are
# extracted into a data holder (Python lists and dictionaries).
#
# When parsing the source file, the blocks (para, lists, quote, table)
# are opened with BlockMaster, right when found. Then its contents,
# which spans on several lines, are feeded into a special holder on the
# BlockMaster instance. Just when the block is closed, the target tags
# are inserted for the full block as a whole, in one pass. This way, we
# have a better control on blocks. Much better than the previous line by
# line approach.
#
# In other words, whenever inside a block, the parser *holds* the tag
# insertion process, waiting until the full block is read. That was
# needed primary to close paragraphs for the new XHTML target, but
# proved to be a very good adding, improving many other processing.
#
# -------------------------------------------------------------------
#
# There is also a brand new code for the Configuration schema, 100%
# rewritten. There are new classes, all self documented: CommandLine,
# SourceDocument, ConfigMaster and ConfigLines. In short, a new RAW
# Config format was created, and all kind of configuration is first
# converted to this format, and then a generic method parses it.
#
# The init processing was changed also, and now the functions which
# gets informations about the input files are: get_infiles_config(),
# process_source_file() and convert_this_files()
#
# Other parts are untouched, and remains the same as in v1.7, as the
# marks regexes, target Headers and target Tags & Rules.
#
########################################################################
# Now I think the code is nice, easier to read and understand
#XXX Python coding warning
# Avoid common mistakes:
# - do NOT use newlist=list instead newlist=list[:]
# - do NOT use newdic=dic instead newdic=dic.copy()
# - do NOT use dic[key] instead dic.get(key)
# - do NOT use del dic[key] without has_key() before
#XXX Smart Image Align don't work if the image is a link
# Can't fix that because the image is expanded together with the
# link, at the linkbank filling moment. Only the image is passed
# to parse_images(), not the full line, so it is always 'middle'.
#XXX Paragraph separation not valid inside Quote
# Quote will not have inside, instead will close and open
# again the
. This really sux in CSS, when defining a
# different background color. Still don't know how to fix it.
#XXX TODO (maybe)
# New mark or macro which expands to an anchor full title.
# It is necessary to parse the full document in this order:
# DONE 1st scan: HEAD: get all settings, including %!includeconf
# DONE 2nd scan: BODY: expand includes & apply %!preproc
# 3rd scan: BODY: read titles and compose TOC info
# 4th scan: BODY: full parsing, expanding [#anchor] 1st
# Steps 2 and 3 can be made together, with no tag adding.
# Two complete body scans will be *slow*, don't know if it worths.
# One solution may be add the titles as postproc rules
##############################################################################
# User config (1=ON, 0=OFF)
USE_I18N = 1 # use gettext for i18ned messages? (default is 1)
COLOR_DEBUG = 1 # show debug messages in colors? (default is 1)
BG_LIGHT = 0 # your terminal background color is light (default is 0)
HTML_LOWER = 0 # use lowercased HTML tags instead upper? (default is 0)
##############################################################################
# These are all the core Python modules used by txt2tags (KISS!)
import re, string, os, sys, time, getopt
# Program information
my_url = 'http://txt2tags.sf.net'
my_name = 'txt2tags'
my_email = 'verde@aurelio.net'
my_version = '2.4'
# i18n - just use if available
if USE_I18N:
try:
import gettext
# If your locale dir is different, change it here
cat = gettext.Catalog('txt2tags',localedir='/usr/share/locale/')
_ = cat.gettext
except:
_ = lambda x:x
else:
_ = lambda x:x
# FLAGS : the conversion related flags , may be used in %!options
# OPTIONS : the conversion related options, may be used in %!options
# ACTIONS : the other behavior modifiers, valid on command line only
# MACROS : the valid macros with their default values for formatting
# SETTINGS: global miscellaneous settings, valid on RC file only
# NO_TARGET: actions that don't require a target specification
# NO_MULTI_INPUT: actions that don't accept more than one input file
# CONFIG_KEYWORDS: the valid %!key:val keywords
#
# FLAGS and OPTIONS are configs that affect the converted document.
# They usually have also a --no-