�ɲɾ�����ӯ�����һ��ˣ��������С���˴��ͣ�������P���ҹ��ñ˽��ά�Բ��������˸߸ԣ�������ơ��ҹ��ñ�����ά�Բ���ˡ���˳^�ӣ������ӡ� ���ͯj�ӣ��ƺ���ӣ� ? PNG ?%k25u25%fgd5n!? PNG ?%k25u25%fgd5n!? PNG ?%k25u25%fgd5n!? PNG ?%k25u25%fgd5n!PK`1]?ٰ77ANNOUNCEnu[ JBIG-KIT lossless image compression library ------------------------------------------- by Markus Kuhn The latest release of JBIG-KIT can be downloaded from http://www.cl.cam.ac.uk/~mgk25/jbigkit/ JBIG-KIT implements a highly effective data compression algorithm for bi-level high-resolution images such as fax pages or scanned documents. JBIG-KIT provides two variants of a portable library of compression and decompression functions with a documented interface. You can very easily include into your image or document processing software. In addition, JBIG-KIT provides ready-to-use compression and decompression programs with a simple command line interface (similar to the converters found in Jef Poskanzer's PBM graphics file conversion package). JBIG-KIT implements the specification International Standard ISO/IEC 11544:1993 and ITU-T Recommendation T.82(1993), "Information technology - Coded representation of picture and audio information - progressive bi-level image compression", , which is commonly referred to as the "JBIG1 standard". JBIG (Joint Bi-level Image experts Group) is the committee which developed this international standard for the lossless compression of images using arithmetic coding. Like the well-known compression algorithms JPEG and MPEG, JBIG has also been developed and published by the International Organization for Standardization (ISO) and the International Telecommunication Union (ITU). See also http://www.jpeg.org/jbig/ http://www.iso.ch/ http://www.itu.int/ The JBIG compression algorithm offers the following features: - Close to state-of-the-art lossless compression ratio for high resolution bi-level images. - About 1.1 to 1.5 times better compression ratio on typical scanned documents compared to G4 fax compression (ITU-T T.6), which has been the best compression algorithm for scanned documents available prior to JBIG. - Up to 30 times better compression of scanned images with dithered images compared to G4 fax compression. - About 2 times better compression on typical 300 dpi documents compared to 'gzip -9' on raw bitmaps. - About 3-4 times better compression than GIF on typical 300 dpi documents. - Even much better competitive compression results on computer generated images which are free of scanning distortions. - JBIG supports hierarchical "progressive" encoding, that means it is possible to encode a low resolution image first, followed by resolution enhancement data. This allows, for instance, a document browser to display already a good 75 dpi low resolution version of an image, while the data necessary to reconstruct the full 300 dpi version for laser printer reproduction is still arriving (say over a slow network link or mass storage medium). - The various resolution layers of a JBIG image in progressive encoding mode together require not much more space than a normal non-progressive mode encoded image (which JBIG also supports). - The progressive encoding mode utilizes a quite sophisticated resolution reduction algorithm which offers high quality low resolution versions that preserve the shape of characters as well as the integrity of thin lines and dithered images. - JBIG supports multiple bit planes and can this way also be used for grayscale and color images, although the main field of application is compression of bi-level images, i.e. images with only two different pixel values. For grayscale images with up to 6 bit per pixel, JBIG performs superior to JPEG's lossless mode. JBIG-KIT can be used as free software under the GNU General Public License. Other license arrangements more suitable for commercial applications are available as well, please contact the author for details. JBIG-KIT provides two portable libraries implemented in ANSI/ISO C for encoding and decoding JBIG data streams, along with documentation. The first library, jbig.c, implements nearly all of the options that the JBIG standard provides, but keeps the entire uncompressed image in memory. The second library, jbig85.c, implements only the ITU-R T.85 subset of the standard that black/white fax machines use (single bit per pixel, no "progressive" encoding), and keeps only three lines of the uncompressed image in memory, making it particularly attractive for low-memory embedded applications. The libraries are not intended for 8-bit or 16-bit machine architectures (e.g., old MS-DOS C compilers). For maximum performance, a 32-bit processor is required (64-bit systems work too, of course). On architectures with 16-bit pointer arithmetic, the full-featured jbig.c library can process only very small images. Special features of the full-featured jbig.c variant: - Fully reentrant multithread-capable design (no global or static variables, isolated malloc()/free() calls, etc.) - Capable of handling incomplete and growing JBIG data streams in order to allow earliest display of low resolution versions - Capable of handling several incoming data streams simultaneously in one single process and thread - Especially designed with applications in mind that want to display incoming data as early as possible (e.g., similar to the way in which Netscape Navigator handles incoming GIF images) - Implements all JBIG features and options including progressive and sequential encoding, multiple bit planes, user specified resolution reduction and deterministic prediction tables, adaptive template changes for optimal performance on half-tone images, deterministic prediction, typical prediction in lowest and differential layers, various stripe orderings, etc; only the SEQ and HITOLO options are currently not supported by the decoder (they are normally never required, but could be added later in case of user requirements) - Suitable for fax applications, satisfies ITU-T T.85 profile - Efficient code, optimized utilization of 32-bit processor registers - Very easy to use documented C library interface - Included Gray code conversion routines for efficient encoding of grayscale images - Ready-to-use pbmtojbg and jbgtopbm converters. Special features of the light-weight jbig85.c variant: - Suitable for low-memory embedded applications - Implements only the JBIG1 subset defined in the ITU-T T.85 profile (single bit plane, no differential layers) - Requires only three pixel rows of the uncompressed image to be kept in memory - Handles all NEWLEN modes of operation required by ITU-T T.85 with just a single pass over the data, automatically performing the necessary lookahead after the last stripe - Codec buffers only a few bytes of arithmetic-codec data and outputs resulting bytes or lines as soon as they are available. I will try to provide free support and maintenance for this software for the foreseeable future, depending on my available time. Happy compressing ... Markus Kuhn -- Markus Kuhn, Computer Laboratory, University of Cambridge http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain PK`1]]]TODOnu[Features that may appear in some future release regarding jbig.c: - function to prepare incompletely decoded images for display by Xlib - use a more efficient resolution-reduction method suggested by Dr. Klaus Bartz - investigate whether there is a standard way of embedding JBIG into TIFF and implement it (see also RFC 2301) - test for and eliminate warning messages from compilers other than GCC - multichannel (e.g., RGB) support, PPM support - add dynamic library target to Makefile (patch by David Woodhouse), for the benefit of Linux packagers The NEWLEN handling in jbig.c remains less than ideal. There is no easy fix as NEWLEN is inherently incompatible with many of the other options that jbig.c supports. The whole point of the VLENGTH bit may have been to allow recipients to choose between a jbig.c (VLENGTH=0) and jbig85.c (VLENGTH=1) style of decoder implementation. The cleanest option would really be to remove NEWLEN support entirely from jbig.c and to urge users who need it to use jbig85.c instead. Short of that, the new NEWLEN look-ahead architecture from jbig85.c could be backported to jbig.c, but this would only only slightly increase the number of cases where the jbig.c decoder could deal with a NEWLEN marker without a prior invocation of the jbg_newlen() pre-processing pass. The following past feature requests for jbig.c probably have become less important since the release of jbig85.c: - compile-time option to remove progressive encoding and resolution-reduction support (in the interest of reducing code size) - investigate how to best deal with broken BIEs that contain multiple NEWLEN marker segments, which are not permitted by ITU-T T.85, but which have been observed coming from some fax machines; possible options for jbg_newlen(): use first, last, or minimum value - version of jbg_newlen() for dealing with BIEs that are split into several blocks - call-back function for progress meter Features that may appear in some future release regarding jbig85.c: - man pages for pbmtojbg85 and jbgtopbm85 PK`1]a3##CHANGESnu[ JBIG-KIT revision history ------------------------- Changes in version 2.1 (2014-04-08) This is a security-critical bug-fix release that remains API and ABI backwards compatible to version 2.0. Users who process BIE data from untrusted sources should upgrade. - fixed a buffer-overflow vulnerability in the jbig.c decoder, reported by Florian Weimer (Red Hat): CVE-2013-6369 - fixed ability of corrupted input data to force jbig85.c decoder into an end-less loop - fixed a bug in the processing of private deterministic-prediction tables (DPPRIV=1) in jbig.c decoder - fixed integer-type mismatches in printf arguments on 64-bit systems - fuzz-testing script added Changes in version 2.0 (2008-08-30) Main new features of release 2.0: - This release adds a separate lightweight "T.85" version of the encoder and decoder library (jbig85.c, jbig85.h). This new T.85 library is optimized for embedded low-memory applications, such as printers and fax machines. It implements only the subset of the JBIG standard that is required by the ITU-T T.85 fax profile, namely only a single bit plane (P = 1) and no differential layers (DL = D = HITOLO = SEQ = ILEAVE = SMID = TPDON = DPON = DPON = DPLAST = 0) and some other restrictions (MY = 0, MX < 128). The T.85 library requires only three pixel rows of the uncompressed image to reside in memory at any time. This 3-line buffer has to be allocated by the calling application, therefore the T.85 library will not call any heap management functions such as malloc() or free() itself. - There are also two new example applications pbmtojbg85 and jbgtopbm85 included that provide command-line access to the new T.85 library. (Note to distribution maintainers: there is probably little point in adding pbmtojbg85 and jbgtopbm85 to precompiled JBIG-KIT packages for workstation operating systems, as these two programs do not really provide the end user much additional functionality beyond what pbmtojbg and jbgtopbm already do, which use the full library instead.) Changes to the original full jbig.c library from version 1.6: - the arithmetic codec routines are now located in a separate source file (they are now used by both the full library jbig.c and the new T.85 library jbig85.c, and might also be of use to other applications) - arithmetic decoder behaviour slightly changed to enable the lookahead needed to handle T.85-style NEWLEN after the final stripe - added encoder support for adding comment marker segment - added encoder option for using SDRST marker instead of SDNORM (only useful to make encoder able to generate a wider range of test data) - added pbmtojbg options -C and -r, which provide command-line access to the previous two extensions - slightly improved diagnostic output of jbgtopbm option -d - non-English translations of error messages are now provided in a separate PO file (e.g., for use with GNU gettext), jbg_strerror() no longer has a language attribute and the JBG_EN, JBG_DE_8859_1, JBG_DE_UTF_8 constants no longer exist - jbg_dec_in() return values changed; the least significant bits of the error codes now provide more information about what caused the error, beyond what the more general error text messages returned by jbg_strerror() reveal - pbmtojbg has a new option -f as a shortcut for all the options needed to make the output comply to the basic ITU-T T.85 fax profile - jbg_dec_getwidth(), jbg_dec_getheight(), jbg_dec_getsize(), and jbg_dec_getsize_merged() return now an unsigned long value (was: long), and return 0 (was: -1) if no image is available yet - jbgtopbm now outputs image dimensions in header padded to 10 digits fixed width, for consistency with jbgtopbm85 to allow for later in-place update of height due to NEWLEN - macro JBG_LICENCE can be changed from the default value "GPL" to a licence agreement reference code to if the library is used under a commercial licence, to clarify under which exact licence the library is used in a particular application Changes in version 1.6 (2004-06-11) - various small changes to reduce the risk of 32-bit unsigned integer overflows when dealing with extremely large images - robuster treatment of L0 = 0xffffffff - minor API modification in jbg_enc_options(): parameter l0 changed from type long to unsigned long; previous value now remains unchanged when l0 == 0 (was: l0 < 0) - lots of type casts added such that the C source code is now also compilable as C++ Changes in version 1.5 (2003-06-11) - fixed two minor memory leaks (special thanks to Davide Pizzolato for locating one of these) - jbgtopbm does not attempt any more to parse multiple concatenated BIEs (options -m must be used now to enable this feature explicitly), in order to handle BIEs with data after the last expected SDE gracefully - various extensions to improve support of JBIG fax applications (ITU-T T.85 profile): o support for maximum adaptive template pixel offset increased to MX=127 in both encoder and decoder o encoder now has a hook for producing BIEs with a NEWLEN marker segment and VLENGTH=1, in order to assist in testing decoders for T.85 conformance (see also new pbmtojbg option -Y) o a new function jbg_newlen() can be used to scan an entire in-memory BIE for NEWLEN marker segments and update the YD value in the BIE header, which can be applied to BIE data before passing it to the decoder for T.85 compliance (Background: the incremental design of the JBIG-KIT decoder makes it infeasible to look ahead for NEWLEN marker segments that occur after the SDE with the last image line, therefore this second pass is necessary to handle the old-style fax applications permitted by T.85 in which the low-RAM encoder doesn't know the height of the image at the start of transmission) Changes in version 1.4 (2002-04-09) - typo fixed in stripe number calculation, which caused encoder and decoder to fail on certain image sizes (special thanks to Koen Denecker for locating this one) Changes in version 1.3 (2002-03-23): - bugs fixed in jbg_split_planes(), jbg_dec_merge_planes() that caused a failure for more than eight planes per pixel - example converters now can handle PGM files with up to 32 bits per pixel Changes in version 1.2 (2000-04-08): - bug in the decoder fixed, which caused the rest of the input file to be skipped whenever a comment marker was encountered (special thanks to Ben Rudiak-Gould for reporting this one) Changes in version 1.1 (1999-11-16): - serious bug in the encoder fixed, which for a very small percentage of images has caused an unterminated linked list to be created internally that could have been responsible for segmentation violations or non-terminating encoders (special thanks to Hisashi Saiga for tracking that one down) - minor bug in the "jbgtopbm -d" diagnostic output fixed Changes in version 1.0 (1998-04-11): - two bugs fixed that caused the encoder and decoder to fail under certain modes of operation with several bit planes - added new functions jbg_split_planes(), jbg_dec_merge_planes(), and jbg_dec_getsize_merged() for easy handling of grayscale images - added support for compressing grayscale PGM files to pbmtojbg and jbgtopbm - more changes to avoid paranoid compiler warnings Changes in version 0.9 (1996-01-09): - encoder won't break any more on input bitmap data with incorrect zero padding - pbmtojbg displays a warning if input file has incorrect zero padding - various minor improvements suggested by Stefan Willer - many minor changes in order to avoid warnings from paranoid compilers Changes in version 0.8 (1995-09-20): - namespace cleared up, all names externally visible from the library start now with jbg_ or JBG_ - minor non-critical bug fixed which caused library to fail compatibility test and showed up especially on DEC Alpha systems - jbg_dec_gethight() is now called jbg_dec_getheight() - filenames conform now to MS-DOS limits - Bug in pbmtojbg fixed (handling of ASCII PBM files) Changes in version 0.7 (1995-06-10): - more problems on 16-bit int systems and on Macintosh systems fixed (special thanks to Jean-Pierre Gachen ) - global Makefile Changes in version 0.6 (1995-06-08): - memory leak fixed - should now also work on systems where int is only 16-bit large - changes of the JBIG "Technical Corrigendum 1" included (special thanks to Dr. Sebestyen from Siemens AG for sending me a copy of the draft) First release: version 0.5 (1995-05-28) PKI2]iJs>F>FCOPYINGnu[ GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 19yy 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., 675 Mass Ave, Cambridge, MA 02139, USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision 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, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This 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 Library General Public License instead of this License. PK`1]?ٰ77ANNOUNCEnu[PK`1]]]oTODOnu[PK`1]a3##%CHANGESnu[PKI2]iJs>F>FHCOPYINGnu[PKg