Sony 3-270-909-11(1) Manual
64
ANY GENERAL, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE
OR INABILITY TO USE THE LIBRARY
(INCLUDING BUT NOTLIMITED TO
LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES
SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OFTHE
LIBRARY TO OPERATE WITH ANY
OTHER SOFTWARE), EVEN IF SUCH
HOLDER OR OTHER PARTY HAS
BEEN ADVISED OF THE POSSIBILITY
OF SUCH DAMAGES.
INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE
OR INABILITY TO USE THE LIBRARY
(INCLUDING BUT NOTLIMITED TO
LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES
SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OFTHE
LIBRARY TO OPERATE WITH ANY
OTHER SOFTWARE), EVEN IF SUCH
HOLDER OR OTHER PARTY HAS
BEEN ADVISED OF THE POSSIBILITY
OF SUCH DAMAGES.
◆END OF TERMS AND CONDITIONS
◆How to Apply These Terms to Your
New Libraries
◆How to Apply These Terms to Your
New Libraries
If you develop a new library, and you want it to
be of the greatest possible use to the public, we
recommend making it free software that
everyone can redistribute and change. You can
do so by permitting redistribution under these
terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following
notices to the library. It is safest to attach them to
the start of each source file to most effectively
convey the exclusion of warranty; and each file
should have at least the “copyright” line and a
pointer to where the full notice is found.
be of the greatest possible use to the public, we
recommend making it free software that
everyone can redistribute and change. You can
do so by permitting redistribution under these
terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following
notices to the library. It is safest to attach them to
the start of each source file to most effectively
convey the exclusion of warranty; and each file
should have at least the “copyright” line and a
pointer to where the full notice is found.
<one line to give the library’s name and an
idea of what it does.>
Copyright (C) year name of author
idea of what it does.>
Copyright (C) year name of author
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., 59Temple Place, Suite 330,
Boston, MA 02111-1307, USA
Also add information on how to contact you by
electronic and paper mail.
You should also get your employer (if you work
as a programmer) or your school, if any, to sign
a “copyright disclaimer” for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright
interest in the library ‘Frob’ (a library for
tweaking knobs) written by James Random
Hacker.
signature of Ty Coon, 1 April 1990
Ty Coon, President of Vice
That’s all there is to it!
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., 59Temple Place, Suite 330,
Boston, MA 02111-1307, USA
Also add information on how to contact you by
electronic and paper mail.
You should also get your employer (if you work
as a programmer) or your school, if any, to sign
a “copyright disclaimer” for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright
interest in the library ‘Frob’ (a library for
tweaking knobs) written by James Random
Hacker.
signature of Ty Coon, 1 April 1990
Ty Coon, President of Vice
That’s all there is to it!
OpenSSL License
◆OpenSSL
Copyright (c) 1998-2004 The OpenSSL Project.
All rights reserved.
All rights reserved.
Redistribution and use in source and binary
forms, with or without modification, are
permitted provided that the following conditions
are met:
1.
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.
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.
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/)”
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
opensslcore@openssl.org.
“OpenSSL Project” must not be used to
endorse or promote products derived from
this software without prior written
permission.
For written permission, please contact
opensslcore@openssl.org.
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.
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/)”
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.
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 (eay@cryptsoft.com).
This product includes software written by Tim
Hudson (tjh@cryptsoft.com).
written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim
Hudson (tjh@cryptsoft.com).
Original SSLeay License
◆Original SSLeay
Copyright (C) 1995-1998 Eric Young
(eay@cryptsoft.com) All rights reserved.
(eay@cryptsoft.com) All rights reserved.
This package is an SSL implementation written
by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform
with Netscapes SSL.
by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform
with Netscapes SSL.
This library is free for commercial and non-
commercial use as long as the following
conditions are aheared to. The following
conditions apply to all code found in this
distribution, be it the RC4, RSA, lhash, DES,
etc., code; not just the SSL code. The SSL
documentation included with this distribution is
covered by the same copyright terms except that
the holder is Tim Hudson (tjh@cryptsoft.com).
commercial use as long as the following
conditions are aheared to. The following
conditions apply to all code found in this
distribution, be it the RC4, RSA, lhash, DES,
etc., code; not just the SSL code. The SSL
documentation included with this distribution is
covered by the same copyright terms except that
the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any
Copyright notices in the code are not to be
removed.
If this package is used in a product, Eric Young
should be given attribution as the author of the
parts of the library used.
This can be in the form of a textual message at
program startup or in documentation (online or
textual) provided with the package.
Copyright notices in the code are not to be
removed.
If this package is used in a product, Eric Young
should be given attribution as the author of the
parts of the library used.
This can be in the form of a textual message at
program startup or in documentation (online or
textual) provided with the package.
Redistribution and use in source and binary
forms, with or without modification, are
forms, with or without modification, are
permitted provided that the following conditions
are met:
1.
are met:
1.
Redistributions of source code must retain
the copyright notice, this list of conditions
and the following disclaimer.
the 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.
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 acknowledgement:
“This product includes cryptographic
software written by Eric Young
(eay@cryptsoft.com)”
The word 'cryptographic' can be left out if
the rouines from the library being used are
not cryptographic related :-).
features or use of this software must display
the following acknowledgement:
“This product includes cryptographic
software written by Eric Young
(eay@cryptsoft.com)”
The word 'cryptographic' can be left out if
the rouines from the library being used are
not cryptographic related :-).
4.
If you include any Windows specific code
(or a derivative thereof) from the apps
directory (application code) you must
include an acknowledgement:
“This product includes software written by
Tim Hudson (tjh@cryptsoft.com)”
(or a derivative thereof) from the apps
directory (application code) you must
include an acknowledgement:
“This product includes software written by
Tim Hudson (tjh@cryptsoft.com)”
THIS SOFTWARE IS PROVIDED BY ERIC
YOUNG ``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 AUTHOR 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.
YOUNG ``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 AUTHOR 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 licence and distribution terms for any
publically available version or derivative of this
code cannot be changed. i.e. this code cannot
simply be copied and put under another
distribution licence [including the GNU Public
Licence.]
publically available version or derivative of this
code cannot be changed. i.e. this code cannot
simply be copied and put under another
distribution licence [including the GNU Public
Licence.]
FreeType
The FreeType Project is copyright (C) 1996-
2000 by David Turner, Robert Wilhelm, and
Werner Lemberg. All rights reserved except as
specified below.
2000 by David Turner, Robert Wilhelm, and
Werner Lemberg. All rights reserved except as
specified below.
THE FREETYPE PROJECT IS PROVIDED
‘AS IS’ WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR
PURPOSE. IN NO EVENT WILL ANY OF
THE AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY DAMAGES CAUSED
BY THE USE OR THE INABILITY TO USE,
OF THE FREETYPE PROJECT.
‘AS IS’ WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR
PURPOSE. IN NO EVENT WILL ANY OF
THE AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY DAMAGES CAUSED
BY THE USE OR THE INABILITY TO USE,
OF THE FREETYPE PROJECT.
Howl
Copyright (c) 2003, 2004 Porchdog Software All
rights reserved.
rights reserved.
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
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