Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: libchewing
Upstream-Contact: chewing development team <chewing-devel@googlegroups.com>
Source: https://github.com/chewing/libchewing

Files: *
Copyright: 2004-2014 chewing development team <chewing-devel@googlegroups.com>
License: LGPL-2.1

Files: debian/*
Copyright: 2004-2014 IME Packaging Team <pkg-ime-devel@lists.alioth.debian.org>
License: LGPL-2.1

Files: cmake/FindCurses.cmake
Copyright: 2000-2011 Kitware, Inc., Insight Software Consortium
License: BSD-3-clause

Files: thirdparty/sqlite-amalgamation/*
Copyright: D. Richard Hipp <drh@hwaci.com>
License: public-domain
 All of the code and documentation in SQLite has been dedicated to the public
 domain by the authors. All code authors, and representatives of the companies
 they work for, have signed affidavits dedicating their contributions to the
 public domain and originals of those signed affidavits are stored in a firesafe
 at the main offices of Hwaci. Anyone is free to copy, modify, publish, use,
 compile, sell, or distribute the original SQLite code, either in source code
 form or as a compiled binary, for any purpose, commercial or non-commercial,
 and by any means.
 .
 The previous paragraph applies to the deliverable code and documentation in
 SQLite - those parts of the SQLite library that you actually bundle and ship
 with a larger application. Some scripts used as part of the build process (for
 example the "configure" scripts generated by autoconf) might fall under other
 open-source licenses. Nothing from these build scripts ever reaches the final
 deliverable SQLite library, however, and so the licenses associated with those
 scripts should not be a factor in assessing your rights to copy and use the
 SQLite library.
 .
 All of the deliverable code in SQLite has been written from scratch. No code
 has been taken from other projects or from the open internet. Every line of
 code can be traced back to its original author, and all of those authors have
 public domain dedications on file. So the SQLite code base is clean and is
 uncontaminated with licensed code from other projects.

License: LGPL-2.1
 This library is free software; you can redistribute it and/or
 modify it under the terms of the GNU Lesser General Public
 License as published by the Free Software Foundation; either
 version 2.1 of the License, or (at your option) any later version.
 .
 This library 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
 Lesser General Public License for more details.
 .
 On Debian system, the complete text of GNU Lesser General Public License can
 be found in "/usr/share/common-licenses/LGPL-2.1".

License: BSD-3-clause
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
 1. Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.
 2. Redistributions in binary form must reproduce the above copyright
    notice, this list of conditions and the following disclaimer in the
    documentation and/or other materials provided with the distribution.
 3. Neither the name of the University nor the names of its contributors
    may be used to endorse or promote products derived from this software
    without specific prior written permission.
 .
 THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 SUCH DAMAGE.