Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
GNOME
libgda
Commits
f307a191
Commit
f307a191
authored
Jul 22, 2001
by
Rodrigo Moya
Browse files
Use pkg-config
parent
ddb5dbe8
Changes
567
Expand all
Hide whitespace changes
Inline
Side-by-side
.cvsignore
deleted
100644 → 0
View file @
ddb5dbe8
intl
aclocal.m4
config.guess
config.sub
ltconfig
ltmain.sh
config.h.in
stamp-h.in
Makefile.in
Makefile
configure
config.log
config.h
config.cache
libtool
config.status
stamp-h
libgda.spec
stamp.h
xml-i18n-update
xml-i18n-merge
xml-i18n-extract
xml-i18n-update.in
xml-i18n-merge.in
xml-i18n-extract.in
control-stamp
configure-stamp
build-stamp
install-sh
missing
mkinstalldirs
INSTALL
ABOUT-NLS
deleted
100644 → 0
View file @
ddb5dbe8
Notes
on
the
Free
Translation
Project
*************************************
Free
software
is
going
international
! The Free Translation Project
is
a
way
to
get
maintainers
of
free
software
,
translators
,
and
users
all
together
,
so
that
will
gradually
become
able
to
speak
many
languages
.
A
few
packages
already
provide
translations
for
their
messages
.
If
you
found
this
`
ABOUT
-
NLS
' file inside a distribution, you may
assume that the distributed package does use GNU `gettext'
internally
,
itself
available
at
your
nearest
GNU
archive
site
.
But
you
do
_not_
need
to
install
GNU
`
gettext
' prior to configuring, installing or using
this package with messages translated.
Installers will find here some useful hints. These notes also
explain how users should proceed for getting the programs to use the
available translations. They tell how people wanting to contribute and
work at translations should contact the appropriate team.
When reporting bugs in the `intl/'
directory
or
bugs
which
may
be
related
to
internationalization
,
you
should
tell
about
the
version
of
`
gettext
' which is used. The information can be found in the
`intl/VERSION'
file
,
in
internationalized
packages
.
Quick
configuration
advice
==========================
If
you
want
to
exploit
the
full
power
of
internationalization
,
you
should
configure
it
using
./
configure
--
with
-
included
-
gettext
to
force
usage
of
internationalizing
routines
provided
within
this
package
,
despite
the
existence
of
internationalizing
capabilities
in
the
operating
system
where
this
package
is
being
installed
.
So
far
,
only
the
`
gettext
' implementation in the GNU C library version 2 provides as
many features (such as locale alias, message inheritance, automatic
charset conversion or plural form handling) as the implementation here.
It is also not possible to offer this additional functionality on top
of a `catgets'
implementation
.
Future
versions
of
GNU
`
gettext
' will
very likely convey even more functionality. So it might be a good idea
to change to GNU `gettext'
as
soon
as
possible
.
So
you
need
_not_
provide
this
option
if
you
are
using
GNU
libc
2
or
you
have
installed
a
recent
copy
of
the
GNU
gettext
package
with
the
included
`
libintl
'.
INSTALL Matters
===============
Some packages are "localizable" when properly installed; the
programs they contain can be made to speak your own native language.
Most such packages use GNU `gettext'
.
Other
packages
have
their
own
ways
to
internationalization
,
predating
GNU
`
gettext
'.
By default, this package will be installed to allow translation of
messages. It will automatically detect whether the system already
provides the GNU `gettext'
functions
.
If
not
,
the
GNU
`
gettext
' own
library will be used. This library is wholly contained within this
package, usually in the `intl/'
subdirectory
,
so
prior
installation
of
the
GNU
`
gettext
' package is _not_ required. Installers may use
special options at configuration time for changing the default
behaviour. The commands:
./configure --with-included-gettext
./configure --disable-nls
will respectively bypass any pre-existing `gettext'
to
use
the
internationalizing
routines
provided
within
this
package
,
or
else
,
_totally_
disable
translation
of
messages
.
When
you
already
have
GNU
`
gettext
' installed on your system and run
configure without an option for your new package, `configure'
will
probably
detect
the
previously
built
and
installed
`
libintl
.
a
' file and
will decide to use this. This might be not what is desirable. You
should use the more recent version of the GNU `gettext'
library
.
I
.
e
.
if
the
file
`
intl
/
VERSION
' shows that the library which comes with this
package is more recent, you should use
./configure --with-included-gettext
to prevent auto-detection.
The configuration process will not test for the `catgets'
function
and
therefore
it
will
not
be
used
.
The
reason
is
that
even
an
emulation
of
`
gettext
' on top of `catgets'
could
not
provide
all
the
extensions
of
the
GNU
`
gettext
' library.
Internationalized packages have usually many `po/LL.po'
files
,
where
LL
gives
an
ISO
639
two
-
letter
code
identifying
the
language
.
Unless
translations
have
been
forbidden
at
`
configure
' time by using the
`--disable-nls'
switch
,
all
available
translations
are
installed
together
with
the
package
.
However
,
the
environment
variable
`
LINGUAS
'
may be set, prior to configuration, to limit the installed set.
`LINGUAS'
should
then
contain
a
space
separated
list
of
two
-
letter
codes
,
stating
which
languages
are
allowed
.
Using
This
Package
==================
As
a
user
,
if
your
language
has
been
installed
for
this
package
,
you
only
have
to
set
the
`
LANG
' environment variable to the appropriate
`LL_CC'
combination
.
Here
`
LL
' is an ISO 639 two-letter language code,
and `CC'
is
an
ISO
3166
two
-
letter
country
code
.
For
example
,
let
's
suppose that you speak German and live in Germany. At the shell
prompt, merely execute `setenv LANG de_DE'
(
in
`
csh
'),
`export LANG; LANG=de_DE'
(
in
`
sh
') or `export LANG=de_DE'
(
in
`
bash
').
This can be done from your `.login'
or
`.
profile
' file, once and for
all.
You might think that the country code specification is redundant.
But in fact, some languages have dialects in different countries. For
example, `de_AT'
is
used
for
Austria
,
and
`
pt_BR
' for Brazil. The
country code serves to distinguish the dialects.
Not all programs have translations for all languages. By default, an
English message is shown in place of a nonexistent translation. If you
understand other languages, you can set up a priority list of languages.
This is done through a different environment variable, called
`LANGUAGE'
.
GNU
`
gettext
' gives preference to `LANGUAGE'
over
`
LANG
'
for the purpose of message handling, but you still need to have `LANG'
set
to
the
primary
language
;
this
is
required
by
other
parts
of
the
system
libraries
.
For
example
,
some
Swedish
users
who
would
rather
read
translations
in
German
than
English
for
when
Swedish
is
not
available
,
set
`
LANGUAGE
' to `sv:de'
while
leaving
`
LANG
' to `sv_SE'
.
In
the
`
LANGUAGE
' environment variable, but not in the `LANG'
environment
variable
,
`
LL_CC
' combinations can be abbreviated as `LL'
to
denote
the
language
's main dialect. For example, `de'
is
equivalent
to
`
de_DE
' (German as spoken in Germany), and `pt'
to
`
pt_PT
'
(Portuguese as spoken in Portugal) in this context.
Translating Teams
=================
For the Free Translation Project to be a success, we need interested
people who like their own language and write it well, and who are also
able to synergize with other translators speaking the same language.
Each translation team has its own mailing list. The up-to-date list of
teams can be found at the Free Translation Project'
s
homepage
,
`
http
://
www
.
iro
.
umontreal
.
ca
/
contrib
/
po
/
HTML
/
', in the "National teams"
area.
If you'
d
like
to
volunteer
to
_work_
at
translating
messages
,
you
should
become
a
member
of
the
translating
team
for
your
own
language
.
The
subscribing
address
is
_not_
the
same
as
the
list
itself
,
it
has
`-
request
' appended. For example, speakers of Swedish can send a
message to `sv-request@li.org'
,
having
this
message
body
:
subscribe
Keep
in
mind
that
team
members
are
expected
to
participate
_actively_
in
translations
,
or
at
solving
translational
difficulties
,
rather
than
merely
lurking
around
.
If
your
team
does
not
exist
yet
and
you
want
to
start
one
,
or
if
you
are
unsure
about
what
to
do
or
how
to
get
started
,
please
write
to
`
translation
@
iro
.
umontreal
.
ca
' to reach the
coordinator for all translator teams.
The English team is special. It works at improving and uniformizing
the terminology in use. Proven linguistic skill are praised more than
programming skill, here.
Available Packages
==================
Languages are not equally supported in all packages. The following
matrix shows the current state of internationalization, as of May 2001.
The matrix shows, in regard of each package, for which languages PO
files have been submitted to translation coordination, with a
translation percentage of at least 50%.
Ready PO files bg cs da de el en eo es et fi fr gl hr id it
+----------------------------------------------+
a2ps | [] [] |
bash | [] [] [] [] |
bison | [] [] [] [] |
clisp | [] [] [] [] |
cpio | [] [] [] [] |
diffutils | [] [] [] [] [] [] [] |
enscript | [] [] |
error | [] |
fileutils | [] [] [] [] [] [] [] |
findutils | [] [] [] [] [] [] [] [] |
flex | [] [] [] |
gawk | |
gcal | |
gcc | [] |
gettext | [] [] [] [] [] [] [] [] [] |
gnupg | [] [] [] [] [] |
grep | [] [] [] |
hello | [] [] [] [] [] [] [] [] [] |
id-utils | [] [] |
indent | [] [] [] [] [] |
libc | [] [] [] [] [] [] [] [] |
lilypond | |
lynx | [] [] [] |
m4 | [] [] [] [] [] [] [] |
make | [] [] [] [] |
parted | [] [] |
ptx | [] [] [] [] [] [] [] |
python | |
recode | [] [] [] [] [] [] [] [] |
sed | [] [] [] [] [] [] [] [] [] |
sh-utils | [] [] [] [] [] [] [] [] [] |
sharutils | [] [] [] [] [] [] [] |
soundtracker | |
sp | |
tar | [] [] [] [] [] [] [] [] |
texinfo | [] [] [] [] |
textutils | [] [] [] [] [] [] [] |
util-linux | [] |
wdiff | [] [] [] [] [] [] [] |
wget | [] [] [] [] [] [] [] [] [] |
+----------------------------------------------+
bg cs da de el en eo es et fi fr gl hr id it
0 14 21 27 10 1 8 20 13 1 28 17 0 9 11
ja ko lv nl no pl pt pt_BR ru sk sl sv tr zh
+----------------------------------------------+
a2ps | [] [] [] | 5
bash | | 4
bison | [] [] [] | 7
clisp | [] | 5
cpio | [] [] [] [] [] | 9
diffutils | [] [] [] | 10
enscript | [] [] [] | 5
error | | 1
fileutils | [] [] [] [] [] [] [] [] [] | 16
findutils | [] [] [] [] [] [] | 14
flex | [] [] [] | 6
gawk | | 0
gcal | | 0
gcc | [] | 2
gettext | [] [] [] [] [] [] [] [] [] [] | 19
gnupg | [] [] [] | 8
grep | | 3
hello | [] [] [] [] [] [] [] [] | 17
id-utils | [] [] [] | 5
indent | [] [] [] [] [] [] [] | 12
libc | [] [] [] [] [] [] [] | 15
lilypond | [] | 1
lynx | [] [] [] [] [] | 8
m4 | [] [] [] [] [] | 12
make | [] [] [] [] [] | 9
parted | [] [] [] | 5
ptx | [] [] [] [] [] [] | 13
python | | 0
recode | [] [] [] | 11
sed | [] [] [] [] [] [] [] | 16
sh-utils | [] [] [] [] [] [] [] [] [] [] | 19
sharutils | [] [] [] [] | 11
soundtracker | | 0
sp | | 0
tar | [] [] [] [] [] [] [] [] | 16
texinfo | [] [] | 6
textutils | [] [] [] [] [] [] [] [] | 15
util-linux | [] | 2
wdiff | [] [] [] [] [] | 12
wget | [] [] [] [] [] [] [] [] | 17
+----------------------------------------------+
29 teams ja ko lv nl no pl pt pt_BR ru sk sl sv tr zh
40 domains 18 8 0 23 6 16 1 15 26 9 9 20 2 3 336
Some counters in the preceding matrix are higher than the number of
visible blocks let us expect. This is because a few extra PO files are
used for implementing regional variants of languages, or language
dialects.
For a PO file in the matrix above to be effective, the package to
which it applies should also have been internationalized and
distributed as such by its maintainer. There might be an observable
lag between the mere existence a PO file and its wide availability in a
distribution.
If May 2001 seems to be old, you may fetch a more recent copy of
this `ABOUT-NLS'
file
on
most
GNU
archive
sites
.
The
most
up
-
to
-
date
matrix
with
full
percentage
details
can
be
found
at
`
http
://
www
.
iro
.
umontreal
.
ca
/
contrib
/
po
/
HTML
/
matrix
.
html
'.
Using `gettext'
in
new
packages
===============================
If
you
are
writing
a
freely
available
program
and
want
to
internationalize
it
you
are
welcome
to
use
GNU
`
gettext
' in your
package. Of course the GNU General Public License applies to your
sources from then if you include `gettext'
directly
in
your
distribution
on
but
since
you
are
writing
free
software
anyway
this
is
no
restriction
.
Once
the
sources
are
change
appropriately
and
the
setup
can
handle
to
use
of
`
gettext
' the only thing missing are the translations. The Free
Translation Project is also available for packages which are not
developed inside the GNU project. Therefore the information given above
applies also for every other Free Software Project. Contact
`translation@iro.umontreal.ca'
to
make
the
`.
pot
' files available to
the translation teams.
AUTHORS
deleted
100644 → 0
View file @
ddb5dbe8
Michael Lausch <michael@lausch.at> (founder of the project, libgda-client, gda-odbc, gda-mysql)
Rodrigo Moya <rodrigo@gnome-db.org> (libgda-common, libgda-client, libgda-server, report, gda-postgres, gda-mysql)
Vivien Malerba <malerba@gnome-db.org> (gda-postgres, libgda-common, queries)
Stephan Heinze <stephan.heinze@xcom.de> (gda-oracle)
Nick Gorham <nick@lurcher.org> (gda-odbc)
Chris Wiegand <cwiegand@urgentmail.com> (C++ bindings)
Alvaro del Castillo <acs@barrapunto.com> (gda-mdb)
Akira TAGOH <at@ue-spacy.com> (gda-ldap)
Carlos Perell Marn <carlos@gnome-db.org> (report)
Reinhard Muller <reinhard@gnue.org> (libgda-client, libgda-server, libgda-common)
Holger Thon <holger.thon@gnome-db.org> (gda-primebase, gda-sybase, gda-tds)
Gerhard Dieringer <gdieringer@compuserve.com> (report, queries)
COPYING
deleted
100644 → 0
View file @
ddb5dbe8
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) 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
this service 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 make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. 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.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
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
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the 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 a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE 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.
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
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
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