pax_global_header 0000666 0000000 0000000 00000000064 13655206052 0014516 g ustar 00root root 0000000 0000000 52 comment=e0ec5528d79a1119717b74489a7d83bfd1349a31
xapers-0.9.0/ 0000775 0000000 0000000 00000000000 13655206052 0013026 5 ustar 00root root 0000000 0000000 xapers-0.9.0/.gitignore 0000664 0000000 0000000 00000000044 13655206052 0015014 0 ustar 00root root 0000000 0000000 *~
*.pyc
dist
build
xapers.egg-info
xapers-0.9.0/COPYING 0000664 0000000 0000000 00000001213 13655206052 0014056 0 ustar 00root root 0000000 0000000 Xapers 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, (in the COPYING-GPL-3 file in this
directory). If not, see http://www.gnu.org/licenses/
xapers-0.9.0/COPYING-GPL-3 0000664 0000000 0000000 00000104374 13655206052 0014652 0 ustar 00root root 0000000 0000000
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
.
xapers-0.9.0/MANIFEST.in 0000664 0000000 0000000 00000000060 13655206052 0014560 0 ustar 00root root 0000000 0000000 include COPYING COPYING-GPL-3 README.md NEWS.md
xapers-0.9.0/Makefile 0000664 0000000 0000000 00000002255 13655206052 0014472 0 ustar 00root root 0000000 0000000 # -*- makefile -*-
VERSION:=$(shell git describe --tags | sed -e s/_/~/ -e s/-/+/ -e s/-/~/)
PV_FILE=lib/xapers/version.py
.PHONY: all
all:
.PHONY: test
test:
./test/xapers-test
.PHONY: update-version
update-version:
echo "__version__ = '$(VERSION)'" >$(PV_FILE)
.PHONY: release
ifdef V
update-version: VERSION:=$(V)
release: VERSION:=$(V)
release: update-version
head -1 NEWS.md | grep "^Xapers $(VERSION) "
make test
git commit -m "Update version for release $(VERSION)." $(PV_FILE) || true
git tag --sign -m "Xapers $(VERSION) release." $(VERSION)
else
release:
git tag -l | grep -v debian/
endif
.PHONY: deb-snapshot debian-snapshot
debian-snapshot: deb-snapshot
deb-snapshot:
rm -rf build/snapshot
mkdir -p build/snapshot/debian
git archive HEAD | tar -x -C build/snapshot/
git archive debian:debian | tar -x -C build/snapshot/debian/
cd build/snapshot; make update-version
cd build/snapshot; dch -b -v $(VERSION) -D UNRELEASED 'test build, not for upload'
cd build/snapshot; echo '3.0 (native)' > debian/source/format
cd build/snapshot; debuild -us -uc
.PHONY: clean
clean:
rm -rf build
rm -rf test/test-results
rm -rf test/tmp.*
debuild clean 2>/dev/null || true
xapers-0.9.0/NEWS.md 0000664 0000000 0000000 00000003430 13655206052 0014124 0 ustar 00root root 0000000 0000000 Xapers 0.8.2 (2017-08-08)
=======================
* Minor bug fixes
Xapers 0.8 (2017-08-02)
=======================
* Move to python 3
* lib: add missing get_authors method (thanks William Pettersson)
Xapers 0.7.1 (2017-01-04)
=======================
* Add ability to search sort results by year. Works in both cli
(--sort option) and curses interface ('o' to toggle sort order)
* fix to charset decoding in cryptoeprint source (thanks dkg)
Xapers 0.7 (2016-12-31)
=======================
* nci: various improvements:
* better buffer handling/redraw
* more commands
* improved prompts, with navigation, history, tab completion, etc.
* lib: fix query matching for tag terms: default AND instead of OR
* bibtex: updates for pybibtex 0.20
Xapers 0.6 (2015-01-10)
=======================
* lib: Document year is now indexed as a proper value, supporting both
'year:' binary and 'year:..' range searches. Will
require running 'restore' from the cli to re-index previously added
articles. Thanks to Rafael Laboissière for the contribution.
* lib: Much improved performance of Document prefixed term retrieval.
* cli: Much improved search output performance. Default output limit
of 20 has been removed.
* nci: Curses interface now loads entries dynamically, so search
results are no longer limited.
* nci: Cleaner results display. Document 'summary' has been removed,
but other information has been added, such as journal article, year,
file info, and document match information.
* nci: Extended navigation commands.
* sources: Now support PDF download from sources, if the source
supports it.
* sources: New IACR 'crytoeprint' source. Thanks to Daniel Kahn
Gillmor for the contribution.
* Other cleanup, bug fixes, and performance improvements.
xapers-0.9.0/README.md 0000664 0000000 0000000 00000020330 13655206052 0014303 0 ustar 00root root 0000000 0000000 Xapers - personal journal article management system
===================================================
Xapers is a personal document indexing system, geared towards academic
journal articles. Think of it as your own personal document search
engine, or a local cache of online libraries. It provides fast search
of document text and bibliographic data and simple document and bibtex
retrieval.
Document files (in PDF format) and source identifiers (e.g. DOI) are
parsed and indexed into a Xapian search engine [0]. Document text is
extracted from the PDF and fully indexed. Bibliographic information
downloaded from online libraries is indexed as prefixed search terms.
Existing bibtex databases can be easily imported as well, including
import of pdf files specified in Jabref/Mendeley format. Documents
can be arbitrarily tagged. Original document files are easily
retrievable from a simple curses search UI. The command line
interface allows for exporting bibtex [1] from arbitrary searches,
allowing seamless integration into LaTeX work flows.
Xapers provides source modules for some common online resources:
* doi: Digital Object Identifier (https://dx.doi.org/)
* arxiv: Open access e-print service (http://arxiv.org/)
* dcc: LIGO Document Control Center (https://dcc.ligo.org/)
* cryptoeprint: Cryptology ePrint Archive (https://eprint.iacr.org/)
Contributions of additional source interface modules is highly
encouraged. See the "Document Sources" section below for info on
creating new sources.
Xapers is heavily inspired by the notmuch mail indexing system [2].
* [0] http://www.xapian.org/
* [1] http://www.bibtex.org/
* [2] http://notmuchmail.org/
![xapers ncurses UI]](screenshot.png "xapers ncurses UI")
Contact
=======
Xapers was written by:
Jameson Graef Rollins
Xapers has a mailing list:
xapers@lists.mayfirst.org
https://lists.mayfirst.org/mailman/listinfo/xapers
We also hang out on IRC:
channel: #xapers
server: irc.freenode.net
Please submit all bug reports to the Debian bug tracking system (BTS):
https://bugs.debian.org/xapers
https://www.debian.org/Bugs/Reporting
Getting Xapers
==============
Source
------
Clone the repo:
$ git clone git://finestructure.net/xapers
$ cd xapers
Dependencies :
* python3
* python3-xapian - Python Xapian search engine bindings
* python3-pybtex - Python bibtex parser
* poppler-utils - PDF processing tools
* python3-pycurl - Python bindings to libcurl
Recommends (for curses UI) :
* python3-urwid - Python Urwid curses library
* xdg-utils - Desktop tools for opening files and URLs
* xclip - X clipboard support for copying document fields
On Debian:
$ sudo apt-get install python3-xapian python3-pybtex python3-pycurl poppler-utils python3-urwid xdg-utils xclip
Run the tests:
$ make test
Debian
------
Xapers is a part of Debian:
$ apt install xapers
Debian/Ubuntu snapshot packages can be easily made from the git
source. You can build the package from any branch but it requires an
up-to-date local branch of origin/debian, e.g.:
$ git branch debian origin/debian
Then:
$ sudo apt-get install build-essential devscripts pkg-config python-all-dev python-setuptools debhelper dpkg-dev fakeroot
$ make debian-snapshot
$ sudo dpkg -i build/xapers_0.8_amd64.deb
Using Xapers
============
See the included xapers(1) man page for detailed usage and information
on source modules and searching.
Command line interface
----------------------
The main interface to Xapers is the xapers command line utility. From
this interface you can import documents, search, tag, etc.
The "add" command allows importing or updating single documents. The
"import" command allows importing an entire bibtex databases (.bib
file). If the bibtex entries include "file" fields (ala. Mendeley or
Jabref), then those files are retrieved, indexed, and imported as
well.
Curses interface
----------------
The curses interface ("xapers show ...") provides a simple way to
display search results and retrieve files. Documents matching
searches are displayed with their bibliographic information. Document
tags can be manipulated, files and bibtex can be viewed, and source
URLs can be opened in a browser.
xapers-adder
------------
xapers-adder is a simple script that helps the adding of individual
documents to your Xapers database. It can be used e.g. as a PDF
handler in your favorite browser. It displays the PDF then presents
the user with the option to import the document into Xapers. The user
is prompted for any sources to retrieve and any initial tags to add.
If the source is known, bibtex is retrieved and indexed. The
resulting xapers entry for the document is displayed.
Development of more clever import methods is highly encouraged.
Python library
--------------
Xapers is a python library under the hood:
>>> import xapers
>>> db = xapers.Database('~/.xapers/docs')
>>> docs = db.search('tag:new')
>>> for doc in docs:
doc.add_tags(['foo'])
...
>>>
Development of new interfaces to the underlying library is highly
encouraged.
Document Sources
================
A Xapers "source" is a python module that describes how to interact
with a single online journal database, from which document files and
bibliographic data can be retrieved.
Sources are assigned unique prefixes (e.g. "doi"). Online libraries
associate unique document identifiers to individual documents
(e.g. "10.1364/JOSAA.29.002092"). A particular online document is
therefore described by a unique "source identifier", or "sid", which
can take two equivalent forms:
full URL http://dx.doi.org/10.1364/JOSAA.29.002092
: doi:10.1364/JOSAA.29.002092
CUSTOM SOURCE MODULES
---------------------
Custom source modules may be written to extend the base functionality
of Xapers. A source module is described by a single python module
(although it may import arbitrary other modules). The base name of
the module file is interpreted as the nickname or 'prefix' for the
source (e.g. if the module is named "doi.py" the source nickname will
be "doi").
The module should include the following properties and functions. If
any are missing, some xapers functionality may be undefined.
description: a brief string description of the source, e.g.:
description = "Digital Object Identifier"
url: base URL of source, e.g.:
url = 'http://dx.doi.org/'
url_format: a printf format string that produces a valid source URL
for a specified source identifier string, e.g.:
url_format = 'http://dx.doi.org/%s'
url_regex: a regular expression string that will match the source
identifier string from a given full URL, e.g.:
url_regex = 'http://dx.doi.org/(10\.\d{4,}[\w\d\:\.\-\/]+)'
scan_regex: a regular expression string that will match the source
identifier string in a scan of a documents plain text, e.g.:
scan_regex = '(?:doi|DOI)[\s\.\:]{0,2}' + id_regex
fetch_bibtex(id): a function that will return a bibtex string for a
source document specified by id.
fetch_file(id): a function that will return a (file_name, file_data)
tuple for a source document specified by id. File should be in
PDF format.
If your source does not provide bibliographic data directly in bibtex
format, the xapers.bibtex module has several helper functions for
creating bibtex strings from python dictionaries (data2bib) or json
objects (json2bib).
See existing source module contributed with the xapers source as
examples (lib/xapers/sources/).
Source module path
------------------
Once a custom source module has been created, place it
~/.xapers/sources. The module path can be overridden with the
XAPERS_SOURCE_PATH environment variable, which can be a
colon-separated list of directories to search for modules.
Testing
-------
Once a module is in place, use the xapers source* commands (sources,
source2url, source2bib, source2file) to test it's functionality. Your
new module should show up in the source listing with the "sources"
command, and should be able to print the relevant data with the other
commands.
Contributing
------------
If you think your module is stable and of general usefulness to the
community, please consider contributing it upstream. Thanks!
xapers-0.9.0/TODO 0000664 0000000 0000000 00000006623 13655206052 0013525 0 ustar 00root root 0000000 0000000 * unique bibtex keys (handle conflicting) (use id?)
* make 'date' alias of 'year'
* nci: translate tex in fields
* translate journal abbreviations in bibtex
* need *something* for docs without sources
* store at least URL
* "notes" for documents (editable txt file)
* add only opens writable db on doc.sync()
* db version
* rename files when being added?
* separate add and update commands
* set/get title, author, tags as data or values (is this faster?)
* gtk gui, with pdf thumbs:
"convert -thumbnail 500x -background white -alpha remove file.pdf[0] thumb.png"
([0] == pdf page)
* rework db/doc interface
* doc is just directory and xapian_doc
* db does write/index on sync
* db: can we force source prefixes to be OP_OR?
doc:
* add ability to remove source sid
* add ability to replace/remove file
* what to do with doc 'data' field:
* snippet/summary (current)
* data for fast retrieval?
* bib abstract
* custom annotations/notes
* nothing
cli:
* utilize meta-data pulled from parser
* update should re-pull from existing source if available
* export should produce full mirror of xapers document structure, with index
nci:
* add update/add commands
* how to test??
* meta for other fields (title, authors, year, etc)
* custom keybindings
* customizable palette
sources:
* add 'hdl': http://handle.net/proxy.html
parser:
* extract metadata from pdfs
* better handle parse errors
* better pdf parser (native python: https://gist.github.com/pazz/5455090)
* parsers for other document types
?
* emacs UI (need json/sexp output)
* store bib data in different format (json instead of bibtex)?
* clear old indexed terms when importing new file/bib?
* vcs integration (git of root)?
BUGS
====
* capitalized prefixed terms are not searchable
- dcc:T00000
- key:HaEA2009a
If the term is capitalized, a colon gets automatically added:
key:foo -> XBIB|foo
key:Foo -> XBIB|:Foo
* can not add --file when source contains '/'
* "xapers add --source=arXiv:hep-th/9806203 --file"
* nci choaks on unknown sources:
File "/usr/lib/python2.7/dist-packages/xapers/source.py", line 181, in get_source
raise SourceError("unknown source: %s" % name)
xapers.source.SourceError: unknown source: url
* uncaught QueryParserError:
servo:~ 1$ xapers show tag:lsc date:2016...
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/usr/lib/python2.7/dist-packages/xapers/__main__.py", line 330, in
nci.UI(cmd=args)
File "/usr/lib/python2.7/dist-packages/xapers/nci/ui.py", line 75, in __init__
self.newbuffer(cmd)
File "/usr/lib/python2.7/dist-packages/xapers/nci/ui.py", line 96, in newbuffer
buf = search.Search(self, query)
File "/usr/lib/python2.7/dist-packages/xapers/nci/search.py", line 370, in __init__
self.__set_search()
File "/usr/lib/python2.7/dist-packages/xapers/nci/search.py", line 377, in __set_search
count = self.ui.db.count(self.query)
File "/usr/lib/python2.7/dist-packages/xapers/database.py", line 318, in count
return self._search(query_string).get_matches_estimated()
File "/usr/lib/python2.7/dist-packages/xapers/database.py", line 285, in _search
query = self.query_parser.parse_query(query_string)
xapian.QueryParserError: Unknown range operation
servo:~ 1$
xapers-0.9.0/bin/ 0000775 0000000 0000000 00000000000 13655206052 0013576 5 ustar 00root root 0000000 0000000 xapers-0.9.0/bin/xapers-adder 0000775 0000000 0000000 00000001406 13655206052 0016104 0 ustar 00root root 0000000 0000000 #!/bin/bash -e
if [ -z "$1" ] || [[ "$1" == '--help' ]] || [[ "$1" == '-h' ]]; then
echo "usage: $(basename $0) [--noterm] " >&2
exit 1
fi
if [[ "$1" == '--noterm' ]]; then
term=false
shift
else
term=true
fi
infile="$1"
if [ ! -e "$infile" ] ;then
echo "File not found: $infile" >&2
exit 1
fi
# open the file with preferred application
nohup xdg-open "$infile" &>/dev/null &
cmd="
echo 'Xapers-adder'
echo '============'
echo 'Type C-c at any time to cancel...'
echo
while ! xapers add --file=\"$infile\" --tags=new --prompt --view; do
read -N1 -p 'ENTER to try again, or C-c to quit:' OK
done
"
if [[ "$term" == 'true' ]] ; then
exec x-terminal-emulator \
-T "xapers-adder" \
-e bash -c "$cmd"
else
eval "$cmd"
fi
xapers-0.9.0/man/ 0000775 0000000 0000000 00000000000 13655206052 0013601 5 ustar 00root root 0000000 0000000 xapers-0.9.0/man/man1/ 0000775 0000000 0000000 00000000000 13655206052 0014435 5 ustar 00root root 0000000 0000000 xapers-0.9.0/man/man1/xapers-adder.1 0000664 0000000 0000000 00000002542 13655206052 0017101 0 ustar 00root root 0000000 0000000 .\" xapers - journal article indexing system
.\"
.\" Copyright © 2013 Jameson Rollins
.\"
.\" Xapers 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.
.\"
.\" Xapers 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 http://www.gnu.org/licenses/ .
.\"
.\" Author: Jameson Rollins
.TH XAPERS 1
.SH NAME
xapers-adder \- "gui" to import individual documents into Xapers database
.SH SYNOPSIS
.B xapers-adder
.IR file.pdf
.SH DESCRIPTION
The specified PDF file is displayed (using \fBxdg-open\fR(1)), then a
terminal is opened (\fBx-terminal-emulator\fR(1)) executing the
following command:
xapers add \-\-file= \-\-tags=new \-\-prompt \-\-view
This program is useful to use as your PDF handler in your browser.
See \fBxapers\fR(1) for more information.
.SH CONTACT
Feel free to email the author:
Jameson Rollins
xapers-0.9.0/man/man1/xapers.1 0000664 0000000 0000000 00000021571 13655206052 0016027 0 ustar 00root root 0000000 0000000 .\" xapers - journal article indexing system
.\"
.\" Copyright © 2013 Jameson Rollins
.\"
.\" Xapers 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.
.\"
.\" Xapers 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 http://www.gnu.org/licenses/ .
.\"
.\" Author: Jameson Rollins
.TH XAPERS 1
.SH NAME
xapers \- personal journal article indexing system
.
.SH SYNOPSIS
.B xapers
.IR command " [" args " ...]"
.
.SH DESCRIPTION
Xapers is a personal document indexing system, geared towards academic
journal articles. It provides fast search of document text and
bibliographic data (synced from online libraries) and simple document
and bibtex retrieval.
Xapers takes as input document files (as PDF) and source identifiers.
Documents are copied into a local document store (~/.xapers/docs by
default) and text is extracted from the PDF and fully indexed into a
Xapian database. Source identifiers are used to download document
bibliographic data from online digital libraries (see \fBSOURCES\fR
below), which are then parsed and indexed to prefixed terms in the
database. The bibliographic data is also stored as bibtex in the
document store for easy retrieval. Documents can be arbitrarily
tagged.
A curses UI is provided for simple access to documents (see the
\fBview\fR command below). Xapers is ultimately a document indexing
library, though, so development of alternate user interfaces is
encouraged.
Underlying Xapers is the wonderful Xapian database/search engine. See
http://xapian.org/ for more information.
.
.SH MAIN COMMANDS
The following are the main xapers commands. See \fBSEARCH TERMS\fR
below for details of the supported syntax for .
.
.SS add [options] []
Add a document, or update an existing document. Must specify at least
one of \-\-file or \-\-source. If search terms are provided they must
match exactly one document and the matching document is updated with
the newly provided information. Available options:
.RS 4
.TP 4
.BR \-\-source=[|]
Source identifier for document. See \fBSOURCES\fR below. This may
also be a path to a file that contains a single bibtex entry.
.RE
.RS 4
.TP 4
.BR \-\-file[=]
Document file (as PDF) to add. Text of document will be extracted and
indexed. A copy of the file will be placed in the Xapers document
store. If provided without path, xapers will attempt to download file
from source, assuming source supports file downloads.
.RE
.RS 4
.TP 4
.BR \-\-tags=[,...]
Initial tags to apply to document. Multiple tags can be specified,
comma separated.
.RE
.RS 4
.TP 4
.BR \-\-prompt
Prompt user for source/file/tags, if not specified. When prompting
for source information input files are automatically scanned for
source IDs and found ids are displayed.
.RE
.RS 4
.TP 4
.BR \-\-view
View resulting entry in curses UI when done. See the \fBviewP\fR
command below for more info.
.RE
.
.SS import [options]
Import an existing bibtex database. Each bibtex entry will be added
as a new document. If bibtex key, or any sources found in bibtex,
match an existing document, that document is instead updated (this
makes the command effectively idempotent). Any "file" fields will be
parsed for document files to add. Files can be specified as a single
path, or in Mendeley/Jabref format. Available options:
.RS 4
.TP 4
.BR \-\-tags=[,...]
Tags to apply to all imported documents. Multiple tags can be
specified, comma separated.
.RE
.
.SS tag +|- [...] [--]
Add/remove tags from documents. '--' can be used to separate tagging
operations from search terms.
.
.SS search [options]
Search for documents in the database. Document information is printed
to stdout.
.RS 4
.TP 4
.BR \-\-output=[summary|bibtex|tags|sources|keys|files]
Specify document information to be output:
.B summary
outputs a single-line summary of the documents (default).
.B bibtex
outputs bibtex for all documents (if available).
.B tags
outputs all tags associated with documents.
.B sources
outputs all sources associated with documents.
.B keys
outputs all bibtex citation keys associated with documents.
.B files
outputs the full paths to all files associated with documents.
Default is
.B summary.
.RE
.RS 4
.TP 4
.BR \-\-limit=N
Limit number of results returned to N.
.RE
.
.SS bibtex
Short for "search \-\-output=bibtex ".
.
.SS count
Return a simple count of search results.
.
.SS view []
.SS show []
View search results in curses search UI. Documents matching search
are displayed with their bibliographic information and a short text
summary. It allows for manipulating document tags and for retrieved
for document files and source URLs for viewing (see
.B xdg-open(1)
for more info). Initial search terms can be provided, but further
searches can be performed from within the UI. While in the UI type
"?" for available commands.
NOTE: At the moment only the top 20 search results are displayed, due
to synchronous loading restrictions. This obviously needs to be
fixed.
.
.SS export
Copy PDF files of resulting documents into , named with
document titles when available.
.
.SS delete
Delete documents from the database. All document files will purged
from the document store.
.RS 4
.TP 4
.BR \-\-noprompt
Do not prompt to confirm deletion of documents.
.RE
.
.SS restore
Restore a database from existing xapers root.
.
.SH SOURCE COMMANDS
These commands provide access to some of the source module methods. See
\fBSOURCES\fR below.
.
.SS sources
List available sources.
.
.SS source2url [...]
Parse a source identifier string and print the corresponding source
URL.
.
.SS source2bib [...]
Retrieve bibtex from source for a specified URL or source id, and
write to stdout.
.
.SS source2file
Retrieve file from source for a specified URL or source id, and write
to stdout.
.
.SS scandoc
Scan a document file (PDF) for source IDs, and print and recognized
source ids to stdout.
.
.SH SOURCES
Sources are online databases from which document bibliographic data
can be retrieved. In Xapers, online libraries are assigned unique
prefixes. The online libraries associate unique document identifiers
to individual documents. See 'xapers sources' for a list of available
online sources.
Xapers recognizes document a source identifier, or \fBsid\fR, in two
forms:
full URL http://dx.doi.org/10.1364/JOSAA.29.002092
sid of form : doi:10.1364/JOSAA.29.002092
URLs are parsed into sources and source ids when recognized, and this
information is used to retrieve bibtex from the online library
databases. The sources and sids for a given document are stored as
prefixed terms in the Xapers database (see below).
.
.SH SEARCH TERMS
Xapers supports a common syntax for search terms.
Search can consist of free-form text and quoted phrases. Terms can be
combined with standard Boolean operators. All terms are combined with
a logical OR by default. Parentheses can be used to group operators,
but must be protect from shell interpretation. The string '*' will
match all documents in the database.
Additionally, the following prefixed terms are understood (where
indicate user-supplied values):
id: Xapers document ID
author: string in authors (also a:)
title: string in title (also t:)
tag: specific user tag
: specific source id (sid)
source: specific source
key: specific bibtex citation key
year: specific publication year (also y:)
year:.. publication year range (also y:)
year:..
year:..
Publication years must be four-digit integers.
See the following for more information on search terms:
http://xapian.org/docs/queryparser.html
.
.SH ENVIRONMENT
The following environment variables can be used to control the
behavior of xapers:
.
.SS XAPERS_ROOT
Location of the Xapers document store. Defaults to "~/.xapers/docs"
if not specified.
.
.SS XAPERS_SOURCE_PATH
Path specification for location of additional custom Xapers source
modules. Defaults to "~/.xapers/sources" if not specified.
.
.SH CONTACT
Feel free to email the author:
Jameson Rollins
xapers-0.9.0/screenshot.png 0000664 0000000 0000000 00000067006 13655206052 0015722 0 ustar 00root root 0000000 0000000 PNG
IHDR ; C5G- sBITO IDATx^3GbߡX|^`h
ԫ9RǏ_[ @UW. @ $(^@ p5_ {lWS&? @ 8KcK+;[Kڽ z-? @mcu[R)6]c!_
C ƋWR.TXwER&&kl-&B @ G`R9jjٓ*p磙> Tly-RHeYckz $0mH䍆4J;˲f}<:,L]ɒa30&ɽej@ 'U+4ij!:+^JI
%uX@}%_n89J=j5V! @ oMkA G$!@7&t,oe˥ w!|Ye-S} otavڭ^ޥYl͔*kgV! @ x#Jc~(im2LT{lʽFsT5>yM);Hm~Uyl # @ K`Ry
_jVU