Toshiba BDX2700KU User Manual
Page 53
53
Others
O
THERS
These conditions apply to any software derived from or based on the FreeType Project, not just the unmodifi ed fi les. If you use our work, you
must acknowledge us. However, no fee need be paid to us.
3. Advertising
--------------
Neither the FreeType authors and contributors nor you shall use the name of the other for commercial, advertising, or promotional purposes
without specifi c prior written permission.
We suggest, but do not require, that you use one or more of the following phrases to refer to this software in your documentation or advertising
materials: `FreeType Project’, `FreeType Engine’, `FreeType library’, or `FreeType Distribution’.
As you have not signed this license, you are not required to accept it. However, as the FreeType Project is copyrighted material, only this
license, or another one contracted with the authors, grants you the right to use, distribute, and modify it. Therefore, by using, distributing, or
modifying the FreeType Project, you indicate that you understand and accept all the terms of this license.
4. Contacts
-----------
There are two mailing lists related to FreeType:
Discusses general use and applications of FreeType, as well as future and wanted additions to the library and distribution.
If you are looking for support, start in this list if you haven’t found anything to help you in the documentation.
Discusses bugs, as well as engine internals, design issues, specifi c licenses, porting, etc.
Our home page can be found at
http://www.freetype.org
--- end of FTL.TXT ---
Appendix H – Openssl License
LICENSE ISSUES
==============
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the
toolkit.
See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to
OpenSSL, please contact [email protected].
OpenSSL License
---------------
/* ====================================================================
Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modifi cation, 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. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software
developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)”
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to
endorse or promote products derived from this software without
prior written permission. For written permission, please contact [email protected].
5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission *
of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment: “This product includes software developed by the OpenSSL
Project for use in the OpenSSL Toolkit (http://www.openssl.org/)”
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS’’ AND ANY EXPRESSED 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 OpenSSL PROJECT OR ITS 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.
This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson
([email protected]).
*/