Third Party Software & Schriftarten im WorksheetCrafter
==============================================================================
A.) Software
1.) The Qt GUI Toolkit Version 5.15.14 ( LGPL-3.0, Anpassungen:
https://worksheetcrafter.com/_supportData/gpl-modified-sources/Qt.tar.xz )
2.) Tiny Mersenne Twister ( tinymt ) Version 1.1.1
3.) Hyphen Version 2.8.6 ( MPL 2.0, Anpassungen:
http://getschoolcraft.com/_supportData/gpl-modified-sources/Hyphen.zip )
4.) Hunspell Version 1.5.4 ( MPL 2.0, Anpassungen:
http://getschoolcraft.com/_supportData/gpl-modified-sources/Hunspell.zip )
5.) Qwt MathML Renderer ( Qwt License Version 1.0 )
6.) QuaZIP (LGPL-v2.1)
7.) CppUnit 1.12.1 ( LGPL-v2.1 )
8.) RTFtoHTML 0.1.0 ( LGPL-v2.1,
http://getschoolcraft.com/_supportData/gpl-modified-sources/Rtf2Html.zip )
9.) SigSlot (Public Domain)
10.) VisualLeakDetector 2.0.0 ( LGPL-v2.1 )
11.) TinyXML ( zlib License )
12.) Nod ( MIT )
13.) Easy Encryption ( MIT )
14.) QR Code generator library ( MIT )
15.) ZipZap ( BSD 2-Clause "Simplified" License )
16.) LAME via BASSenc_MP3 ( LGPL-v2.0,
http://getschoolcraft.com/_supportData/gpl-modified-sources/bassenc_mp3-source.zip )
17.) utf8proc ( MIT )
18.) UTF8-CPP: UTF-8 with C++ in a Portable Way 4.0.5 ( Boost Software License 1.0 )
19.) Json for Modern C++ (MIT)
20.) libzip 1.10.1
21.) zlib 1.3.1
22.) ICU (UNICODE LICENSE V3)
23.) cpp-httplib 0.25.0 ( MIT )
100.) GNU GENERAL PUBLIC LICENSE Version 3
101.) GNU LESSER GENERAL PUBLIC LICENSE Version 2.1
102.) GNU LESSER GENERAL PUBLIC LICENSE Version 3.0
103.) MOZILLA PUBLIC LICENSE Version 2.0
104.) Boost Software License 1.0
B.) Schriftarten
50.) "ABeeZee" von Anja Meiners ( SIL Open Font License )
51.) "Grundschrift" von Christian Urf ( eigene Lizenz )
52.) "Gruschudru" von Florian Emrich, die wiederum auf der Schrift
"Andika Basic" von Annie Olsen basiert ( SIL Open Font License )
52.1) FONTLOG
52.2) OFL Andika Basic Regular Release 1.0
52.3) README - Andika Basic Regular Release 1.0
52.4) AndikaBasicR-FAQ-KI
53.) "Fibel Nord Mitlaute", "Fibel Nord Selbstlaute", "Fibel Nord Halb2"
und "Fibel Nord Zebra" von Ruben Rimmler und Peter Wiegel
54.) "LRS Nord Fenster" und "LRS ABC-Nummer2" von Ruben Rimmler
55.) "OpenDyslexic" Version 2 von Abbie Gonzalez ( SIL Open Font License )
500.) SIL OPEN FONT LICENSE Version 1.0 - 22 November 2005
501.) SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
503.) Frequently Asked Questions about the SIL Open Font License (OFL)
==============================================================================
1.) The Qt GUI Toolkit 5.15.14
==============================================================================
GNU LESSER GENERAL PUBLIC LICENSE
The Qt Toolkit is Copyright (C) 2017 The Qt Company Ltd.
Contact: https://www.qt.io/licensing
You may use, distribute and copy the Qt GUI Toolkit under the terms of
GNU Lesser General Public License version 3, which supplements GNU General
Public License Version 3. Both of the licenses are displayed below.
==============================================================================
2.) Tiny Mersenne Twister(tinymt) Version 1.1.1
==============================================================================
Copyright (c) 2011, 2013 Mutsuo Saito, Makoto Matsumoto,
Hiroshima University and The University of Tokyo.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* 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.
* Neither the name of the Hiroshima 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 COPYRIGHT HOLDERS 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 COPYRIGHT
OWNER 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.
==============================================================================
3.) Hyphen Version 2.8.6
==============================================================================
GPL 2.0/LGPL 2.1/MPL 1.1 tri-license
The contents of this software may be used under the terms of
the GNU General Public License Version 2 or later (the "GPL"), or
the GNU Lesser General Public License Version 2.1 or later (the "LGPL",
see COPYING.LGPL) or the Mozilla Public License Version 1.1 or later
(the "MPL", see COPYING.MPL).
The Plain TeX hyphenation tables "hyphen.tex" by Donald E. Knuth
has a non MPL/LGPL compatible license, but freely redistributable:
"Unlimited copying and redistribution of this file are permitted as long
as this file is not modified. Modifications are permitted, but only if
the resulting file is not named hyphen.tex."
Software distributed under these licenses is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the licences
for the specific language governing rights and limitations under the licenses.
==============================================================================
4.) Hunspell Version 1.5.4
==============================================================================
Hunspell spell checker and morphological analyser library
Documentation, tests, examples: http://hunspell.github.io/
Author of Hunspell:
László Németh (nemethl (at) gyorsposta.hu)
Hunspell based on OpenOffice.org's Myspell. MySpell's author:
Kevin Hendricks (kevin.hendricks (at) sympatico.ca)
License: GPL 2.0/LGPL 2.1/MPL 1.1 tri-license
The contents of this library may be used under the terms of
the GNU General Public License Version 2 or later (the "GPL"), or
the GNU Lesser General Public License Version 2.1 or later (the "LGPL",
see http://gnu.org/copyleft/lesser.html) or the Mozilla Public License
Version 1.1 or later (the "MPL", see http://mozilla.org/MPL/MPL-1.1.html).
Software distributed under these licenses is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the licences
for the specific language governing rights and limitations under the licenses.
==============================================================================
5.) Qwt MathML Renderer
==============================================================================
Qwt License
Version 1.0, January 1, 2003
The Qwt library and included programs are provided under the terms
of the GNU LESSER GENERAL PUBLIC LICENSE (LGPL) with the following
exceptions:
1. Widgets that are subclassed from Qwt widgets do not
constitute a derivative work.
2. Static linking of applications and widgets to the
Qwt library does not constitute a derivative work
and does not require the author to provide source
code for the application or widget, use the shared
Qwt libraries, or link their applications or
widgets against a user-supplied version of Qwt.
If you link the application or widget to a modified
version of Qwt, then the changes to Qwt must be
provided under the terms of the LGPL in sections
1, 2, and 4.
3. You do not have to provide a copy of the Qwt license
with programs that are linked to the Qwt library, nor
do you have to identify the Qwt license in your
program or documentation as required by section 6
of the LGPL.
However, programs must still identify their use of Qwt.
The following example statement can be included in user
documentation to satisfy this requirement:
[program/widget] is based in part on the work of
the Qwt project (http://qwt.sf.net).
==============================================================================
6.) QuaZIP
==============================================================================
QuaZIP is the C++ wrapper for Gilles Vollant's ZIP/UNZIP package
(AKA minizip) using Trolltech's Qt library.
Copyright (C) 2005-2012 Sergey A. Tachenov
This program 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 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 Lesser
General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with this program; if not, write to the Free Software Foundation,
Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Original ZIP package is copyrighted by Gilles Vollant, see
quazip/(un)zip.h files for details, basically it's zlib license.
==============================================================================
7.) CppUnit 1.12.1
==============================================================================
CppUnit --- The C++ Unit Test Library
-------------------------------------
http://cppunit.sourceforge.net
CppUnit is the C++ port of the famous JUnit framework for unit
testing.
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.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
==============================================================================
8.) RTFtoHTML 0.1.0
==============================================================================
This is RTF to HTML converter version 0.1.0.
Copyright (C) 2003 Valentin Lavrinenko, vlavrinenko@users.sourceforge.net
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.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
==============================================================================
9.) SigSlot
==============================================================================
Written by Sarah Thompson (sarah@telergy.com) 2002.
License: Public domain. You are free to use this code however you like,
with the proviso that the author takes on no responsibility
or liability for any use.
==============================================================================
10.) VisualLeakDetector 2.0.0
==============================================================================
Copyright © 2005-2017 VLD Team
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.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
==============================================================================
11.) TinyXML
==============================================================================
TinyXML is released under the zlib license:
This software is provided 'as-is', without any express or implied warranty.
In no event will the authors be held liable for any damages arising from the
use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim
that you wrote the original software. If you use this software in a product,
an acknowledgment in the product documentation would be appreciated but is
not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
==============================================================================
12.) Nod
==============================================================================
Copyright (c) 2015 Fredrik Berggren
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE SOFTWARE.
==============================================================================
13.) Easy Encryption
==============================================================================
Copyright (c) 2018 Philippe Rémy
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
==============================================================================
14.) QR Code generator library
==============================================================================
Copyright © 2022 Project Nayuki. (MIT License)
https://www.nayuki.io/page/qr-code-generator-library
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
The Software is provided "as is", without warranty of any kind, express or
implied, including but not limited to the warranties of merchantability,
fitness for a particular purpose and noninfringement. In no event shall the
authors or copyright holders be liable for any claim, damages or other
liability, whether in an action of contract, tort or otherwise, arising from,
out of or in connection with the Software or the use or other dealings in
the Software.
==============================================================================
15.) ZipZap
==============================================================================
Copyright (c) 2012, Pixelglow Software.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
* 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.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
==============================================================================
17.) utf8proc
==============================================================================
Copyright (c) 2014-2021 Steven G. Johnson, Jiahao Chen, Peter Colberg,
Tony Kelman, Scott P. Jones, and other contributors.
Copyright (c) 2009 Public Software Group e. V., Berlin, Germany
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
==============================================================================
18.) UTF8-CPP: UTF-8 with C++ in a Portable Way
==============================================================================
Copyright 2006 Nemanja Trifunovic
Permission is hereby granted, free of charge, to any person or organization
obtaining a copy of the software and accompanying documentation covered by
this license (the "Software") to use, reproduce, display, distribute,
execute, and transmit the Software, and to prepare derivative works of the
Software, and to permit third-parties to whom the Software is furnished to
do so, all subject to the following:
The copyright notices in the Software and this entire statement, including
the above license grant, this restriction and the following disclaimer,
must be included in all copies of the Software, in whole or in part, and
all derivative works of the Software, unless such copies or derivative
works are solely in the form of machine-executable object code generated by
a source language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
==============================================================================
19.) Json for Modern C++
==============================================================================
MIT License
Copyright (c) 2013-2022 Niels Lohmann
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
==============================================================================
20.) libzip 1.10.1
==============================================================================
Copyright (C) 1999-2020 Dieter Baron and Thomas Klausner
The authors can be contacted at
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. The names of the authors may not be used to endorse or promote
products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHORS ``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 AUTHORS 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.
==============================================================================
21.) zlib 1.3.1
==============================================================================
Copyright notice:
(C) 1995-2022 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any damages
arising from the use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly Mark Adler
jloup@gzip.org madler@alumni.caltech.edu
==============================================================================
22.) ICU
==============================================================================
UNICODE LICENSE V3
COPYRIGHT AND PERMISSION NOTICE
Copyright © 2016-2024 Unicode, Inc.
NOTICE TO USER: Carefully read the following legal agreement. BY
DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING DATA FILES, AND/OR
SOFTWARE, YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE
TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE, DO NOT
DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA FILES OR SOFTWARE.
Permission is hereby granted, free of charge, to any person obtaining a
copy of data files and any associated documentation (the "Data Files") or
software and any associated documentation (the "Software") to deal in the
Data Files or Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, and/or sell
copies of the Data Files or Software, and to permit persons to whom the
Data Files or Software are furnished to do so, provided that either (a)
this copyright and permission notice appear with all copies of the Data
Files or Software, or (b) this copyright and permission notice appear in
associated Documentation.
THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF
THIRD PARTY RIGHTS.
IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE
BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES,
OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE DATA
FILES OR SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall
not be used in advertising or otherwise to promote the sale, use or other
dealings in these Data Files or Software without prior written
authorization of the copyright holder.
SPDX-License-Identifier: Unicode-3.0
----------------------------------------------------------------------
Third-Party Software Licenses
This section contains third-party software notices and/or additional
terms for licensed third-party software components included within ICU
libraries.
----------------------------------------------------------------------
ICU License - ICU 1.8.1 to ICU 57.1
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2016 International Business Machines Corporation and others
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of
the Software and that both the above copyright notice(s) and this
permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder
shall not be used in advertising or otherwise to promote the sale, use
or other dealings in this Software without prior written authorization
of the copyright holder.
All trademarks and registered trademarks mentioned herein are the
property of their respective owners.
----------------------------------------------------------------------
Chinese/Japanese Word Break Dictionary Data (cjdict.txt)
# The Google Chrome software developed by Google is licensed under
# the BSD license. Other software included in this distribution is
# provided under other licenses, as set forth below.
#
# The BSD License
# http://opensource.org/licenses/bsd-license.php
# Copyright (C) 2006-2008, Google Inc.
#
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#
# Redistributions of source code must retain the above copyright notice,
# this list of conditions and the following disclaimer.
# 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.
# Neither the name of Google Inc. 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 COPYRIGHT HOLDERS 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 COPYRIGHT OWNER 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.
#
#
# The word list in cjdict.txt are generated by combining three word lists
# listed below with further processing for compound word breaking. The
# frequency is generated with an iterative training against Google web
# corpora.
#
# * Libtabe (Chinese)
# - https://sourceforge.net/project/?group_id=1519
# - Its license terms and conditions are shown below.
#
# * IPADIC (Japanese)
# - http://chasen.aist-nara.ac.jp/chasen/distribution.html
# - Its license terms and conditions are shown below.
#
# ---------COPYING.libtabe ---- BEGIN--------------------
#
# /*
# * Copyright (c) 1999 TaBE Project.
# * Copyright (c) 1999 Pai-Hsiang Hsiao.
# * All rights reserved.
# *
# * Redistribution and use in source and binary forms, with or without
# * modification, are permitted provided that the following conditions
# * are met:
# *
# * . Redistributions of source code must retain the above copyright
# * notice, this list of conditions and the following disclaimer.
# * . 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.
# * . Neither the name of the TaBE Project 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 COPYRIGHT HOLDERS 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.
# */
#
# /*
# * Copyright (c) 1999 Computer Systems and Communication Lab,
# * Institute of Information Science, Academia
# * Sinica. All rights reserved.
# *
# * Redistribution and use in source and binary forms, with or without
# * modification, are permitted provided that the following conditions
# * are met:
# *
# * . Redistributions of source code must retain the above copyright
# * notice, this list of conditions and the following disclaimer.
# * . 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.
# * . Neither the name of the Computer Systems and Communication Lab
# * 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 COPYRIGHT HOLDERS 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.
# */
#
# Copyright 1996 Chih-Hao Tsai @ Beckman Institute,
# University of Illinois
# c-tsai4@uiuc.edu http://casper.beckman.uiuc.edu/~c-tsai4
#
# ---------------COPYING.libtabe-----END--------------------------------
#
#
# ---------------COPYING.ipadic-----BEGIN-------------------------------
#
# Copyright 2000, 2001, 2002, 2003 Nara Institute of Science
# and Technology. All Rights Reserved.
#
# Use, reproduction, and distribution of this software is permitted.
# Any copy of this software, whether in its original form or modified,
# must include both the above copyright notice and the following
# paragraphs.
#
# Nara Institute of Science and Technology (NAIST),
# the copyright holders, disclaims all warranties with regard to this
# software, including all implied warranties of merchantability and
# fitness, in no event shall NAIST be liable for
# any special, indirect or consequential damages or any damages
# whatsoever resulting from loss of use, data or profits, whether in an
# action of contract, negligence or other tortuous action, arising out
# of or in connection with the use or performance of this software.
#
# A large portion of the dictionary entries
# originate from ICOT Free Software. The following conditions for ICOT
# Free Software applies to the current dictionary as well.
#
# Each User may also freely distribute the Program, whether in its
# original form or modified, to any third party or parties, PROVIDED
# that the provisions of Section 3 ("NO WARRANTY") will ALWAYS appear
# on, or be attached to, the Program, which is distributed substantially
# in the same form as set out herein and that such intended
# distribution, if actually made, will neither violate or otherwise
# contravene any of the laws and regulations of the countries having
# jurisdiction over the User or the intended distribution itself.
#
# NO WARRANTY
#
# The program was produced on an experimental basis in the course of the
# research and development conducted during the project and is provided
# to users as so produced on an experimental basis. Accordingly, the
# program is provided without any warranty whatsoever, whether express,
# implied, statutory or otherwise. The term "warranty" used herein
# includes, but is not limited to, any warranty of the quality,
# performance, merchantability and fitness for a particular purpose of
# the program and the nonexistence of any infringement or violation of
# any right of any third party.
#
# Each user of the program will agree and understand, and be deemed to
# have agreed and understood, that there is no warranty whatsoever for
# the program and, accordingly, the entire risk arising from or
# otherwise connected with the program is assumed by the user.
#
# Therefore, neither ICOT, the copyright holder, or any other
# organization that participated in or was otherwise related to the
# development of the program and their respective officials, directors,
# officers and other employees shall be held liable for any and all
# damages, including, without limitation, general, special, incidental
# and consequential damages, arising out of or otherwise in connection
# with the use or inability to use the program or any product, material
# or result produced or otherwise obtained by using the program,
# regardless of whether they have been advised of, or otherwise had
# knowledge of, the possibility of such damages at any time during the
# project or thereafter. Each user will be deemed to have agreed to the
# foregoing by his or her commencement of use of the program. The term
# "use" as used herein includes, but is not limited to, the use,
# modification, copying and distribution of the program and the
# production of secondary products from the program.
#
# In the case where the program, whether in its original form or
# modified, was distributed or delivered to or received by a user from
# any person, organization or entity other than ICOT, unless it makes or
# grants independently of ICOT any specific warranty to the user in
# writing, such person, organization or entity, will also be exempted
# from and not be held liable to the user for any such damages as noted
# above as far as the program is concerned.
#
# ---------------COPYING.ipadic-----END----------------------------------
----------------------------------------------------------------------
Lao Word Break Dictionary Data (laodict.txt)
# Copyright (C) 2016 and later: Unicode, Inc. and others.
# License & terms of use: http://www.unicode.org/copyright.html
# Copyright (c) 2015 International Business Machines Corporation
# and others. All Rights Reserved.
#
# Project: https://github.com/rober42539/lao-dictionary
# Dictionary: https://github.com/rober42539/lao-dictionary/laodict.txt
# License: https://github.com/rober42539/lao-dictionary/LICENSE.txt
# (copied below)
#
# This file is derived from the above dictionary version of Nov 22, 2020
# ----------------------------------------------------------------------
# Copyright (C) 2013 Brian Eugene Wilson, Robert Martin Campbell.
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#
# Redistributions of source code must retain the above copyright notice, this
# list of conditions and the following disclaimer. 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.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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
# COPYRIGHT HOLDER 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.
# --------------------------------------------------------------------------
----------------------------------------------------------------------
Burmese Word Break Dictionary Data (burmesedict.txt)
# Copyright (c) 2014 International Business Machines Corporation
# and others. All Rights Reserved.
#
# This list is part of a project hosted at:
# github.com/kanyawtech/myanmar-karen-word-lists
#
# --------------------------------------------------------------------------
# Copyright (c) 2013, LeRoy Benjamin Sharon
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met: Redistributions of source code must retain the above
# copyright notice, this list of conditions and the following
# disclaimer. 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.
#
# Neither the name Myanmar Karen Word Lists, 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 COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
# --------------------------------------------------------------------------
----------------------------------------------------------------------
Time Zone Database
ICU uses the public domain data and code derived from Time Zone
Database for its time zone support. The ownership of the TZ database
is explained in BCP 175: Procedure for Maintaining the Time Zone
Database section 7.
# 7. Database Ownership
#
# The TZ database itself is not an IETF Contribution or an IETF
# document. Rather it is a pre-existing and regularly updated work
# that is in the public domain, and is intended to remain in the
# public domain. Therefore, BCPs 78 [RFC5378] and 79 [RFC3979] do
# not apply to the TZ Database or contributions that individuals make
# to it. Should any claims be made and substantiated against the TZ
# Database, the organization that is providing the IANA
# Considerations defined in this RFC, under the memorandum of
# understanding with the IETF, currently ICANN, may act in accordance
# with all competent court orders. No ownership claims will be made
# by ICANN or the IETF Trust on the database or the code. Any person
# making a contribution to the database or code waives all rights to
# future claims in that contribution or in the TZ Database.
----------------------------------------------------------------------
Google double-conversion
Copyright 2006-2011, the V8 project authors. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* 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.
* Neither the name of Google Inc. 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 COPYRIGHT HOLDERS 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 COPYRIGHT
OWNER 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.
----------------------------------------------------------------------
JSON parsing library (nlohmann/json)
File: vendor/json/upstream/single_include/nlohmann/json.hpp (only for ICU4C)
MIT License
Copyright (c) 2013-2022 Niels Lohmann
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
----------------------------------------------------------------------
File: aclocal.m4 (only for ICU4C)
Section: pkg.m4 - Macros to locate and utilise pkg-config.
Copyright © 2004 Scott James Remnant .
Copyright © 2012-2015 Dan Nicholson
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 2 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, write to the Free Software
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
02111-1307, USA.
As a special exception to the GNU General Public License, if you
distribute this file as part of a program that contains a
configuration script generated by Autoconf, you may include it under
the same distribution terms that you use for the rest of that
program.
(The condition for the exception is fulfilled because
ICU4C includes a configuration script generated by Autoconf,
namely the `configure` script.)
----------------------------------------------------------------------
File: config.guess (only for ICU4C)
This file 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 .
As a special exception to the GNU General Public License, if you
distribute this file as part of a program that contains a
configuration script generated by Autoconf, you may include it under
the same distribution terms that you use for the rest of that
program. This Exception is an additional permission under section 7
of the GNU General Public License, version 3 ("GPLv3").
(The condition for the exception is fulfilled because
ICU4C includes a configuration script generated by Autoconf,
namely the `configure` script.)
----------------------------------------------------------------------
File: install-sh (only for ICU4C)
Copyright 1991 by the Massachusetts Institute of Technology
Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation, and that the name of M.I.T. not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission. M.I.T. makes no representations about the
suitability of this software for any purpose. It is provided "as is"
without express or implied warranty.
==============================================================================
23.) cpp-httplib 0.25.0
==============================================================================
Copyright (c) 2017 yhirose
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
==============================================================================
100.) GNU GENERAL PUBLIC LICENSE Version 3
==============================================================================
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
.
==============================================================================
101.) GNU LESSER GENERAL PUBLIC LICENSE Version 2.1
==============================================================================
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
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 and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, 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 library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete 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 distribute a copy of this License along with the
Library.
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 Library or any portion
of it, thus forming a work based on the Library, 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) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
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 Library, 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 Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you 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.
If distribution of 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 satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be 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.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library 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.
9. 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 Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
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 with
this License.
11. 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 Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library 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 Library.
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.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library 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.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser 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 Library
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 Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
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
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "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
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. 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 LIBRARY 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
LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
==============================================================================
102.) GNU LESSER GENERAL PUBLIC LICENSE Version 3.0
==============================================================================
GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein, “this License†refers to version 3 of the GNU Lesser
General Public License, and the “GNU GPL†refers to version 3 of the
GNU General Public License.
“The Library†refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.
An “Application†is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode
of using an interface provided by the Library.
A “Combined Work†is a work produced by combining or linking an
Application with the Library. The particular version of the Library
with which the Combined Work was made is also called the “Linked
Versionâ€.
The “Minimal Corresponding Source†for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.
The “Corresponding Application Code†for a Combined Work means the
object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License
without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a
facility refers to a function or data to be supplied by an Application
that uses the facility (other than as an argument passed when the
facility is invoked), then you may convey a copy of the modified
version:
a) under this License, provided that you make a good faith effort
to ensure that, in the event an Application does not supply the
function or data, the facility still operates, and performs
whatever part of its purpose remains meaningful, or
b) under the GNU GPL, with none of the additional permissions of
this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from
a header file that is part of the Library. You may convey such object
code under terms of your choice, provided that, if the incorporated
material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following:
a) Give prominent notice with each copy of the object code that
the Library is used in it and that the Library and its use are
covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this
license document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that, taken
together, effectively do not restrict modification of the portions of
the Library contained in the Combined Work and reverse engineering for
debugging such modifications, if you also do each of the following:
a) Give prominent notice with each copy of the Combined Work that
the Library is used in it and that the Library and its use are
covered by this License.
b) Accompany the Combined Work with a copy of the GNU GPL and this
license document.
c) For a Combined Work that displays copyright notices during
execution, include the copyright notice for the Library among
these notices, as well as a reference directing the user to the
copies of the GNU GPL and this license document.
d) Do one of the following:
0) Convey the Minimal Corresponding Source under the terms of
this License, and the Corresponding Application Code in a form
suitable for, and under terms that permit, the user to
recombine or relink the Application with a modified version of
the Linked Version to produce a modified Combined Work, in the
manner specified by section 6 of the GNU GPL for conveying
Corresponding Source.
1) Use a suitable shared library mechanism for linking with
the Library. A suitable mechanism is one that (a) uses at run
time a copy of the Library already present on the user's
computer system, and (b) will operate properly with a modified
version of the Library that is interface-compatible with the
Linked Version.
e) Provide Installation Information, but only if you would
otherwise be required to provide such information under section 6
of the GNU GPL, and only to the extent that such information is
necessary to install and execute a modified version of the
Combined Work produced by recombining or relinking the Application
with a modified version of the Linked Version. (If you use option
4d0, the Installation Information must accompany the Minimal
Corresponding Source and Corresponding Application Code. If you
use option 4d1, you must provide the Installation Information in
the manner specified by section 6 of the GNU GPL for conveying
Corresponding Source.)
5. Combined Libraries.
You may place library facilities that are a work based on the Library
side by side in a single library together with other library
facilities that are not Applications and are not covered by this
License, and convey such a combined library under terms of your
choice, if you do both of the following:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities, conveyed under the terms of this License.
b) Give prominent notice with the combined library that part of
it is a work based on the Library, and explaining where to find
the accompanying uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions
of the GNU Lesser 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 Library
as you received it specifies that a certain numbered version of the
GNU Lesser General Public License “or any later version†applies to
it, you have the option of following the terms and conditions either
of that published version or of any later version published by the
Free Software Foundation. If the Library as you received it does not
specify a version number of the GNU Lesser General Public License,
you may choose any version of the GNU Lesser General Public License
ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the Library.
==============================================================================
103.) MOZILLA PUBLIC LICENSE Version 2.0
==============================================================================
Mozilla Public License Version 2.0
==================================
1. Definitions
--------------
1.1. "Contributor"
means each individual or legal entity that creates, contributes to
the creation of, or owns Covered Software.
1.2. "Contributor Version"
means the combination of the Contributions of others (if any) used
by a Contributor and that particular Contributor's Contribution.
1.3. "Contribution"
means Covered Software of a particular Contributor.
1.4. "Covered Software"
means Source Code Form to which the initial Contributor has attached
the notice in Exhibit A, the Executable Form of such Source Code
Form, and Modifications of such Source Code Form, in each case
including portions thereof.
1.5. "Incompatible With Secondary Licenses"
means
(a) that the initial Contributor has attached the notice described
in Exhibit B to the Covered Software; or
(b) that the Covered Software was made available under the terms of
version 1.1 or earlier of the License, but not also under the
terms of a Secondary License.
1.6. "Executable Form"
means any form of the work other than Source Code Form.
1.7. "Larger Work"
means a work that combines Covered Software with other material, in
a separate file or files, that is not Covered Software.
1.8. "License"
means this document.
1.9. "Licensable"
means having the right to grant, to the maximum extent possible,
whether at the time of the initial grant or subsequently, any and
all of the rights conveyed by this License.
1.10. "Modifications"
means any of the following:
(a) any file in Source Code Form that results from an addition to,
deletion from, or modification of the contents of Covered
Software; or
(b) any new file in Source Code Form that contains any Covered
Software.
1.11. "Patent Claims" of a Contributor
means any patent claim(s), including without limitation, method,
process, and apparatus claims, in any patent Licensable by such
Contributor that would be infringed, but for the grant of the
License, by the making, using, selling, offering for sale, having
made, import, or transfer of either its Contributions or its
Contributor Version.
1.12. "Secondary License"
means either the GNU General Public License, Version 2.0, the GNU
Lesser General Public License, Version 2.1, the GNU Affero General
Public License, Version 3.0, or any later versions of those
licenses.
1.13. "Source Code Form"
means the form of the work preferred for making modifications.
1.14. "You" (or "Your")
means an individual or a legal entity exercising rights under this
License. For legal entities, "You" includes any entity that
controls, is controlled by, or is under common control with You. For
purposes of this definition, "control" means (a) the power, direct
or indirect, to cause the direction or management of such entity,
whether by contract or otherwise, or (b) ownership of more than
fifty percent (50%) of the outstanding shares or beneficial
ownership of such entity.
2. License Grants and Conditions
--------------------------------
2.1. Grants
Each Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license:
(a) under intellectual property rights (other than patent or trademark)
Licensable by such Contributor to use, reproduce, make available,
modify, display, perform, distribute, and otherwise exploit its
Contributions, either on an unmodified basis, with Modifications, or
as part of a Larger Work; and
(b) under Patent Claims of such Contributor to make, use, sell, offer
for sale, have made, import, and otherwise transfer either its
Contributions or its Contributor Version.
2.2. Effective Date
The licenses granted in Section 2.1 with respect to any Contribution
become effective for each Contribution on the date the Contributor first
distributes such Contribution.
2.3. Limitations on Grant Scope
The licenses granted in this Section 2 are the only rights granted under
this License. No additional rights or licenses will be implied from the
distribution or licensing of Covered Software under this License.
Notwithstanding Section 2.1(b) above, no patent license is granted by a
Contributor:
(a) for any code that a Contributor has removed from Covered Software;
or
(b) for infringements caused by: (i) Your and any other third party's
modifications of Covered Software, or (ii) the combination of its
Contributions with other software (except as part of its Contributor
Version); or
(c) under Patent Claims infringed by Covered Software in the absence of
its Contributions.
This License does not grant any rights in the trademarks, service marks,
or logos of any Contributor (except as may be necessary to comply with
the notice requirements in Section 3.4).
2.4. Subsequent Licenses
No Contributor makes additional grants as a result of Your choice to
distribute the Covered Software under a subsequent version of this
License (see Section 10.2) or under the terms of a Secondary License (if
permitted under the terms of Section 3.3).
2.5. Representation
Each Contributor represents that the Contributor believes its
Contributions are its original creation(s) or it has sufficient rights
to grant the rights to its Contributions conveyed by this License.
2.6. Fair Use
This License is not intended to limit any rights You have under
applicable copyright doctrines of fair use, fair dealing, or other
equivalents.
2.7. Conditions
Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
in Section 2.1.
3. Responsibilities
-------------------
3.1. Distribution of Source Form
All distribution of Covered Software in Source Code Form, including any
Modifications that You create or to which You contribute, must be under
the terms of this License. You must inform recipients that the Source
Code Form of the Covered Software is governed by the terms of this
License, and how they can obtain a copy of this License. You may not
attempt to alter or restrict the recipients' rights in the Source Code
Form.
3.2. Distribution of Executable Form
If You distribute Covered Software in Executable Form then:
(a) such Covered Software must also be made available in Source Code
Form, as described in Section 3.1, and You must inform recipients of
the Executable Form how they can obtain a copy of such Source Code
Form by reasonable means in a timely manner, at a charge no more
than the cost of distribution to the recipient; and
(b) You may distribute such Executable Form under the terms of this
License, or sublicense it under different terms, provided that the
license for the Executable Form does not attempt to limit or alter
the recipients' rights in the Source Code Form under this License.
3.3. Distribution of a Larger Work
You may create and distribute a Larger Work under terms of Your choice,
provided that You also comply with the requirements of this License for
the Covered Software. If the Larger Work is a combination of Covered
Software with a work governed by one or more Secondary Licenses, and the
Covered Software is not Incompatible With Secondary Licenses, this
License permits You to additionally distribute such Covered Software
under the terms of such Secondary License(s), so that the recipient of
the Larger Work may, at their option, further distribute the Covered
Software under the terms of either this License or such Secondary
License(s).
3.4. Notices
You may not remove or alter the substance of any license notices
(including copyright notices, patent notices, disclaimers of warranty,
or limitations of liability) contained within the Source Code Form of
the Covered Software, except that You may alter any license notices to
the extent required to remedy known factual inaccuracies.
3.5. Application of Additional Terms
You may choose to offer, and to charge a fee for, warranty, support,
indemnity or liability obligations to one or more recipients of Covered
Software. However, You may do so only on Your own behalf, and not on
behalf of any Contributor. You must make it absolutely clear that any
such warranty, support, indemnity, or liability obligation is offered by
You alone, and You hereby agree to indemnify every Contributor for any
liability incurred by such Contributor as a result of warranty, support,
indemnity or liability terms You offer. You may include additional
disclaimers of warranty and limitations of liability specific to any
jurisdiction.
4. Inability to Comply Due to Statute or Regulation
---------------------------------------------------
If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Software due to
statute, judicial order, or regulation then You must: (a) comply with
the terms of this License to the maximum extent possible; and (b)
describe the limitations and the code they affect. Such description must
be placed in a text file included with all distributions of the Covered
Software under this License. Except to the extent prohibited by statute
or regulation, such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.
5. Termination
--------------
5.1. The rights granted under this License will terminate automatically
if You fail to comply with any of its terms. However, if You become
compliant, then the rights granted under this License from a particular
Contributor are reinstated (a) provisionally, unless and until such
Contributor explicitly and finally terminates Your grants, and (b) on an
ongoing basis, if such Contributor fails to notify You of the
non-compliance by some reasonable means prior to 60 days after You have
come back into compliance. Moreover, Your grants from a particular
Contributor are reinstated on an ongoing basis if such Contributor
notifies You of the non-compliance by some reasonable means, this is the
first time You have received notice of non-compliance with this License
from such Contributor, and You become compliant prior to 30 days after
Your receipt of the notice.
5.2. If You initiate litigation against any entity by asserting a patent
infringement claim (excluding declaratory judgment actions,
counter-claims, and cross-claims) alleging that a Contributor Version
directly or indirectly infringes any patent, then the rights granted to
You by any and all Contributors for the Covered Software under Section
2.1 of this License shall terminate.
5.3. In the event of termination under Sections 5.1 or 5.2 above, all
end user license agreements (excluding distributors and resellers) which
have been validly granted by You or Your distributors under this License
prior to termination shall survive termination.
************************************************************************
* *
* 6. Disclaimer of Warranty *
* ------------------------- *
* *
* Covered Software is provided under this License on an "as is" *
* basis, without warranty of any kind, either expressed, implied, or *
* statutory, including, without limitation, warranties that the *
* Covered Software is free of defects, merchantable, fit for a *
* particular purpose or non-infringing. The entire risk as to the *
* quality and performance of the Covered Software is with You. *
* Should any Covered Software prove defective in any respect, You *
* (not any Contributor) assume the cost of any necessary servicing, *
* repair, or correction. This disclaimer of warranty constitutes an *
* essential part of this License. No use of any Covered Software is *
* authorized under this License except under this disclaimer. *
* *
************************************************************************
************************************************************************
* *
* 7. Limitation of Liability *
* -------------------------- *
* *
* Under no circumstances and under no legal theory, whether tort *
* (including negligence), contract, or otherwise, shall any *
* Contributor, or anyone who distributes Covered Software as *
* permitted above, be liable to You for any direct, indirect, *
* special, incidental, or consequential damages of any character *
* including, without limitation, damages for lost profits, loss of *
* goodwill, work stoppage, computer failure or malfunction, or any *
* and all other commercial damages or losses, even if such party *
* shall have been informed of the possibility of such damages. This *
* limitation of liability shall not apply to liability for death or *
* personal injury resulting from such party's negligence to the *
* extent applicable law prohibits such limitation. Some *
* jurisdictions do not allow the exclusion or limitation of *
* incidental or consequential damages, so this exclusion and *
* limitation may not apply to You. *
* *
************************************************************************
8. Litigation
-------------
Any litigation relating to this License may be brought only in the
courts of a jurisdiction where the defendant maintains its principal
place of business and such litigation shall be governed by laws of that
jurisdiction, without reference to its conflict-of-law provisions.
Nothing in this Section shall prevent a party's ability to bring
cross-claims or counter-claims.
9. Miscellaneous
----------------
This License represents the complete agreement concerning the subject
matter hereof. If any provision of this License is held to be
unenforceable, such provision shall be reformed only to the extent
necessary to make it enforceable. Any law or regulation which provides
that the language of a contract shall be construed against the drafter
shall not be used to construe this License against a Contributor.
10. Versions of the License
---------------------------
10.1. New Versions
Mozilla Foundation is the license steward. Except as provided in Section
10.3, no one other than the license steward has the right to modify or
publish new versions of this License. Each version will be given a
distinguishing version number.
10.2. Effect of New Versions
You may distribute the Covered Software under the terms of the version
of the License under which You originally received the Covered Software,
or under the terms of any subsequent version published by the license
steward.
10.3. Modified Versions
If you create software not governed by this License, and you want to
create a new license for such software, you may create and use a
modified version of this License if you rename the license and remove
any references to the name of the license steward (except to note that
such modified license differs from this License).
10.4. Distributing Source Code Form that is Incompatible With Secondary
Licenses
If You choose to distribute Source Code Form that is Incompatible With
Secondary Licenses under the terms of this version of the License, the
notice described in Exhibit B of this License must be attached.
Exhibit A - Source Code Form License Notice
-------------------------------------------
This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0. If a copy of the MPL was not distributed with this
file, You can obtain one at http://mozilla.org/MPL/2.0/.
If it is not possible or desirable to put the notice in a particular
file, then You may include the notice in a location (such as a LICENSE
file in a relevant directory) where a recipient would be likely to look
for such a notice.
You may add additional accurate notices of copyright ownership.
Exhibit B - "Incompatible With Secondary Licenses" Notice
---------------------------------------------------------
This Source Code Form is "Incompatible With Secondary Licenses", as
defined by the Mozilla Public License, v. 2.0.
==============================================================================
104.) Boost Software License 1.0
==============================================================================
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization
obtaining a copy of the software and accompanying documentation covered by
this license (the "Software") to use, reproduce, display, distribute,
execute, and transmit the Software, and to prepare derivative works of the
Software, and to permit third-parties to whom the Software is furnished to
do so, all subject to the following:
The copyright notices in the Software and this entire statement, including
the above license grant, this restriction and the following disclaimer,
must be included in all copies of the Software, in whole or in part, and
all derivative works of the Software, unless such copies or derivative
works are solely in the form of machine-executable object code generated by
a source language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
==============================================================================
50.) "ABeeZee" von Anja Meiners ( SIL Open Font License )
==============================================================================
ABeeZee is Copyright (c), Anja Meiners.
All Rights Reserved.
ABeeZee is a Reserved Font Name for this Font Software.
Copyright (c) 2011 by Anja Meiners, with Reserved Font Name 'ABeeZee'
This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL
==============================================================================
51.) "Grundschrift" von Christian Urf ( eigene Lizenz )
==============================================================================
Hinweise zum Copyright:
Die Grundschrift wurde von mir mit Hilfe von myscriptfont.com erstellt und
darf weitergegeben und kopiert werden.
Die Erstellung und Weitergabe von Unterrichtsmaterialien mit Hilfe der Schrift
ist ausdrücklich erwünscht.
Kontaktmöglichkeit: grundschrift@urff.info
Christian Urf
==============================================================================
52.) "Gruschudru" von Florian Emrich ( SIL Open Font License )
==============================================================================
Gruschudru is Copyright (c), Florian Emrich.
All Rights Reserved.
Gruschudru is a Reserved Font Name for this Font Software.
This Font Software is licensed under the SIL Open Font License, Version 1.0.
No modification of the license is permitted, only verbatim copy is allowed.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL
==============================================================================
52.1) FONTLOG
==============================================================================
FONTLOG
Gruschudru Basic v 1.0
==========================
Die Schrift entspricht in nahezu allem der Schrift Andika Basic. Änderungen
wurden lediglich beim großen I gemacht, sowie beim kleinen t.
Der OFL folgend wird natürlich auch diese Schrift unter der OFL
veröffentlicht.
Andika Basic Regular v 1.0
==========================
This file provides detailed information on the Andika family of fonts.
This information should be distributed along with the Andika fonts and
any derivative works.
Basic Font Information
----------------------
Andika ("Write!" in Swahili) is a sans serif, Unicode-compliant font
designed especially for literacy use, taking into account the needs of
beginning readers. The focus is on clear, easy-to-perceive letterforms
that will not be easily confused with one another.
A sans serif font is preferred by some literacy personnel for teaching
people to read. Its forms are simpler and less cluttered than some
serif fonts can be. For years, literacy workers have had to make do
with fonts that were available but not really suitable for beginning
readers and writers. In some cases, literacy specialists have had to
tediously cobble together letters from a variety of fonts in order to
get the all of characters they need for their particular language
project, resulting in confusing and unattractive publications. Andika
addresses those issues.
After receiving many insightful comments on the Design Review fonts,
we have refined Andika's final letterforms, with alternate shapes
still available for some characters. Andika Basic Regular (italic,
bold, and bold italic are yet to come) is here released as the
foundation for the Andika font family.
With the SIL TypeTuner utility (see http://scripts.sil.org/TypeTuner),
you can select which alternates to use as Andika's default
letterforms.
SIL's "Basic" Roman fonts -- Andika Basic, Gentium Basic, and Gentium
Book Basic -- have a limited character set, supporting only the Basic
Latin and Latin-1 Supplement Unicode ranges, plus a selection of the
more commonly used extended Latin characters, with miscellaneous
diacritical marks, symbols and punctuation. For a complete list of
supported characters see the list at the end of this document.
In particular, these fonts do not support:
Full extended Latin IPA
Complete support for Central European languages
Greek
Cyrillic
A much more complete character set, comparable to Charis SIL and
Doulos SIL, will be supported in a future version of Andika. This
"Basic" font is intended to provide an Andika with stable letterforms
for both default and alternate glyphs. No need to request additional
glyphs or characters to be supported in the Basic fonts - such support
will become available in the full font in the future.
Features
--------
One font from this typeface family is included in this release:
* Andika Basic Regular
As an SIL "Basic" font, Andika Basic has:
OpenType and Graphite smart code for diacritic placement
A few useful OpenType and Graphite features
Support for a few more recent additions to Unicode and the SIL PUA
Character assignments are updated to conform to Unicode 5.1
Andika Basic supports a subset of the smart font features that the
Doulos SIL font supports. Those features are:
Capital Eng alternates
Capital N-left-hook alternate
Capital Q alternate
Capital Y-hook alternate
Literacy alternates -- single-story a and g -- as default glyphs
Lower case j alternate
Lower case dotless j alternate
Lower case q alternate
Lower case y-hook alternate
Modifier apostrophe alternate
Modifier colon alternate
No-tail t and y alternates
Numeral 0 1 4 6 7 9 alternates
Open O -- both upper and lower case -- alternates
Tail i and l alternates
Vietnamese-style diacritics
More detail on features can be seen at
http://scripts.sil.org/SILUnicodeRF_Features and
http://scripts.sil.org/DoulosSIL_Technical.
ChangeLog
----------
(This should list both major and minor changes, most recent first.)
15 Mar 2011 (SIL TypeTuner) Tuned version of Andika Basic Regular 1.0
- Tuned and delivered by SIL TypeTuner
(http://scripts.sil.org/ttw/fonts2go.cgi).
- See included xml file for details of feature changes.
2 May 2008 (SIL NRSI team) Andika Basic Regular version 1.0
- Released under SIL Open Font License.
19 January 2007 (SIL NRSI team) Andika Design Review version 0.001
- Released under Open Font License. Five new fonts containing
revisions of some glyphs and different combinations of others.
7 Aug 2006 (SIL NRSI team) Andika Design Review version 0.001
- Released under Open Font License.
Acknowledgements
-----------------
(Here is where contributors can be acknowledged. If you make
modifications
be sure to add your name (N), email (E), web-address (W) and
description
(D). This list is sorted by last name in alphabetical order.)
N: Victor Gaultney, Annie Olsen, Julie Remington
E:
W: http://scripts.sil.org
D: SIL designers and font engineers
SIL will remain as maintainers of this font project, but we do not
intend any further major releases. Our primary efforts will be going
into the full Andika package. Any contributions should be directed
toward that project.
For more information please visit the Andika page on SIL
International's Computers and Writing Systems website:
http://scripts.sil.org/andika
Or send an e-mail to
Supported Characters in Andika Basic
--------------------------------------------
C0 Controls and Basic Latin U+0020-U+007F
C1 Controls and Latin-1 Supplement U+00A0-U+00FF
Latin Extended-A U+0100..U+0103, U+0106..U+010E, U+011A..U+0121,
U+0124..U+0125, U+0128..U+012D, U+0130..U+0133, U+0139..U+013A,
U+0141..U+0144, U+0147..U+0148, U+014A..U+0155, U+0158..U+015D,
U+0160..U+0161, U+0164, U+0168..U+0171, U+00174..U+017E
Latin Extended-B U+0181, U+0186, U+0189..U+018A, U+018E, U+0190,
U+0192, U+0197..U+019A, U+019D, U+019F..U+01A1, U+01A9..U+01AA,
U+01AF..U+01B0, U+01B3..U+01B4, U+01B7, U+01CD..U+01E3,
U+01E6..U+01E9, U+01EE..U+01EF, U+01F4..U+01F5, U+01F8..U+01FF,
U+021E..U+021F, U+0226..U+0233, U+0237, U+023D, U+0241..U+0242,
U+0244..U+0245, U+024A..U+024B
IPA Extensions U+0251, U+0253..U+0254, U+0256..U+0257, U+0259,
U+025B, U+0263, U+0268..U+0269, U+026B, U+0272, U+0275, U+0283,
U+0289..U+028A, U+028C, U+0292, U+0294, U+02A0
Spacing Modifier Letters U+02BC, U+02C0, U+02C6..U+02C7,
U+02C9..U+02CB, U+02CD, U+02D7..U+02DD
Combining Diacritical Marks U+0300..U+0304,U+0306..U+030C, U+031B,
U+0323, U+0327..U+0328, U+0331, U+033F, U+035F
Greek and Coptic U+03A0, U+03A9, U+03C0
Latin Extended Additional U+1E02..U+1E0F, U+1E14..U+1E17,
U+1E1C..U+1E27, U+1E2E..U+1E3B, U+1E3E..U+1E49, U+1E4C..U+1E6F,
U+1E78..U+1E99, U+1EA0..U+1EF9
General Punctuation U+2011, U+2013..U+2014, U+2018..U+201A,
U+201C..U+201E, U+2020..U+2022, U+2026, U+2030, U+2039..U+203A, U+2044
Currency Symbols U+20AC
Letterlike Symbols U+2122..U+2123, U+2126
Mathematical Operators U+2202, U+2205..U+2206, U+220F,
U+2211..U+2212, U+2219..U+221A, U+221E, U+222B, U+2248, U+2260,
U+2264..U+2265
Geometric Shapes U+25CA, U+25CC
Latin Extended-C U+2C60..U+2C62
Modifier Tone Letters U+A700..U+A71A
Latin Extended-D U+A789..U+A78C
Alphabetic Presentation Forms U+FB01..U+FB02
SIL PUA U+F130..U+F131, U+F195, U+F197, U+F1C8, U+F1E9..U+F1EA,
U+F20E..U+F20F, U+F211..U+F212, U+F218..U+F219, U+F21D..U+F21F,
U+F242, U+F26A
Note: All of the SIL PUA characters listed above (except U+F130 and
U+F131) have now been accepted into the Unicode Standard. They are
therefore double-encoded in Andika Basic, allowing previously-entered
data to still display correctly.
==============================================================================
52.2) OFL Andika Basic Regular Release 1.0
==============================================================================
Copyright (c) 2004-2008, SIL International (http://scripts.sil.org),
with Reserved Font Names 'Andika' and 'SIL'.
This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL
==============================================================================
52.3) README - Andika Basic Regular Release 1.0
==============================================================================
2 May 2008
=========================================
Thank you for your interest in Andika ("Write!" in Swahili), a
Unicode-compliant sans serif font designed by SIL International
primarily for literacy use.
See FONTLOG.txt for detailed information on the rationale for Andika,
as well as a complete list of supported characters.
See AndikaBasicR-FAQ-KI.txt for frequently-asked questions and known
issues.
Andika Basic is released under the SIL Open Font License.
Andika is a trademark of SIL International.
See the OFL and OFL-FAQ for details of the SIL Open Font License.
See the FONTLOG for information on this and previous releases.
See the website (http://scripts.sil.org/andika) documentation or the
Andika Basic FAQ (http://scripts.sil.org/Andika_FAQ-KI) for frequently
asked questions and their answers.
TYPETUNER
15 Mar 2011
=========
This package contains a TypeTuned version of the Andika Basic font.
The TypeTuner settings file used to generate the enclosed font
is included in the package as AndikaBasic-feat_set_tuned.xml.
By inspecting this file with a text editor you can determine
which alternate behaviors have been enabled.
TIPS
====
We cannot afford to offer free technical support. The font has, however,
been through some testing on various platforms to be sure it works in most
situations. In particular, it has been tested and shown to work on Windows
2000, Windows XP and Windows Vista. Graphite capabilities have been tested
on Graphite-supported platforms.
If you do find a problem, please do report it to .
We can't guarantee any direct response, but will try to fix reported bugs in
future versions. Make sure you read through the
Complex Roman Font FAQ (http://scripts.sil.org/ComplexRomanFontFAQ).
Many problems can be solved, or at least explained, through an understanding
of the encoding and use of the fonts. Here are some basic hints:
Encoding:
The fonts are encoded according to Unicode, so your application must support
Unicode text in order to access letters other than the standard alphabet.
Most applications provide basic Unicode support. You will, however,
need some way of entering Unicode text into your document.
Keyboarding:
Charis SIL does not include any keyboarding helps or utilities. It uses the
built-in keyboards of the operating system. You will need to install the
appropriate keyboard and input method for the characters of the language you
wish to use. If you want to enter characters that are not supported by any
system keyboard, the Keyman program (www.tavultesoft.com) can be helpful
on Windows systems. Also available for Windows is MSKLC
(http://www.microsoft.com/globaldev/tools/msklc.mspx).
For Linux systems, KMFL (http://kmfl.sourceforge.net/)
is available. Ukelele (http://scripts.sil.org/ukelele) is available for Mac
OS X
versions 10.2 and later.
Another method of entering some symbols is provided by a few applications
such as Adobe InDesign. They can display a glyph palette that shows all the
glyphs (symbols) in a font and allow you to enter them by clicking on the
glyph you want.
Rendering:
This font is designed to work with two advanced font technologies,
Graphite or OpenType. To take advantage of the advanced typographic
capabilities of this font, you must be using applications that provide an
adequate level of support for Graphite or OpenType. See "Applications
that provide an adequate level of support for SIL Unicode Roman fonts"
(http://scripts.sil.org/Complex_AdLvSup).
CONTACT
========
For more information please visit the Andika Basic page on SIL International's
Computers and Writing systems website:
http://scripts.sil.org/andika
Or send an email to
==============================================================================
52.4) AndikaBasicR-FAQ-KI
==============================================================================
Andika Basic Regular v 1.0
==========================
Where does the name "Andika" come from?
Andika -- pronounced ahn-DEE-kah
Swahili -- spoken widely in southeastern regions of the African continent,
among other places. (See http://www.ethnologue.com/)
Meaning - "Write!"
What characters are included in this release?
Andika Basic covers some 630 commonly-used (in the SIL world) Roman
characters. See http://scripts.sil.org/Andika_technical for the full
listing.
What are all the stages of release for the Andika fonts?
Andika Design Review -- completed
Andika Basic -- where we are now
Andika Regular
Andika Basic Bold, Basic Italic, and Basic Bold Italic
Andika Bold, Italic, and Bold Italic
Why is the line spacing so much looser than other fonts?
Our SIL Unicode Roman fonts include characters with multiple stacked
diacritics that need a much looser line spacing (for example, U+1EA8 LATIN
CAPITAL LETTER A WITH CIRCUMFLEX AND HOOK ABOVE). We cannot make the line
spacing tighter without experiencing “clipping†of those characters. You
may
be able to overcome this by adjusting the line spacing in the application.
For example, in Microsoft Word select Format / Paragraph and set the line
spacing to use the Exactly setting and a value more suited to your needs.
For example, if the font size is 12 pt, select line spacing of Exactly 13
pt.
This will give a tighter line spacing. You can adjust the value up or down
depending on how many diacritics you need to stack. Another solution would
be to use SIL’s TypeTuner utility, which allows choosing a line spacing
setting as well as choosing default glyphs.
Does this font have straight quotes as well as curly ones?
Yes, there are both. Here are the Unicode codepoints (in order) and their
character names included in this font:
U+0022 QUOTATION MARK
U+0027 APOSTROPHE
U+2018 LEFT SINGLE QUOTATION MARK
U+2019 RIGHT SINGLE QUOTATION MARK
U+201C LEFT DOUBLE QUOTATION MARK
U+201D RIGHT DOUBLE QUOTATION MARK
Can I use Andika in my print publication?
Andika Basic is released under the SIL Open Font License
(see http://scripts.sil.org/OFL), which permits use for any publication,
whether electronic or printed. For more answers to usage questions, see the
OFL-FAQ (http://scripts.sil.org/OFL-FAQ). The license, along with
information specific to Andika Basic, is in the release package.
Can I use Andika on my website?
Yes. You can create web pages that request that Andika Basic be used to
display them (if that font is available on the user’s system). According to
the license, you are even allowed to place the font on your site for people
to download it. We would strongly recommend, however, that you direct users
to our site -- http://scripts.sil.org/Andika_download — to download the
font. This ensures that they are always using the most recent version with
bug fixes, etc.
Can I make changes to Andika?
Yes! That is allowed as long as you abide by the conditions of the SIL
Open
Font License (http://scripts.sil.org/OFL). We would be very interested in
seeing any changes you might make. See "Notes to contributors"
(http://scripts.sil.org/Andika_download) for more information.
Known Issues
We know of the following problems. Please report any others you encounter:
There has been no manual hinting done, but we have improved the overall
autohinting parameters. Still, onscreen display may at times be somewhat
distorted. Please evaluate the letterforms from printed text, but let us
know if you find severe distortions. In any case, the fonts should look
fine when printed.
Opening the font with FontLab 5.0.x, then closing it, crashes FontLab.
We are working to get this bug fixed in the next version of FontLab.
A workaround is to open the font, save as a .vfb file, close (which
still causes a crash). Then restart FontLab and open the .vfb file.
There are no alternate versions of fi and fl ligatures at this time.
==============================================================================
55.) "OpenDyslexic" Version 2 von Abbie Gonzalez ( SIL Open Font License )
==============================================================================
Copyright (c) 2019-07-29, Abbie Gonzalez
(https://abbiecod.es|support@abbiecod.es),
with Reserved Font Name OpenDyslexic.
Copyright (c) 12/2012 - 2019
This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL
OpenDyslexic is an open source font created to help increase readability for
readers with dyslexia. The typeface includes regular, bold, italic, and
bold-italic styles. It is being updated continually and improved based on
input from other dyslexic users.
There is a new version of OpenDyslexic.
It's licensed as SIL-OFL to make it easier to include in projects
where other licenses caused difficulty.
==============================================================================
500.) SIL OPEN FONT LICENSE Version 1.0 - 22 November 2005
==============================================================================
PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of cooperative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide an open
framework in which fonts may be shared and improved in partnership with
others.
The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and sold with any software provided that the font
names of derivative works are changed. The fonts and derivatives,
however, cannot be released under any other type of license.
DEFINITIONS
"Font Software" refers to any and all of the following:
- font files
- data files
- source code
- build scripts
- documentation
"Reserved Font Name" refers to the Font Software name as seen by
users and any other names as specified after the copyright statement.
"Standard Version" refers to the collection of Font Software
components as distributed by the Copyright Holder.
"Modified Version" refers to any derivative font software made by
adding to, deleting, or substituting -- in part or in whole --
any of the components of the Standard Version, by changing formats
or by porting the Font Software to a new environment.
"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.
PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:
1) Neither the Font Software nor any of its individual components,
in Standard or Modified Versions, may be sold by itself.
2) Standard or Modified Versions of the Font Software may be bundled,
redistributed and sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.
3) No Modified Version of the Font Software may use the Reserved Font
Name(s), in part or in whole, unless explicit written permission is
granted by the Copyright Holder. This restriction applies to all
references stored in the Font Software, such as the font menu name and
other font description fields, which are used to differentiate the
font from others.
4) The name(s) of the Copyright Holder or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder and the Author(s) or with their explicit written
permission.
5) The Font Software, modified or unmodified, in part or in whole,
must be distributed using this license, and may not be distributed
under any other license.
TERMINATION
This license becomes null and void if any of the above conditions are
not met.
DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.
==============================================================================
501.) SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
==============================================================================
PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.
The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.
DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.
"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).
"Original Version" refers to the collection of Font Software components as
distributed by the Copyright Holder(s).
"Modified Version" refers to any derivative made by adding to, deleting,
or substituting -- in part or in whole -- any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.
"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.
PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:
1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.
2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.
3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.
4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.
5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.
TERMINATION
This license becomes null and void if any of the above conditions are
not met.
DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.
==============================================================================
503.) Frequently Asked Questions about the SIL Open Font License (OFL)
==============================================================================
Version 1.1-update5 - April 2017
The OFL FAQ is copyright (c) 2005-2017 SIL International.
(See http://scripts.sil.org/OFL for updates)
CONTENTS OF THIS FAQ
1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
2 USING OFL FONTS FOR WEB PAGES AND ONLINE WEB FONT SERVICES
3 MODIFYING OFL-LICENSED FONTS
4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
5 CHOOSING RESERVED FONT NAMES
6 ABOUT THE FONTLOG
7 MAKING CONTRIBUTIONS TO OFL PROJECTS
8 ABOUT THE LICENSE ITSELF
9 ABOUT SIL INTERNATIONAL
APPENDIX A - FONTLOG EXAMPLE
1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
1.1 Can I use the fonts for a book or other print publication, to create logos
or other graphics or even to manufacture objects based on their outlines?
Yes. You are very welcome to do so. Authors of fonts released under the OFL
allow you to use their font software as such for any kind of design work. No
additional license or permission is required, unlike with some other licenses.
Some examples of these uses are: logos, posters, business cards, stationery,
video titling, signage, t-shirts, personalised fabric, 3D-printed/laser-cut
shapes, sculptures, rubber stamps, cookie cutters and lead type.
1.1.1 Does that restrict the license or distribution of that artwork?
No. You remain the author and copyright holder of that newly derived graphic or
object. You are simply using an open font in the design process. It is only
when you redistribute, bundle or modify the font itself that other conditions
of the license have to be respected (see below for more details).
1.1.2 Is any kind of acknowledgement required?
No. Font authors may appreciate being mentioned in your artwork's
acknowledgements alongside the name of the font, possibly with a link to their
website, but that is not required.
1.2 Can the fonts be included with Free/Libre and Open Source Software
collections such as GNU/Linux and BSD distributions and repositories?
Yes! Fonts licensed under the OFL can be freely included alongside other
software under FLOSS (Free/Libre and Open Source Software) licenses. Since
fonts are typically aggregated with, not merged into, existing software, there
is little need to be concerned about incompatibility with existing software
licenses. You may also repackage the fonts and the accompanying components in a
.rpm or .deb package (or other similar package formats or installers) and
include them in distribution CD/DVDs and online repositories. (Also see section
5.9 about rebuilding from source.)
1.3 I want to distribute the fonts with my program. Does this mean my program
also has to be Free/Libre and Open Source Software?
No. Only the portions based on the Font Software are required to be released
under the OFL. The intent of the license is to allow aggregation or bundling
with software under restricted licensing as well.
1.4 Can I sell a software package that includes these fonts?
Yes, you can do this with both the Original Version and a Modified Version of
the fonts. Examples of bundling made possible by the OFL would include: word
processors, design and publishing applications, training and educational
software, games and entertainment software, mobile device applications, etc.
1.5 Can I include the fonts on a CD of freeware or commercial fonts?
Yes, as long some other font or software is also on the disk, so the OFL font
is not sold by itself.
1.6 Why won't the OFL let me sell the fonts alone?
The intent is to keep people from making money by simply redistributing the
fonts. The only people who ought to profit directly from the fonts should be
the original authors, and those authors have kindly given up potential direct
income to distribute their fonts under the OFL. Please honour and respect their
contribution!
1.7 What about sharing OFL fonts with friends on a CD, DVD or USB stick?
You are very welcome to share open fonts with friends, family and colleagues
through removable media. Just remember to include the full font package,
including any copyright notices and licensing information as available in
OFL.txt. In the case where you sell the font, it has to come bundled with
software.
1.8 Can I host the fonts on a web site for others to use?
Yes, as long as you make the full font package available. In most cases it may
be best to point users to the main site that distributes the Original Version
so they always get the most recent stable and complete version. See also
discussion of web fonts in Section 2.
1.9 Can I host the fonts on a server for use over our internal network?
Yes. If the fonts are transferred from the server to the client computer by
means that allow them to be used even if the computer is no longer attached to
the network, the full package (copyright notices, licensing information, etc.)
should be included.
1.10 Does the full OFL license text always need to accompany the font?
The only situation in which an OFL font can be distributed without the text of
the OFL (either in a separate file or in font metadata), is when a font is
embedded in a document or bundled within a program. In the case of metadata
included within a font, it is legally sufficient to include only a link to the
text of the OFL on http://scripts.sil.org/OFL, but we strongly recommend
against this. Most modern font formats include metadata fields that will accept
the full OFL text, and full inclusion increases the likelihood that users will
understand and properly apply the license.
1.11 What do you mean by 'embedding'? How does that differ from other means of
distribution?
By 'embedding' we mean inclusion of the font in a document or file in a way
that makes extraction (and redistribution) difficult or clearly discouraged. In
many cases the names of embedded fonts might also not be obvious to those
reading the document, the font data format might be altered, and only a subset
of the font - only the glyphs required for the text - might be included. Any
other means of delivering a font to another person is considered
'distribution', and needs to be accompanied by any copyright notices and
licensing information available in OFL.txt.
1.12 So can I embed OFL fonts in my document?
Yes, either in full or a subset. The restrictions regarding font modification
and redistribution do not apply, as the font is not intended for use outside
the document.
1.13 Does embedding alter the license of the document itself?
No. Referencing or embedding an OFL font in any document does not change the
license of the document itself. The requirement for fonts to remain under the
OFL does not apply to any document created using the fonts and their
derivatives. Similarly, creating any kind of graphic using a font under OFL
does not make the resulting artwork subject to the OFL.
1.14 If OFL fonts are extracted from a document in which they are embedded
(such as a PDF file), what can be done with them? Is this a risk to author(s)?
The few utilities that can extract fonts embedded in a PDF will typically
output limited amounts of outlines - not a complete font. To create a working
font from this method is much more difficult and time consuming than finding
the source of the original OFL font. So there is little chance that an OFL font
would be extracted and redistributed inappropriately through this method. Even
so, copyright laws address any misrepresentation of authorship. All Font
Software released under the OFL and marked as such by the author(s) is intended
to remain under this license regardless of the distribution method, and cannot
be redistributed under any other license. We strongly discourage any font
extraction - we recommend directly using the font sources instead - but if you
extract font outlines from a document, please be considerate: respect the work
of the author(s) and the licensing model.
1.15 What about distributing fonts with a document? Within a compressed folder
structure? Is it distribution, bundling or embedding?
Certain document formats may allow the inclusion of an unmodified font within
their file structure which may consist of a compressed folder containing the
various resources forming the document (such as pictures and thumbnails).
Including fonts within such a structure is understood as being different from
embedding but rather similar to bundling (or mere aggregation) which the
license explicitly allows. In this case the font is conveyed unchanged whereas
embedding a font usually transforms it from the original format. The OFL does
not allow anyone to extract the font from such a structure to then redistribute
it under another license. The explicit permission to redistribute and embed
does not cancel the requirement for the Font Software to remain under the
license chosen by its author(s). Even if the font travels inside the document
as one of its assets, it should not lose its authorship information and
licensing.
1.16 What about ebooks shipping with open fonts?
The requirements differ depending on whether the fonts are linked, embedded or
distributed (bundled or aggregated). Some ebook formats use web technologies to
do font linking via @font-face, others are designed for font embedding, some
use fonts distributed with the document or reading software, and a few rely
solely on the fonts already present on the target system. The license
requirements depend on the type of inclusion as discussed in 1.15.
1.17 Can Font Software released under the OFL be subject to URL-based access
restrictions methods or DRM (Digital Rights Management) mechanisms?
Yes, but these issues are out-of-scope for the OFL. The license itself neither
encourages their use nor prohibits them since such mechanisms are not
implemented in the components of the Font Software but through external
software. Such restrictions are put in place for many different purposes
corresponding to various usage scenarios. One common example is to limit
potentially dangerous cross-site scripting attacks. However, in the spirit of
libre/open fonts and unrestricted writing systems, we strongly encourage open
sharing and reuse of OFL fonts, and the establishment of an environment where
such restrictions are unnecessary. Note that whether you wish to use such
mechanisms or you prefer not to, you must still abide by the rules set forth by
the OFL when using fonts released by their authors under this license.
Derivative fonts must be licensed under the OFL, even if they are part of a
service for which you charge fees and/or for which access to source code is
restricted. You may not sell the fonts on their own - they must be part of a
larger software package, bundle or subscription plan. For example, even if the
OFL font is distributed in a software package or via an online service using a
DRM mechanism, the user would still have the right to extract that font, use,
study, modify and redistribute it under the OFL.
1.18 I've come across a font released under the OFL. How can I easily get more
information about the Original Version? How can I know where it stands compared
to the Original Version or other Modified Versions?
Consult the copyright statement(s) in the license for ways to contact the
original authors. Consult the FONTLOG (see section 6 for more details and
examples) for information on how the font differs from the Original Version,
and get in touch with the various contributors via the information in the
acknowledgement section. Please consider using the Original Versions of the
fonts whenever possible.
1.19 What do you mean in condition 4 of the OFL's permissions and conditions?
Can you provide examples of abusive promotion / endorsement / advertisement vs.
normal acknowledgement?
The intent is that the goodwill and reputation of the author(s) should not be
used in a way that makes it sound like the original author(s) endorse or
approve of a specific Modified Version or software bundle. For example, it
would not be right to advertise a word processor by naming the author(s) in a
listing of software features, or to promote a Modified Version on a web site by
saying "designed by ...". However, it would be appropriate to acknowledge the
author(s) if your software package has a list of people who deserve thanks. We
realize that this can seem to be a grey area, but the standard used to judge an
acknowledgement is that if the acknowledgement benefits the author(s) it is
allowed, but if it primarily benefits other parties, or could reflect poorly on
the author(s), then it is not.
1.20 I'm writing a small app for mobile platforms, do I need to include the
whole package?
If you bundle a font under the OFL with your mobile app you must comply with
the terms of the license. At a minimum you must include the copyright
statement, the license notice and the license text. A mention of this
information in your About box or Changelog, with a link to where the font
package is from, is good practice, and the extra space needed to carry these
items is very small. You do not, however, need to include the full contents of
the font package - only the fonts you use and the copyright and license that
apply to them. For example, if you only use the regular weight in your app, you
do not need to include the italic and bold versions.
1.21 What about including OFL fonts by default in my firmware or dedicated
operating system?
Many such systems are restricted and turned into appliances so that users
cannot study or modify them. Using open fonts to increase quality and language
coverage is a great idea, but you need to be aware that if there is a way for
users to extract fonts you cannot legally prevent them from doing that. The
fonts themselves, including any changes you make to them, must be distributed
under the OFL even if your firmware has a more restrictive license. If you do
transform the fonts and change their formats when you include them in your
firmware you must respect any names reserved by the font authors via the RFN
mechanism and pick your own font name. Alternatively if you directly add a font
under the OFL to the font folder of your firmware without modifying or
optimizing it you are simply bundling the font like with any other software
collection, and do not need to make any further changes.
1.22 Can I make and publish CMS themes or templates that use OFL fonts? Can I
include the fonts themselves in the themes or templates? Can I sell the whole
package?
Yes, you are very welcome to integrate open fonts into themes and templates for
your preferred CMS and make them more widely available. Remember that you can
only sell the fonts and your CMS add-on as part of a software bundle. (See 1.4
for details and examples about selling bundles).
1.23 Can OFL fonts be included in services that deliver fonts to the desktop
from remote repositories? Even if they contain both OFL and non-OFL fonts?
Yes. Some foundries have set up services to deliver fonts to subscribers
directly to desktops from their online repositories; similarly, plugins are
available to preview and use fonts directly in your design tool or publishing
suite. These services may mix open and restricted fonts in the same channel,
however they should make a clear distinction between them to users. These
services should also not hinder users (such as through DRM or obfuscation
mechanisms) from extracting and using the OFL fonts in other environments, or
continuing to use OFL fonts after subscription terms have ended, as those uses
are specifically allowed by the OFL.
1.24 Can services that provide or distribute OFL fonts restrict my use of them?
No. The terms of use of such services cannot replace or restrict the terms of
the OFL, as that would be the same as distributing the fonts under a different
license, which is not allowed. You are still entitled to use, modify and
redistribute them as the original authors have intended outside of the sole
control of that particular distribution channel. Note, however, that the fonts
provided by these services may differ from the Original Versions.
2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEB FONT SERVICES
NOTE: This section often refers to a separate paper on 'Web Fonts & RFNs'. This
is available at http://scripts.sil.org/OFL_web_fonts_and_RFNs
2.1 Can I make webpages using these fonts?
Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three
best options are:
- referring directly in your stylesheet to open fonts which may be available on
the user's system
- providing links to download the full package of the font - either from your
own website or from elsewhere - so users can install it themselves
- using @font-face to distribute the font directly to browsers. This is
recommended and explicitly allowed by the licensing model because it is
distribution. The font file itself is distributed with other components of the
webpage. It is not embedded in the webpage but referenced through a web address
which will cause the browser to retrieve and use the corresponding font to
render the webpage (see 1.11 and 1.15 for details related to embedding fonts
into documents). As you take advantage of the @font-face cross-platform
standard, be aware that web fonts are often tuned for a web environment and not
intended for installation and use outside a browser. The reasons in favour of
using web fonts are to allow design of dynamic text elements instead of static
graphics, to make it easier for content to be localized and translated, indexed
and searched, and all this with cross-platform open standards without depending
on restricted extensions or plugins. You should check the CSS cascade (the
order in which fonts are being called or delivered to your users) when testing.
2.2 Can I make and use WOFF (Web Open Font Format) versions of OFL fonts?
Yes, but you need to be careful. A change in font format normally is considered
modification, and Reserved Font Names (RFNs) cannot be used. Because of the
design of the WOFF format, however, it is possible to create a WOFF version
that is not considered modification, and so would not require a name change.
You are allowed to create, use and distribute a WOFF version of an OFL font
without changing the font name, but only if:
- the original font data remains unchanged except for WOFF compression, and
- WOFF-specific metadata is either omitted altogether or present and includes,
unaltered, the contents of all equivalent metadata in the original font.
If the original font data or metadata is changed, or the WOFF-specific metadata
is incomplete, the font must be considered a Modified Version, the OFL
restrictions would apply and the name of the font must be changed: any RFNs
cannot be used and copyright notices and licensing information must be included
and cannot be deleted or modified. You must come up with a unique name - we
recommend one corresponding to your domain or your particular web application.
Be aware that only the original author(s) can use RFNs. This is to prevent
collisions between a derivative tuned to your audience and the original
upstream version and so to reduce confusion.
Please note that most WOFF conversion tools and online services do not meet the
two requirements listed above, and so their output must be considered a
Modified Version. So be very careful and check to be sure that the tool or
service you're using is compressing unchanged data and completely and
accurately reflecting the original font metadata.
2.3 What about other web font formats such as EOT/EOTLite/CWT/etc.?
In most cases these formats alter the original font data more than WOFF, and do
not completely support appropriate metadata, so their use must be considered
modification and RFNs may not be used. However, there may be certain formats or
usage scenarios that may allow the use of RFNs. See
http://scripts.sil.org/OFL_web_fonts_and_RFNs
2.4 Can I make OFL fonts available through web font online services?
Yes, you are welcome to include OFL fonts in online web font services as long
as you properly meet all the conditions of the license. The origin and open
status of the font should be clear among the other fonts you are hosting.
Authorship, copyright notices and license information must be sufficiently
visible to your users or subscribers so they know where the font comes from and
the rights granted by the author(s). Make sure the font file contains the
needed copyright notice(s) and licensing information in its metadata. Please
double-check the accuracy of every field to prevent contradictory information.
Other font formats, including EOT/EOTLite/CWT and superior alternatives like
WOFF, already provide fields for this information. Remember that if you modify
the font within your library or convert it to another format for any reason the
OFL restrictions apply and you need to change the names accordingly. Please
respect the author's wishes as expressed in the OFL and do not misrepresent
original designers and their work. Don't lump quality open fonts together with
dubious freeware or public domain fonts. Consider how you can best work with
the original designers and foundries, support their efforts and generate
goodwill that will benefit your service. (See 1.17 for details related to
URL-based access restrictions methods or DRM mechanisms).
2.5 Some web font formats and services provide ways of "optimizing" the font
for a particular website or web application; is that allowed?
Yes, it is permitted, but remember that these optimized versions are Modified
Versions and so must follow OFL requirements like appropriate renaming. Also
you need to bear in mind the other important parameters beyond compression,
speed and responsiveness: you need to consider the audience of your particular
website or web application, as choosing some optimization parameters may turn
out to be less than ideal for them. Subsetting by removing certain glyphs or
features may seriously limit functionality of the font in various languages
that your users expect. It may also introduce degradation of quality in the
rendering or specific bugs on the various target platforms compared to the
original font from upstream. In other words, remember that one person's
optimized font may be another person's missing feature. Various advanced
typographic features (OpenType, Graphite or AAT) are also available through CSS
and may provide the desired effects without the need to modify the font.
2.6 Is subsetting a web font considered modification?
Yes. Removing any parts of the font when delivering a web font to a browser,
including unused glyphs and smart font code, is considered modification. This
is permitted by the OFL but would not normally allow the use of RFNs. Some
newer subsetting technologies may be able to subset in a way that allows users
to effectively have access to the complete font, including smart font
behaviour. See 2.8 and http://scripts.sil.org/OFL_web_fonts_and_RFNs
2.7 Are there any situations in which a modified web font could use RFNs?
Yes. If a web font is optimized only in ways that preserve Functional
Equivalence (see 2.8), then it may use RFNs, as it reasonably represents the
Original Version and respects the intentions of the author(s) and the main
purposes of the RFN mechanism (avoids collisions, protects authors, minimizes
support, encourages derivatives). However this is technically very difficult
and often impractical, so a much better scenario is for the web font service or
provider to sign a separate agreement with the author(s) that allows the use of
RFNs for Modified Versions.
2.8 How do you know if an optimization to a web font preserves Functional
Equivalence?
Functional Equivalence is described in full in the 'Web fonts and RFNs' paper
at http://scripts.sil.org/OFL_web_fonts_and_RFNs, in general, an optimized font
is deemed to be Functionally Equivalent (FE) to the Original Version if it:
- Supports the same full character inventory. If a character can be properly
displayed using the Original Version, then that same character, encoded
correctly on a web page, will display properly.
- Provides the same smart font behavior. Any dynamic shaping behavior that
works with the Original Version should work when optimized, unless the browser
or environment does not support it. There does not need to be guaranteed
support in the client, but there should be no forced degradation of smart font
or shaping behavior, such as the removal or obfuscation of OpenType, Graphite
or AAT tables.
- Presents text with no obvious degradation in visual quality. The lettershapes
should be equally (or more) readable, within limits of the rendering platform.
- Preserves original author, project and license metadata. At a minimum, this
should include: Copyright and authorship; The license as stated in the Original
Version, whether that is the full text of the OFL or a link to the web version;
Any RFN declarations; Information already present in the font or documentation
that points back to the Original Version, such as a link to the project or the
author's website.
If an optimized font meets these requirements, and so is considered to be FE,
then it's very likely that the original author would feel that the optimized
font is a good and reasonable equivalent. If it falls short of any of these
requirements, the optimized font does not reasonably represent the Original
Version, and so should be considered to be a Modified Version. Like other
Modified Versions, it would not be allowed to use any RFNs and you simply need
to pick your own font name.
2.9 Isn't use of web fonts another form of embedding?
No. Unlike embedded fonts in a PDF, web fonts are not an integrated part of the
document itself. They are not specific to a single document and are often
applied to thousands of documents around the world. The font data is not stored
alongside the document data and often originates from a different location. The
ease by which the web fonts used by a document may be identified and downloaded
for desktop use demonstrates that they are philosophically and technically
separate from the web pages that specify them. See
http://scripts.sil.org/OFL_web_fonts_and_RFNs
2.10 So would it be better to not use RFNs at all if you want your font to be
distributed by a web fonts service?
No. Although the OFL does not require authors to use RFNs, the RFN mechanism is
an important part of the OFL model and completely compatible with web font
services. If that web font service modifies the fonts, then the best solution
is to sign a separate agreement for the use of any RFNs. It is perfectly valid
for an author to not declare any RFNs, but before they do so they need to fully
understand the benefits they are giving up, and the overall negative effect of
allowing many different versions bearing the same name to be widely
distributed. As a result, we don't generally recommend it.
2.11 What should an agreement for the use of RFNs say? Are there any examples?
There is no prescribed format for this agreement, as legal systems vary, and no
recommended examples. Authors may wish to add specific clauses to further
restrict use, require author review of Modified Versions, establish user
support mechanisms or provide terms for ending the agreement. Such agreements
are usually not public, and apply only to the main parties. However, it would
be very beneficial for web font services to clearly state when they have
established such agreements, so that the public understands clearly that their
service is operating appropriately.
See the separate paper on 'Web Fonts & RFNs' for in-depth discussion of issues
related to the use of RFNs for web fonts. This is available at
http://scripts.sil.org/OFL_web_fonts_and_RFNs
3 MODIFYING OFL-LICENSED FONTS
3.1 Can I change the fonts? Are there any limitations to what things I can and
cannot change?
You are allowed to change anything, as long as such changes do not violate the
terms of the license. In other words, you are not allowed to remove the
copyright statement(s) from the font, but you could put additional information
into it that covers your contribution. See the placeholders in the OFL header
template for recommendations on where to add your own statements. (Remember
that, when authors have reserved names via the RFN mechanism, you need to
change the internal names of the font to your own font name when making your
modified version even if it is just a small change.)
3.2 I have a font that needs a few extra glyphs - can I take them from an OFL
licensed font and copy them into mine?
Yes, but if you distribute that font to others it must be under the OFL, and
include the information mentioned in condition 2 of the license.
3.3 Can I charge people for my additional work? In other words, if I add a
bunch of special glyphs or OpenType/Graphite/AAT code, can I sell the enhanced
font?
Not by itself. Derivative fonts must be released under the OFL and cannot be
sold by themselves. It is permitted, however, to include them in a larger
software package (such as text editors, office suites or operating systems),
even if the larger package is sold. In that case, you are strongly encouraged,
but not required, to also make that derived font easily and freely available
outside of the larger package.
3.4 Can I pay someone to enhance the fonts for my use and distribution?
Yes. This is a good way to fund the further development of the fonts. Keep in
mind, however, that if the font is distributed to others it must be under the
OFL. You won't be able to recover your investment by exclusively selling the
font, but you will be making a valuable contribution to the community. Please
remember how you have benefited from the contributions of others.
3.5 I need to make substantial revisions to the font to make it work with my
program. It will be a lot of work, and a big investment, and I want to be sure
that it can only be distributed with my program. Can I restrict its use?
No. If you redistribute a Modified Version of the font it must be under the
OFL. You may not restrict it in any way beyond what the OFL permits and
requires. This is intended to ensure that all released improvements to the
fonts become available to everyone. But you will likely get an edge over
competitors by being the first to distribute a bundle with the enhancements.
Again, please remember how you have benefited from the contributions of others.
3.6 Do I have to make any derivative fonts (including extended source files,
build scripts, documentation, etc.) publicly available?
No, but please consider sharing your improvements with others. You may find
that you receive in return more than what you gave.
3.7 If a trademark is claimed in the OFL font, does that trademark need to
remain in modified fonts?
Yes. Any trademark notices must remain in any derivative fonts to respect
trademark laws, but you may add any additional trademarks you claim, officially
registered or not. For example if an OFL font called "Foo" contains a notice
that "Foo is a trademark of Acme", then if you rename the font to "Bar" when
creating a Modified Version, the new trademark notice could say "Foo is a
trademark of Acme Inc. - Bar is a trademark of Roadrunner Technologies Ltd.".
Trademarks work alongside the OFL and are not subject to the terms of the
licensing agreement. The OFL does not grant any rights under trademark law.
Bear in mind that trademark law varies from country to country and that there
are no international trademark conventions as there are for copyright. You may
need to significantly invest in registering and defending a trademark for it to
remain valid in the countries you are interested in. This may be costly for an
individual independent designer.
3.8 If I commit changes to a font (or publish a branch in a DVCS) as part of a
public open source software project, do I have to change the internal font
names?
Only if there are declared RFNs. Making a public commit or publishing a public
branch is effectively redistributing your modifications, so any change to the
font will require that you do not use the RFNs. Even if there are no RFNs, it
may be useful to change the name or add a suffix indicating that a particular
version of the font is still in development and not released yet. This will
clearly indicate to users and fellow designers that this particular font is not
ready for release yet. See section 5 for more details.
4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
4.1 Can I use the SIL OFL for my own fonts?
Yes! We heartily encourage everyone to use the OFL to distribute their own
original fonts. It is a carefully constructed license that allows great freedom
along with enough artistic integrity protection for the work of the authors as
well as clear rules for other contributors and those who redistribute the
fonts. The licensing model is used successfully by various organisations, both
for-profit and not-for-profit, to release fonts of varying levels of scope and
complexity.
4.2 What do I have to do to apply the OFL to my font?
If you want to release your fonts under the OFL, we recommend you do the
following:
4.2.1 Put your copyright and Reserved Font Names information at the beginning
of the main OFL.txt file in place of the dedicated placeholders (marked with
the <> characters). Include this file in your release package.
4.2.2 Put your copyright and the OFL text with your chosen Reserved Font
Name(s) into your font files (the copyright and license fields). A link to the
OFL text on the OFL web site is an acceptable (but not recommended)
alternative. Also add this information to any other components (build scripts,
glyph databases, documentation, test files, etc). Accurate metadata in your
font files is beneficial to you as an increasing number of applications are
exposing this information to the user. For example, clickable links can bring
users back to your website and let them know about other work you have done or
services you provide. Depending on the format of your fonts and sources, you
can use template human-readable headers or machine-readable metadata. You
should also double-check that there is no conflicting metadata in the font
itself contradicting the license, such as the fstype bits in the os2 table or
fields in the name table.
4.2.3 Write an initial FONTLOG.txt for your font and include it in the release
package (see Section 6 and Appendix A for details including a template).
4.2.4 Include the relevant practical documentation on the license by adding
the current OFL-FAQ.txt file in your package.
4.2.5 If you wish you can use the OFL graphics
(http://scripts.sil.org/OFL_logo) on your website.
4.3 Will you make my font OFL for me?
We won't do the work for you. We can, however, try to answer your questions,
unfortunately we do not have the resources to review and check your font
packages for correct use of the OFL. We recommend you turn to designers,
foundries or consulting companies with experience in doing open font design to
provide this service to you.
4.4 Will you distribute my OFL font for me?
No, although if the font is of sufficient quality and general interest we may
include a link to it on our partial list of OFL fonts on the OFL web site. You
may wish to consider other open font catalogs or hosting services, such as the
Unifont Font Guide (http://unifont.org/fontguide), The League of Movable Type
(http://theleagueofmovabletype.com) or the Open Font Library
(http://openfontlibrary.org/), which despite the name has no direct
relationship to the OFL or SIL. We do not endorse any particular catalog or
hosting service - it is your responsibility to determine if the service is
right for you and if it treats authors with fairness.
4.5 Why should I use the OFL for my fonts?
- to meet needs for fonts that can be modified to support lesser-known languages
- to provide a legal and clear way for people to respect your work but still
use it (and reduce piracy)
- to involve others in your font project
- to enable your fonts to be expanded with new weights and improved writing
system/language support
- to allow more technical font developers to add features to your design (such
as OpenType, Graphite or AAT support)
- to renew the life of an old font lying on your hard drive with no business
model
- to allow your font to be included in Libre Software operating systems like
Ubuntu
- to give your font world status and wide, unrestricted distribution
- to educate students about quality typeface and font design
- to expand your test base and get more useful feedback
- to extend your reach to new markets when users see your metadata and go to
your website
- to get your font more easily into one of the web font online services
- to attract attention for your commercial fonts
- to make money through web font services
- to make money by bundling fonts with applications
- to make money adjusting and extending existing open fonts
- to get a better chance that foundations/NGOs/charities/companies who
commission fonts will pick you
- to be part of a sharing design and development community
- to give back and contribute to a growing body of font sources
5 CHOOSING RESERVED FONT NAMES
5.1 What are Reserved Font Names?
These are font names, or portions of font names, that the author has chosen to
reserve for use only with the Original Version of the font, or for Modified
Version(s) created by the original author.
5.2 Why can't I use the Reserved Font Names in my derivative font names? I'd
like people to know where the design came from.
The best way to acknowledge the source of the design is to thank the original
authors and any other contributors in the files that are distributed with your
revised font (although no acknowledgement is required). The FONTLOG is a
natural place to do this. Reserved Font Names ensure that the only fonts that
have the original names are the unmodified Original Versions. This allows
designers to maintain artistic integrity while allowing collaboration to
happen. It eliminates potential confusion and name conflicts. When choosing a
name, be creative and avoid names that reuse almost all the same letters in the
same order or sound like the original. It will help everyone if Original
Versions and Modified Versions can easily be distinguished from one another and
from other derivatives. Any substitution and matching mechanism is outside the
scope of the license.
5.3 What do you mean by "primary name as presented to the user"? Are you
referring to the font menu name?
Yes, this applies to the font menu name and other mechanisms that specify a
font in a document. It would be fine, however, to keep a text reference to the
original fonts in the description field, in your modified source file or in
documentation provided alongside your derivative as long as no one could be
confused that your modified source is the original. But you cannot use the
Reserved Font Names in any way to identify the font to the user (unless the
Copyright Holder(s) allow(s) it through a separate agreement). Users who
install derivatives (Modified Versions) on their systems should not see any of
the original Reserved Font Names in their font menus, for example. Again, this
is to ensure that users are not confused and do not mistake one font for
another and so expect features only another derivative or the Original Version
can actually offer.
5.4 Am I not allowed to use any part of the Reserved Font Names?
You may not use individual words from the Reserved Font Names, but you would be
allowed to use parts of words, as long as you do not use any word from the
Reserved Font Names entirely. We do not recommend using parts of words because
of potential confusion, but it is allowed. For example, if "Foobar" was a
Reserved Font Name, you would be allowed to use "Foo" or "bar", although we
would not recommend it. Such an unfortunate choice would confuse the users of
your fonts as well as make it harder for other designers to contribute.
5.5 So what should I, as an author, identify as Reserved Font Names?
Original authors are encouraged to name their fonts using clear, distinct
names, and only declare the unique parts of the name as Reserved Font Names.
For example, the author of a font called "Foobar Sans" would declare "Foobar"
as a Reserved Font Name, but not "Sans", as that is a common typographical
term, and may be a useful word to use in a derivative font name. Reserved Font
Names should also be single words for simplicity and legibility. A font called
"Flowing River" should have Reserved Font Names "Flowing" and "River", not
"Flowing River". You also need to be very careful about reserving font names
which are already linked to trademarks (whether registered or not) which you do
not own.
5.6 Do I, as an author, have to identify any Reserved Font Names?
No. RFNs are optional and not required, but we encourage you to use them. This
is primarily to avoid confusion between your work and Modified Versions. As an
author you can release a font under the OFL and not declare any Reserved Font
Names. There may be situations where you find that using no RFNs and letting
your font be changed and modified - including any kind of modification -
without having to change the original name is desirable. However you need to be
fully aware of the consequences. There will be no direct way for end-users and
other designers to distinguish your Original Version from many Modified
Versions that may be created. You have to trust whoever is making the changes
and the optimizations to not introduce problematic changes. The RFNs you choose
for your own creation have value to you as an author because they allow you to
maintain artistic integrity and keep some control over the distribution channel
to your end-users. For discussion of RFNs and web fonts see section 2.
5.7 Are any names (such as the main font name) reserved by default?
No. That is a change to the license as of version 1.1. If you want any names to
be Reserved Font Names, they must be specified after the copyright statement(s).
5.8 Is there any situation in which I can use Reserved Font Names for a
Modified Version?
The Copyright Holder(s) can give certain trusted parties the right to use any
of the Reserved Font Names through separate written agreements. For example,
even if "Foobar" is a RFN, you could write up an agreement to give company
"XYZ" the right to distribute a modified version with a name that includes
"Foobar". This allows for freedom without confusion. The existence of such an
agreement should be made as clear as possible to downstream users and designers
in the distribution package and the relevant documentation. They need to know
if they are a party to the agreement or not and what they are practically
allowed to do or not even if all the details of the agreement are not public.
5.9 Do font rebuilds require a name change? Do I have to change the name of
the font when my packaging workflow includes a full rebuild from source?
Yes, all rebuilds which change the font data and the smart code are Modified
Versions and the requirements of the OFL apply: you need to respect what the
Author(s) have chosen in terms of Reserved Font Names. However if a package (or
installer) is simply a wrapper or a compressed structure around the final font
- leaving them intact on the inside - then no name change is required. Please
get in touch with the author(s) and copyright holder(s) to inquire about the
presence of font sources beyond the final font file(s) and the recommended
build path. That build path may very well be non-trivial and hard to reproduce
accurately by the maintainer. If a full font build path is made available by
the upstream author(s) please be aware that any regressions and changes you may
introduce when doing a rebuild for packaging purposes is your own
responsibility as a package maintainer since you are effectively creating a
separate branch. You should make it very clear to your users that your rebuilt
version is not the canonical one from upstream.
5.10 Can I add other Reserved Font Names when making a derivative font?
Yes. List your additional Reserved Font Names after your additional copyright
statement, as indicated with example placeholders at the top of the OFL.txt
file. Be sure you do not remove any existing RFNs but only add your own. RFN
statements should be placed next to the copyright statement of the relevant
author as indicated in the OFL.txt template to make them visible to designers
wishing to make their separate version.
6 ABOUT THE FONTLOG
6.1 What is this FONTLOG thing exactly?
It has three purposes: 1) to provide basic information on the font to users and
other designers and developers, 2) to document changes that have been made to
the font or accompanying files, either by the original authors or others, and
3) to provide a place to acknowledge authors and other contributors. Please use
it!
6.2 Is the FONTLOG required?
It is not a requirement of the license, but we strongly recommend you have one.
6.3 Am I required to update the FONTLOG when making Modified Versions?
No, but users, designers and other developers might get very frustrated with
you if you don't. People need to know how derivative fonts differ from the
original, and how to take advantage of the changes, or build on them. There are
utilities that can help create and maintain a FONTLOG, such as the FONTLOG
support in FontForge.
6.4 What should the FONTLOG look like?
It is typically a separate text file (FONTLOG.txt), but can take other formats.
It commonly includes these four sections:
- brief header describing the FONTLOG itself and name of the font family
- Basic Font Information - description of the font family, purpose and breadth
- ChangeLog - chronological listing of changes
- Acknowledgements - list of authors and contributors with contact information
It could also include other sections, such as: where to find documentation, how
to make contributions, information on contributing organizations, source code
details, and a short design guide. See Appendix A for an example FONTLOG.
7 MAKING CONTRIBUTIONS TO OFL PROJECTS
7.1 Can I contribute work to OFL projects?
In many cases, yes. It is common for OFL fonts to be developed by a team of
people who welcome contributions from the wider community. Contact the original
authors for specific information on how to participate in their projects.
7.2 Why should I contribute my changes back to the original authors?
It would benefit many people if you contributed back in response to what you've
received. Your contributions and improvements to the fonts and other components
could be a tremendous help and would encourage others to contribute as well and
'give back'. You will then benefit from other people's contributions as well.
Sometimes maintaining your own separate version takes more effort than merging
back with the original. Be aware that any contributions, however, must be
either your own original creation or work that you own, and you may be asked to
affirm that clearly when you contribute.
7.3 I've made some very nice improvements to the font. Will you consider
adopting them and putting them into future Original Versions?
Most authors would be very happy to receive such contributions. Keep in mind
that it is unlikely that they would want to incorporate major changes that
would require additional work on their end. Any contributions would likely need
to be made for all the fonts in a family and match the overall design and
style. Authors are encouraged to include a guide to the design with the fonts.
It would also help to have contributions submitted as patches or clearly marked
changes - the use of smart source revision control systems like subversion,
mercurial, git or bzr is a good idea. Please follow the recommendations given
by the author(s) in terms of preferred source formats and configuration
parameters for sending contributions. If this is not indicated in a FONTLOG or
other documentation of the font, consider asking them directly. Examples of
useful contributions are bug fixes, additional glyphs, stylistic alternates
(and the smart font code to access them) or improved hinting. Keep in mind that
some kinds of changes (esp. hinting) may be technically difficult to integrate.
7.4 How can I financially support the development of OFL fonts?
It is likely that most authors of OFL fonts would accept financial
contributions - contact them for instructions on how to do this. Such
contributions would support future development. You can also pay for others to
enhance the fonts and contribute the results back to the original authors for
inclusion in the Original Version.
8 ABOUT THE LICENSE ITSELF
8.1 I see that this is version 1.1 of the license. Will there be later changes?
Version 1.1 is the first minor revision of the OFL. We are confident that
version 1.1 will meet most needs, but are open to future improvements. Any
revisions would be for future font releases, and previously existing licenses
would remain in effect. No retroactive changes are possible, although the
Copyright Holder(s) can re-release the font under a revised OFL. All versions
will be available on our web site: http://scripts.sil.org/OFL.
8.2 Does this license restrict the rights of the Copyright Holder(s)?
No. The Copyright Holder(s) still retain(s) all the rights to their creation;
they are only releasing a portion of it for use in a specific way. For example,
the Copyright Holder(s) may choose to release a 'basic' version of their font
under the OFL, but sell a restricted 'enhanced' version under a different
license. They may also choose to release the same font under both the OFL and
some other license. Only the Copyright Holder(s) can do this, and doing so does
not change the terms of the OFL as it applies to that font.
8.3 Is the OFL a contract or a license?
The OFL is a worldwide license based on international copyright agreements and
conventions. It is not a contract and so does not require you to sign it to
have legal validity. By using, modifying and redistributing components under
the OFL you indicate that you accept the license.
8.4 I really like the terms of the OFL, but want to change it a little. Am I
allowed to take ideas and actual wording from the OFL and put them into my own
custom license for distributing my fonts?
We strongly recommend against creating your very own unique open licensing
model. Using a modified or derivative license will likely cut you off - along
with the font(s) under that license - from the community of designers using the
OFL, potentially expose you and your users to legal liabilities, and possibly
put your work and rights at risk. The OFL went though a community and legal
review process that took years of effort, and that review is only applicable to
an unmodified OFL. The text of the OFL has been written by SIL (with review and
consultation from the community) and is copyright (c) 2005-2017 SIL
International. You may re-use the ideas and wording (in part, not in whole) in
another non-proprietary license provided that you call your license by another
unambiguous name, that you do not use the preamble, that you do not mention SIL
and that you clearly present your license as different from the OFL so as not
to cause confusion by being too similar to the original. If you feel the OFL
does not meet your needs for an open license, please contact us.
8.5 Can I quote from the OFL FAQ?
Yes, SIL gives permission to quote from the OFL FAQ (OFL-FAQ.txt), in whole or
in part, provided that the quoted text is:
- unmodified,
- used to help explain the intent of the OFL, rather than cause
misunderstanding, and
- accompanied with the following attribution: "From the OFL FAQ (OFL-FAQ.txt),
copyright (c) 2005-2017 SIL International. Used by permission.
http://scripts.sil.org/OFL-FAQ_web".
8.6 Can I translate the license and the FAQ into other languages?
SIL certainly recognises the need for people who are not familiar with English
to be able to understand the OFL and its use. Making the license very clear and
readable has been a key goal for the OFL, but we know that people understand
their own language best.
If you are an experienced translator, you are very welcome to translate the OFL
and OFL-FAQ so that designers and users in your language community can
understand the license better. But only the original English version of the
license has legal value and has been approved by the community. Translations do
not count as legal substitutes and should only serve as a way to explain the
original license. SIL - as the author and steward of the license for the
community at large - does not approve any translation of the OFL as legally
valid because even small translation ambiguities could be abused and create
problems.
SIL gives permission to publish unofficial translations into other languages
provided that they comply with the following guidelines:
- Put the following disclaimer in both English and the target language stating
clearly that the translation is unofficial:
"This is an unofficial translation of the SIL Open Font License into
. It was not published by SIL International, and does not
legally state the distribution terms for fonts that use the OFL. A release
under the OFL is only valid when using the original English text. However, we
recognize that this unofficial translation will help users and designers not
familiar with English to better understand and use the OFL. We encourage
designers who consider releasing their creation under the OFL to read the
OFL-FAQ in their own language if it is available. Please go to
http://scripts.sil.org/OFL for the official version of the license and the
accompanying OFL-FAQ."
- Keep your unofficial translation current and update it at our request if
needed, for example if there is any ambiguity which could lead to confusion.
If you start such a unofficial translation effort of the OFL and OFL-FAQ please
let us know.
8.7 Does the OFL have an explicit expiration term?
No, the implicit intent of the OFL is that the permissions granted are
perpetual and irrevocable.
9 ABOUT SIL INTERNATIONAL
9.1 Who is SIL International and what do they do?
SIL serves language communities worldwide, building their capacity for
sustainable language development, by means of research, translation, training
and materials development. SIL makes its services available to all without
regard to religious belief, political ideology, gender, race, or ethnic
background. SIL's members and volunteers share a Christian commitment.
9.2 What does this have to do with font licensing?
The ability to read, write, type and publish in one's own language is one of
the most critical needs for millions of people around the world. This requires
fonts that are widely available and support lesser-known languages. SIL
develops - and encourages others to develop - a complete stack of writing
systems implementation components available under open licenses. This open
stack includes input methods, smart fonts, smart rendering libraries and smart
applications. There has been a need for a common open license that is
specifically applicable to fonts and related software (a crucial component of
this stack), so SIL developed the SIL Open Font License with the help of the
Free/Libre and Open Source Software community.
9.3 How can I contact SIL?
Our main web site is: http://www.sil.org/
Our site about complex scripts is: http://scripts.sil.org/
Information about this license (and contact information) is at:
http://scripts.sil.org/OFL
APPENDIX A - FONTLOG EXAMPLE
Here is an example of the recommended format for a FONTLOG, although other
formats are allowed.
-----
FONTLOG for the GlobalFontFamily fonts
This file provides detailed information on the GlobalFontFamily Font Software.
This information should be distributed along with the GlobalFontFamily fonts
and any derivative works.
Basic Font Information
GlobalFontFamily is a Unicode typeface family that supports all languages that
use the Latin script and its variants, and could be expanded to support other
scripts.
NewWorldFontFamily is based on the GlobalFontFamily and also supports Greek,
Hebrew, Cyrillic and Armenian.
More specifically, this release supports the following Unicode ranges...
This release contains...
Documentation can be found at...
To contribute to the project...
ChangeLog
10 December 2010 (Fred Foobar) GlobalFontFamily-devel version 1.4
- fix new build and testing system (bug #123456)
1 August 2008 (Tom Parker) GlobalFontFamily version 1.2.1
- Tweaked the smart font code (Branch merged with trunk version)
- Provided improved build and debugging environment for smart behaviours
7 February 2007 (Pat Johnson) NewWorldFontFamily Version 1.3
- Added Greek and Cyrillic glyphs
7 March 2006 (Fred Foobar) NewWorldFontFamily Version 1.2
- Tweaked contextual behaviours
1 Feb 2005 (Jane Doe) NewWorldFontFamily Version 1.1
- Improved build script performance and verbosity
- Extended the smart code documentation
- Corrected minor typos in the documentation
- Fixed position of combining inverted breve below (U+032F)
- Added OpenType/Graphite smart code for Armenian
- Added Armenian glyphs (U+0531 -> U+0587)
- Released as "NewWorldFontFamily"
1 Jan 2005 (Joe Smith) GlobalFontFamily Version 1.0
- Initial release
Acknowledgements
If you make modifications be sure to add your name (N), email (E), web-address
(if you have one) (W) and description (D). This list is in alphabetical order.
N: Jane Doe
E: jane@university.edu
W: http://art.university.edu/projects/fonts
D: Contributor - Armenian glyphs and code
N: Fred Foobar
E: fred@foobar.org
W: http://foobar.org
D: Contributor - misc Graphite fixes
N: Pat Johnson
E: pat@fontstudio.org
W: http://pat.fontstudio.org
D: Designer - Greek & Cyrillic glyphs based on Roman design
N: Tom Parker
E: tom@company.com
W: http://www.company.com/tom/projects/fonts
D: Engineer - original smart font code
N: Joe Smith
E: joe@fontstudio.org
W: http://joe.fontstudio.org
D: Designer - original Roman glyphs
Fontstudio.org is an not-for-profit design group whose purpose is...
Foobar.org is a distributed community of developers...
Company.com is a small business who likes to support community designers...
University.edu is a renowned educational institution with a strong design
department...
-----
4 ABOUT MAKING CONTRIBUTIONS
4.1 Why should I contribute my changes back to the original authors?
It would benefit many people if you contributed back to what you've
received. Providing your contributions and improvements to the fonts and
other components (data files, source code, build scripts, documentation,
etc.) could be a tremendous help and would encourage others to contribute as
well and 'give back', which means you will have an opportunity to benefit
from other people's contributions as well. Sometimes maintaining your own
separate version takes more effort than merging back with the original. Be
aware that any contributions, however, must be either your own original
creation or work that you own, and you may be asked to affirm that clearly
when you contribute.
4.2 I've made some very nice improvements to the font, will you consider
adopting them and putting them into future Original Versions?
Most authors would be very happy to receive such contributions. Keep in mind
that it is unlikely that they would want to incorporate major changes that
would require additional work on their end. Any contributions would likely
need to be made for all the fonts in a family and match the overall design
and style. Authors are encouraged to include a guide to the design with the
fonts. It would also help to have contributions submitted as patches or
clearly marked changes (the use of smart source revision control systems
like subversion, svk, mercurial, git or bzr is a good idea). Examples of
useful contributions are bug fixes, additional glyphs, stylistic alternates
(and the smart font code to access them) or improved hinting.
4.3 How can I financially support the development of OFL fonts?
It is likely that most authors of OFL fonts would accept financial
contributions - contact them for instructions on how to do this. Such
contributions would support future development. You can also pay for others
to enhance the fonts and contribute the results back to the original authors
for inclusion in the Original Version.
5 ABOUT THE LICENSE
5.1 I see that this is version 1.1 of the license. Will there be later
changes?
Version 1.1 is the first minor revision of the OFL. We are confident that
version 1.1 will meet most needs, but are open to future improvements. Any
revisions would be for future font releases, and previously existing
licenses would remain in effect. No retroactive changes are possible,
although the Copyright Holder(s) can re-release the font under a revised
OFL. All versions will be available on our web site:
http://scripts.sil.org/OFL.
5.2 Can I use the SIL Open Font License for my own fonts?
Yes! We heartily encourage anyone to use the OFL to distribute their own
original fonts. It is a carefully constructed license that allows great
freedom along with enough artistic integrity protection for the work of the
authors as well as clear rules for other contributors and those who
redistribute the fonts. Some additional information about using the OFL is
included at the end of this FAQ.
5.3 Does this license restrict the rights of the Copyright Holder(s)?
No. The Copyright Holder(s) still retain(s) all the rights to their
creation; they are only releasing a portion of it for use in a specific way.
For example, the Copyright Holder(s) may choose to release a 'basic' version
of their font under the OFL, but sell a restricted 'enhanced' version. Only
the Copyright Holder(s) can do this.
5.4 Is the OFL a contract or a license?
The OFL is a license and not a contract and so does not require you to sign
it to have legal validity. By using, modifying and redistributing components
under the OFL you indicate that you accept the license.
5.5 How about translating the license and the FAQ into other languages?
SIL certainly recognises the need for people who are not familiar with
English to be able to understand the OFL and this FAQ better in their own
language. Making the license very clear and readable is a key goal of the OFL.
If you are an experienced translator, you are very welcome to help by
translating the OFL and its FAQ so that designers and users in your language
community can understand the license better. But only the original English
version of the license has legal value and has been approved by the
community. Translations do not count as legal substitutes and should only
serve as a way to explain the original license. SIL - as the author and
steward of the license for the community at large - does not approve any
translation of the OFL as legally valid because even small translation
ambiguities could be abused and create problems.
We give permission to publish unofficial translations into other languages
provided that they comply with the following guidelines:
- put the following disclaimer in both English and the target language
stating clearly that the translation is unofficial:
"This is an unofficial translation of the SIL Open Font License into
$language. It was not published by SIL International, and does not legally
state the distribution terms for fonts that use the OFL. A release under the
OFL is only valid when using the original English text.
However, we recognize that this unofficial translation will help users and
designers not familiar with English to understand the SIL OFL better and
make it easier to use and release font families under this collaborative
font design model. We encourage designers who consider releasing their
creation under the OFL to read the FAQ in their own language if it is
available.
Please go to http://scripts.sil.org/OFL for the official version of the
license and the accompanying FAQ."
- keep your unofficial translation current and update it at our request if
needed, for example if there is any ambiguity which could lead to confusion.
If you start such a unofficial translation effort of the OFL and its
accompanying FAQ please let us know, thank you.
6 ABOUT SIL INTERNATIONAL
6.1 Who is SIL International and what does it do?
SIL International is a worldwide faith-based education and development
organization (NGO) that studies, documents, and assists in developing the
world's lesser-known languages through literacy, linguistics, translation,
and other academic disciplines. SIL makes its services available to all
without regard to religious belief, political ideology, gender, race, or
ethnic background. SIL's members and volunteers share a Christian commitment.
6.2 What does this have to do with font licensing?
The ability to read, write, type and publish in one's own language is one of
the most critical needs for millions of people around the world. This
requires fonts that are widely available and support lesser-known languages.
SIL develops - and encourages others to develop - a complete stack of
writing systems implementation components available under open licenses.
This open stack includes input methods, smart fonts, smart rendering
libraries and smart applications. There has been a need for a common open
license that is specifically applicable to fonts and related software (a
crucial component of this stack) so SIL developed the SIL Open Font License
with the help of the FLOSS community.
6.3 How can I contact SIL?
Our main web site is: http://www.sil.org/
Our site about complex scripts is: http://scripts.sil.org/
Information about this license (including contact email information) is at:
http://scripts.sil.org/OFL
7 ABOUT USING THE OFL FOR YOUR ORIGINAL FONTS
If you want to release your fonts under the OFL, you only need to do the
following:
7.1 Put your copyright and reserved font names information in the beginning
of the main OFL file (simply use the dedicated placeholders).
7.2 Put your copyright and the OFL references in your various font files
(such as in the copyright, license and description fields) and in your other
components (build scripts, glyph databases, documentation, rendering
samples, etc). Accurate metadata in your font files is beneficial to you as
an increasing number of applications are exposing this information to the
user. For example, clickable links can bring users back to your website and
let them know about other work you have done or services you provide.
Depending on the format of your fonts and sources, you can use template
human-readable headers or machine-readable metadata.
7.3 Write an initial FONTLOG for your font and include it in the release
package.
7.4 Include the OFL license file in your release package.
7.5 We also highly recommend you include the relevant practical
documentation on the license by putting the OFL-FAQ in your package.
7.6 If you wish, you can use the OFL Graphics on your web page.
That's all. If you have any more questions please get in touch with us.
