whoami7 - Manager
:
/
home
/
fresvfqn
/
waterdamagerestorationandrepairsmithtown.com
/
Compressed
/
Upload File:
files >> //home/fresvfqn/waterdamagerestorationandrepairsmithtown.com/Compressed/t1lib.zip
PK �P[MZ�} usr/share/t1lib/t1lib.confignu �[��� t1lib.config - global configuration file for t1lib. It was created automatically on Wed Apr 30 10:03:32 UTC 2025 by the t1libconfig script. Run /usr/sbin/t1libconfig --force to rebuild it. ENCODING=. AFM= TYPE1= FONTDATABASE=/opt/alt/t1lib/usr/share/t1lib/FontDatabase PK �P[O�Ax� � usr/share/doc/alt-t1lib/READMEnu �[��� -------------------------------------------------------------------------- --------------------------- t1lib-README --------------------------------- -------------------------------------------------------------------------- /*-------------------------------------------------------------------------- ----- File: REAMDE.t1lib-5.1.2 ----- Author: Rainer Menzner (Rainer.Menzner@web.de) ----- Date: 2007-12-23 ----- Description: This is file README.t1lib of the t1lib-package. It contains an overview and brief installation instructions for the t1-library. ----- Copyright: t1lib is copyrighted (c) Rainer Menzner, 1996-2007. As of version 0.5, t1lib is distributed under the GNU General Public Library License. The conditions can be found in the files LICENSE and LGPL, which should reside in the toplevel directory of the distribution. Please note that there are parts of t1lib that are subject to other licenses: The parseAFM-package is copyrighted by Adobe Systems Inc. The type1 rasterizer is copyrighted by IBM and the X11-consortium. ----- Warranties: Of course, there's NO WARRANTY OF ANY KIND :-) ----- Credits: I want to thank IBM and the X11-consortium for making their rasterizer freely available. Also thanks to Piet Tutelaers for his ps2pk, from which I took the rasterizer sources in a format independent from X11. Thanks to all people who make free software living! --------------------------------------------------------------------------*/ About t1lib: ------------ t1lib is a library distributed under the GNU General Public Library License for generating character- and string-glyphs from Adobe Type 1 fonts under UNIX. t1lib uses most of the code of the X11 rasterizer donated by IBM to the X11-project. But some disadvantages of the rasterizer being included in X11 have been eliminated. Here are some of the features: - t1lib is completely independent of X11 (although the program provided for testing the library needs X11) - fonts are made known to library by means of a font database file at runtime - searchpaths for all types of input files are configured by means of a configuration file at runtime - characters are rastered as they are needed - characters and complete strings may be rastered by a simple function call - when rastering strings, pairwise kerning information from .afm-files may optionally be taken into account - an interface to ligature-information of afm-files is provided - a program to generate afm-files from Type 1 font files is included - rotation and arbitrary transformations are supported - there's support for extending and slanting fonts - underlining, overlining and overstriking is supported - new encoding vectors may be loaded at runtime and fonts may be reencoded using these encoding vectors - antialiasing is implemented - Right-To-Left typesetting is supported - Font subsetting is easily possible - support of composite character information - stroking of character outlines with variable strokewidths - An interactive test program called "xglyph" is included in the distribution. This program allows to test all of the features of the library. It requires X11. Changes and New Features: ------------------------- - See the file Changes in the T1Lib top-directory for information on new features. Installation: ------------- ----------------------------------------------------------------------------- Note: VMS-users should examine configure.com in the toplevel directory, which is a configure-script for VMS, kindly contributed by John Hasstedt and now maintained by Martin Zinser. This file contains notes on how to compile t1lib on VMS. ----------------------------------------------------------------------------- After unpacking the archive (what you obviously did already), change to subdirectory t1lib-..../ and type: ./configure This will create the Makefiles. Then type make In order to use the testprogram xglyph, X11 needs to be installed on your system. If you have difficulties during configuring and building t1lib, cd to directory t1lib-.../doc and execute $ latex t1lib_doc.tex $ makeindex t1lib_doc $ latex t1lib_doc.tex $ latex t1lib_doc.tex This will generate the docs which contain a more detailed description of the build-process. LaTeX2e is required. Alternatively, you can scan the preformatted pdf-documentation. Before installing the libraries, you should test whether all things work correct: 1) Change to subdirectory xglyph 2) Start the program xglyph 3) Ensure that the output-window is not hidden behind another window. 4) Before doing anything other, click on button "String". The string "Test" should now be rastered and displayed in the output-window, using font BitstreamCharterBTRoman at 100bp without kerning. If that works, most probably all works for you. 5) Have a look at t1lib_doc.dvi in the doc-subdirectory of the package and read the chapter on xglyph. However, most of this program is self-explaining, so that you might want to omit this step. 6) Play with the program and enjoy. 7) If you do not have X11, you can still check whether t1lib works for you. Copy one of the pfb-files from t1lib-.../Fonts/type1, say, bchr.pfb, to the type1afm-subdirectory, and run type1afm bchr.pfb If the afm-file bchr.afm is generated, t1lib will most probably work on your system. Documentation: -------------- As mentioned above, documentation is provided in LaTeX2e-format subdirectory T1Lib/doc. It should have been built during the build. The section on runtime setup is really important, because programs may fail due to an invalid or incomplete runtime setup, although the programs itself may be correct! A preformatted Version is also available in pdf. How to get it: -------------- t1lib is available at ftp://sunsite.unc.edu/pub/Linux/libs/graphics/t1lib-x.y[.z].tar.gz where x.y[.z] is the version identification. Closing: -------- You are allowed to send the author lots of money and dozents of gifts, but you needn't :-) If you have any comments to this library, feedback is wanted. Send eMail to: Rainer.Menzner@web.de Future: ------- Within the past years, my time has constantly and increasingly become spare so that I hardly found time to further develop t1lib. And developing free software is undoubtedly related to a certain amount of fun, which in turn only can come up if you are relaxed with respect to time ... Since t1lib now has reached a reasonably stable state, I intend to more or less freeze the development of new features at this point. Of course, bug fixes etc. should be possible further. If there is somebody out there willing to further develop t1lib, he or she is welcome to contact me ... Have fun, -Rainer PK �P[iJs�>F >F usr/share/doc/alt-t1lib/LICENSEnu �[��� 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. <one line to give the program's name and a brief idea of what it does.> Copyright (C) 19yy <name of author> 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. <signature of Ty Coon>, 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 �P[�C�6b 6b usr/share/doc/alt-t1lib/Changesnu �[��� Nov 1996: t1lib-0.1-alpha ------------------------- - first public release of t1lib with all basic functionality May 1997: t1lib-0.2-beta ------------------------- - Now uses autoconf to configure the software for the system. - All functions put into one library. - ATTENTION: Argument order for the glyph-setting functions changed to be consistent with the info functions. Programs that already use t1lib have to be rewritten (sorry....) - Function for computing the width of a string added (T1_GetStringWidth()). - Function for computing the BoundingBox of a string added (T1_GetStringBBox()). - Function T1_GetMetricsInfo() added. It returns a struct containing width, bounding box, number of characters and horizontal position of the characters in character space coordinates (afm-units). - Function T1_GetBBox() renamed to T1_GetCharBBox() for consistency reasons. - All exit() calls removed from library and replaced by appropriate error return codes. - t1lib now optionally supports a logfile for logging of error- and warning-messages at runtime. The "verbosity" of this logfile may be chosen by the user. - Documentation more complete. July 1997: t1lib-0.3-beta ------------------------- - Code for placing character bitmaps in T1_SetString() slightly advanced; the restrictions concerning slanted fonts are eliminated. - T1_GetStringBBox()/T1_GetCharBBox() extended. It is now possible to get the bounding box if the font is slanted. This is implemented by examining the characters outline at 1000bp. - Some Bugs in the code managing linked lists of font sizes have been corrected. - Bug in T1_CopyFont() has been corrected. This should work now. - The behavior during configuration file searching has been changed to be compatible to well known UNIX-conventions. - As the main new feature in this release t1lib now has direct support for X11 (optionally). There is a set of functions that act similar to XDrawText(), i.e. they draw directly into a drawable (pixmap or window). - Caching of bitmaps of the X11 rastering functions is also done in the X-Server for maximum performance (although it is not as fast as I dreamed of, admittedly). - X11 rastering functions use the current foreground/background colors - The X11 rastering functions implement automatical antialiasing between foreground and background color - The X11 rastering functions provide an opaque and a transparent mode - The X11 rastering functions can draw into drawable of any depth (provided the depth is large enough) - A new target has been added to the makefiles allowing to remove a t1lib-installation automatically from a system. December 1997: t1lib-0.4-beta ----------------------------- - Many memory allocation bugs fixed. t1lib is now "libefence-proved". - Kerning and Metrics-Lookup rewritten. The corresponding functions are now based on character indices rather than on character names which makes them up to 8 x faster than before, depeding on data and context. - Raph Levien (raph@acm.org) contributed a fast algorithm for subsampling which improves Antialiasing time significantly. - Fred L. Drake, Jr. (fdrake@acm.org) contributed a Python-interface to t1lib. This allows Python programmers to make use of Adobe Type 1 fonts. This package, called t1python, is distributed with t1lib in an independent subdirectory of the distribution. See README.t1python for more information on t1python. - Bitmaps and antialiased bitmaps may now be padded 8, 16 or 32 bits. This allows (with some restrictions) somewhat faster concatenation of characterbitmaps to stringbitmaps. The padding-value may be set and queried at runtime. - The optional X11-interface, introduced in t1lib-0.3-beta, has been reduced to a simple wrapper. X11-pixmap caching has been completely dropped since it has proven to be too inefficient. However, at the level of the function calls, nothing has changed. - Configuration of t1lib (with or without X11-interface) may be queried by applicationprogrammers at compiletime or by applications at runtime. - Two functions for informations on fonts have been added: 1) T1_GetFontBBox(): Return a fonts' bounding box. 2) T1_GetAllCharNames(): Return a list of all character defined in a Type 1 font. This might be of interest if somebody wants to set up new encodings. - Function T1_CloseLib() added. This function allows to completely free the data-structures of t1lib. T1_CloseLib() should be called in future when an application using t1lib exits. - Many other things not worth to be metioned ... March 1998: t1lib-0.5-beta -------------------------- - Changed the license to the GNU General Public Library License (LGPL) - Definition of INFINITY removed from lib/type1/[regions.c|regions.h|t1imager.h]. Collided with a definition in math.h on OS/2. - Implemented proper handling of environment variables CFLAGS, LDFLAGS and CC during build process. - Added target 'without_doc' for people who have a very rudimentary or no LaTeX-System at all - Fixed some bugs that appeared when font files from database were not found - Clipmask Bug in the X11-rastering functions fixed - Bugs in VM-reallocation (T1_LoadFont()) repeatedly fixed. It is now ANSI-C compliant. - Alignment of VM changed. This was needed on some systems. - Set of functions for accessing information from FontInfo dictionary is now complete. This introduces the new functions T1_GetFullName(), T1_GetFamilyName(), T1_GetWeight(), T1_GetItalicAngle(), T1_GetIsFixedPitch(), T1_GetVersion(), T1_GetNotice(). - ATTENTION: In the above context, T1_GetPostScriptName() has been renamed to T1_GetFontName() for consistency reasons, sorry. - ATTENTION: All types "unsigned char (*)" have been changed to char (*) in the API functions. This was necessary while adapting t1lib to ANSI-standard to make it portable. Sorry for this confusion. - New function T1_AddFont(): Fonts can now be added to the font database at runtime. This means especially, one can ignore a FontDataBase file thus can start t1lib-programs on single fontfiles without doing a complete setup before. - There is now also the possibility to ignore the currently active configuration file, thereby setting all search paths to the current working directory and having an empty font data base. This is meant for small applications that work on single files. - t1lib is now able to work with fonts without corresponding afm-files. AFM-information can be produced from pfa- and pfb-files. This, of course, refers only to character-metrics information. - A function T1_WriteAFMFallbackFile() is provided which allows to dump metrics information to a valid AFM-file. - New subdirectory type1afm created which contains type1afm, a program to extract afm files from Type 1 font files. - Renamed definitions MAX, MIN, ABS, TRUE and FALSE because they collided with system header files on some systems. - Corrected antialiasing functions. The metrics should now be as correct as possible and black pixel at the right edge of the bitmaps should not appear any more. - Handling of unencoded characters in strings (such as adieresis in AdobeStandardEncoding) is now consistent in rotated and non-rotated glyphs. - A few functions have been added to get information on the file search environment and to manipulate the search paths from within applications. - Mixed endian setups (i.e., client and X-server on different machines with different endianess) should now be handled correctly. - In summary t1lib should now be much more portable than before. - Update to t1python-0.3 March 1998: t1lib-0.6-beta -------------------------- - Cleaned up the sources in type1-directory - Functions Xalloc() and Xfree removed. x11dummy.c from list of source files removed. - A few bugs fixed - Character positioning rewritten. It does now handle strings correctly in which the leftmost pixels does not belong to the first character and the rightmost pixels do not belong to the last character. - t1lib now substitutes .notdef for defined character names that have no corresponding charstring. This is a workaround for some fonts in the ghostscript distribution (e.g., s050000l.pfb) - Separated the X11-wrapper from the rest of t1-stuff. t1lib now consists of two libraries and two include files. - Cleaned up configuration and compilation process. May 1998: t1lib-0.7-beta ------------------------ - Athena libraries are explicitly located for non-standard system - glyph-structure changed. glyph.metrics.characterWidth is replaced glyph.metrics.advanceX and an entry glyph.metrics.advanceY is added. - Interpretation of the sign of glyph.metrics.descent has changed. - String-rastering functions now support Underlining, Overlining and Overstriking. - Functions for overriding default line-parameters implemented. - Whitespace at beginning and ending of glyphs is now correctly recorded into leftSideBearing and RightSideBearing. - Function T1_ConcatGlyphs() added to API. It concatenates two glyphs of identical depth with an optional displacement inserted. - xglyph output window has changed for X-rastering functions. It is now of constant size with the logical origin in the center. Too large glyphs are simply clipped. - t1lib can be compiled and run on VMS thanks to John Hasstedt (John.Hasstedt@sunysb.edu). A configure.com script for building on VMS is included in the toplevel directory. - T1_GetMetricsInfo() and T1_GetStringBBox() fixed. Now results are correct also if the leftmost pixel in a glyph doesn't belong to the first char and if the rightmost pixel does not belong to the last character. - Leading and trailing white space in glyphs should now be recorded consistently and correctly for all rastering functions. - xglyph can now display a character map of a font. - Global variable T1_errno introduced. It basically works the same way as the errno in libc. This allows applications a unified error-handling. - Update to t1python-0.7. November 1998: t1lib-0.8-beta ----------------------------- - T1_GetAllCharNames() returned invalid list if the Charstrings dictionary was larger than the actual number of charstrings defined (which is perfectly valid, even if it does not make much sense) --> fixed. - 4 x Antialiasing implemented. This can improve the quality at small sizes once more, at the cost of some computational and memory requirement. It is possible to work with 2 x and 4 x concurrently. - Function T1_GetLibIdent() added to API. - Function T1_SetRasterFlags() added to API. It allows to selectively enable or disable certain rasterizer features like, e.g., hinting. - xglyph extended to support 4 x antialiasing. - xglyph now recognizes a few commandline options, primarily intended for debugging purposes. - xglyph is now somewhat more intelligent (and faster) if slanting, extending or reencoding is applied to a font. - New function T1_SetDefaultEncoding(). It allows to set a default encoding vector which then is applied to all subsequently loaded fonts that have StandardEncoding. - Bug in Type 1 rasterizer corrected which prevented fonts with non-standard lenIV values from being correctly decrypted (Charstring decryption). - Internal ISOLatin1Encoding removed from rasterizer since there's no reason for mainting this encoding scheme internally - tlib now has notion of "Encoding Schemes". The format of encoding files is extended correspondingly and is backward compatible. - Memory leaks eliminated, thanks to David Huggins-Daines. - Some slight performance improvements. - Kerning performance improved. Moreover, kerning pairs need no longer be alphabetically sorted. - AFM-parser modified to work with DOS-style AFM-files. - Some bugs in scan-code of Type 1 rasterizer corrected. Scanner is now aware of pfb-blocks and can scan files with multiple binary data segments. - t1lib now uses GNU-libtool, thanks to Hirotsugo Kakugawa (h.kakugawa@computer.org) - An encoding file for IsoLatin2 charset is included thanks to Jiri Pavlovsky (jirap@bajt.cz). - The angle-argument of the rastering functions has been replaced by a more general transformation specification. This is an incompatible change to previous versions, but I think it should be worth it. - t1lib can now handle fontfile names with arbitrary extensions and even without extension. - t1lib compiles and runs under Win32 using the cygwin32 toolkit. - Maximum number of stem-hints enlarged (-> 256) because 128 were not enough for complicated fonts. May 1999: t1lib-0.9 ------------------- - Sub-Pixel positioning for Antialiasing functions enthanced (It was in fact not correct before. - Multiple Master fonts are rejected instead of SIGSEGV (nearly as professional as supporting them ;) - An additional set of functions allows access, filling and manipulation of outlines. - Functionality for non-antialiased "bytemaps". - "Smart Antialiasing", allows to automatically let t1lib decide what AA-level to use. The switchlimits are adjustable. - An AFM-filename may explicitly be specified. This suppresses t1lib´s search for these files. This allows interfacing with other path search systems like kpathsea. This was suggested by Nicolai Langfeldt (janl@math.uio.no). - Some problems with aspect ratios different from 1 and transformed glyphs fixed. - Support for Right-To-Left typesetting. This might be experimental because I don't know the rules for this exactly. - In the context of Right-To-Left typesetting T1_ConcatGlyphs() expects one additional argument "mode". ATTENTION: This is an incompatible change with respect to V. 0.8. - abort()-calls in type1-sources are caught by longjmp(). t1lib does not any longer exit a program. Rather, errors may be handled by the user. - If a rastering operation did not produce any black pixels, the rastering fuctions do not return a NULL-glyph any longer. Rather, a glyph with the correct metrics and NULL-bitmap pointer is returned. This seems to come closer to accepted standards. - The t1python-package is currently not distributed with t1lib because the interface is not up to date. - A lot of bugs fixed (and a lot of others introduced, of course :) June 1999: t1lib-0.9.1 --------------------- - Several Bug-fixes, some functions that have been reported to be missing by users, but no general new features. - New functions T1_GetExtend(), T1_GetSlant() and T1_GetTransform() which give access to currently active values of fontlevel transformations - New function T1_GetNoKernPairs() which gives access to the number of defined kerningpairs. - New functions to query the grayvalue settings (T1_AAGetGrayValues(), T1_AAHGetGrayValues() and T1_AANGetGrayValues()) - Arbitrary linear transformations on fontlevel including caching using T1_TransformFont() (on suggestion and patches by Derek B. Noonburg, (derekn@foolabs.com) - Introduction of the initialization flag T1_NO_AFM which suppresses use of AFM data. This limits the functionality of t1lib considerably but applications that do not need those advanced functions can gain some performance boost while loading fonts because AFM files are not parsed and the mapping tables are not setup (also by Derek B. Noonburg) - xglyph clips output window for the function fonttable() to the physical screen size. This is to prevent from freezing or exceeding resources if the fonttable button had accidentally been pressed while a large size was active. - The utility function T1_DumpPixmap() removed from API. New function T1_XImageFromGlyph() added to X11 interface. This function allows, together with the Xpm-library function XpmWriteFileFromImage(), to write xpm-files from glyphs of arbitrary depths, colors, etc ... - Functions T1_CopyOutline() and T1_FreeOutline() added to the outline interface. - Fixed alignment problem on 64bit architecture. September 1999: t1lib-0.9.2: ---------------------------- - Support for EMX-environments under MSDOS. This concerns the file locating routines. - t1lib now allows for charstring code 15 and escape code 15 by ignoring these. They may appear in some old Adobe fonts. - Makefiles are more independent of GNU make. - Finally, undefined/missing characters are handled consistent in all rastering functions by substituting .notdef. - Several bug-fixes November 1999: t1lib-1.0: ------------------------- - Bug-fixes. - There happen to exist different assumptions about what exactly ISOLatin1Encoding is. Especially the name for char 45 (dec) is not uniquely specified in ISO 8859-1. Thus t1lib provides two encoding files ISOLatin1Encoding one which (PSLatin1.enc) is compatible with PostScript Level 2 and above. March 2000: t1lib-1.0.1: ------------------------- - A few bug Fixes. - lenIV=-1 is now handled. According to an undocumented Adobe convention lenIV=-1 indicates suppressing of charstring encryption. - Patches to compile t1lib und MS Visual C++ 6.0. In case something goes wrong, please contact Nakano Hideo (hideo@mb.infoeddy.ne.jp). February 2001: t1lib-1.1.0: --------------------------- - Bug Fixes. - Functions T1_GetFontFilePath() and T1_GetAfmFilePath() which return the complete path of the files used by t1lib. - Fixed parser code which previously failed on ASCII-encrypted files in which the hex-lines were separated by <LF><CR> instead of by <LF> (Yes, there such DOSian files out there ...). - Multiple inclusion protection for t1lib.h - T1_QueryLigs() fixed. It did not work correct if successors and/or ligatures were not in the current encoding. - New patches for VMS by Martin P. J. Zinser (zinser@decus.de). - Patch by Sergey Babkin (babkin@bellatlantic.net) to correct the rasterizer to respect StdStemWidths. - General support for font subsetting. - Dokumentation also provided as pdf for those people who do not have LaTeX installed. This is due to suggestions and patches by Nguyen-Dai Quy (NDQ@iris.ltas.ulg.ac.be). April 2001: t1lib-1.1.1: ------------------------ - Update to libtool-1.3.5. - T1_GetFontBBox() also accepts specification consisting of floating point numbers (as suggested by Derek B. Noonburg (derekn@foolabs.com)). - Within the near future the t1lib-webpage will be no longer available because I will change my employer. - Similarly, the sources will be distributed from sunsite only from then on. - The Author's eMail-address will also become invalid in the near future. The new and hopefully permanent eMail.address will be "Rainer.Menzner@web.de". July 2001: t1lib-1.2: ---------------------- - Fixed bug in subsetting code. - Fixed bug in AFM-parser code. - Fixed kerning mapping code. Kerning did not work correctly for characters that appeared multiple times in an encoding vector. - In the same context a new function, T1_GetEncodingIndices() has been added to the API. It returns an array of indices (by contrast, T1_GetEncodingIndex() returns only the lowest index found). - Support for composite characters. - Additional support for dvips encoding files (thanks to suggestion and contribution by Nicolai Langfeldt (janl@linpro.no). - Documentation is installed in PostScript and PDF format, but no longer in DVI format. October 2001: t1lib-1.3: ------------------------ - *Really* an update to libtool-1.3.5 - Global Font Metrics Information is loaded from AFM files in order to be able to read the typographic ascender. Line ruling did not behave as documented. However, problems could still exist because the typographic ascender specification is optional in AFMs. - Reorganized search path handling and, in particular, the respective documentation is more detailed. - The configuration file now allows multiple lines of one type of search path specification and it is also possible to quote path specification in order to specify paths that contains special characters like spaces, colons, etc. - Multiple font databases are supported. - T1_PrintLog() extended to accept a variable argument list. - The environment variable T1LIB_LOGMODE is evaluated to give the user the chance to specify a loglevel and hence to detect t1lib-problems even if the application programmer did not enable the log file features. - Further bug fixes November 2001: t1lib-1.3.1: --------------------------- - Color problem in t1x11-module fixed. - Fixes in AFM parser. Among others, Version had been read as name, instead of as string. This led to a failure to scan global font info for some standard AFMs. - Fixes in of OpenVMS special code - Further Fixes January 2003: t1lib-5.0.0: -------------------------- - Forced PostScript target in the doc directory to file. - Subsetting code extended in order to ensure that components of composite characters are also part of the subset. - Hinting meachanism reworked in order to get rid of some rasterizing artifacts. - Experimental support for stroked fonts (PaintType=1) - Experimental support for stroking standard ATM fonts with PaintType=0. - For historical reasons, there happened to exist a few documented API functions that did not adhere to the T1_... naming convention. After considering the pro's and con's, I have decided to cleanup the interface, thus making this version incompatible to the previous version. Especially in the type1 subdirectory there are still a lot of global symbols, but at least these are not part of the documented API. The following functions are affected: CheckForInit() --> T1_CheckForInit() CheckForFontID() --> T1_CheckForFontID() T1_Get_no_fonts() --> T1_GetNoFonts() Furthermore, I have removed and made static a few functions which accidentally had found their way into t1lib.h, but which had not been part of the documented API. I'm sorry if this causes inconveniences ... - The new version, 5.0.0, follows as consequence from the issues discussed above. It is defined by the libtool quantities CURRENT, REVISION and AGE. - Functions for drawing rectangles. - Bug Fixes - Please also have a look at the topic "Future" in README.t1lib-5.0.0. February 2004: t1lib-5.0.1: --------------------------- - Support for Flex was not adapted to the changes from 5.0.0. This led to rasterization errors in fonts that use the Flex functionality --> fixed. - Bug Fixes April 2004: t1lib-5.0.2: ------------------------ - Changes not updated for this version Mai 2005: t1lib-5.1.0: ---------------------- - Check against MultipleMasterFonts somewhat more tolerant, so that Type 1 Fonts automatically created from Multiple Master Fonts (e.g. using Mmpfb) should now be acceptable. - The configure-machinery had been somewhat out of date and has been updated. The distributed configure script has been generated by AutoConf 2.59 and the redistributed libtool parts are taken from GNU libtool 1.5.10. - Top-Level TeX-file in the doc subdirectory adapted to recent TeX systems' requirements. - Added IsoLatin9.enc to distribution. - Subsetting extended so that it works for SEAC-constructed composites even if no AFM composite character information is available - Somewhat more intelligent defaults for subsetting when composite characters are included in the subset. - Reallocation had been broken by relocation of internal StandardEncoding vector. This problem turned out on systems where realloc() actually returned a different pointer. - Fix for outline code on 64bit systems. This involves a redefinition of the T1_PATHPOINT struct. This should be uncritical because for 32bit systems there is no difference, whereas on 64bit systems, this has never worked correctly before. - DESTDIR support in Makefile.in by Volker Zell - Support for XLFD font database format (in which the fonts' names appear in the first place on a line). - Further Bug Fixes December 2006: t1lib-5.1.1: --------------------------- - DESTDIR support was missing and has been addded in install-target for type1afm. - A bug fix in Anti-Aliasing subsampling code, which could make t1lib crash under certain conditions. - Small number of further fixes, in particular with respect to the build mechanism. December 2007: t1lib-5.1.2: --------------------------- - Small number of fixes reported by users. The fixes pertain to a vulnerability issue, memory access issues. - More decent handling if Encoding and / or FontBBox specification are missing (which is invalid with respect to the specification, but recoverablel). PK �P[.���b �b usr/share/doc/alt-t1lib/LGPLnu �[��� GNU LIBRARY GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 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 library GPL. It is numbered 2 because it goes with version 2 of the ordinary GPL.] 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 Library General Public License, applies to some specially designated Free Software Foundation software, and to any other libraries whose authors decide to use it. You can use it for your libraries, 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 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 a program 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. Our method of protecting your rights has two steps: (1) copyright the library, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the library. Also, for each distributor's protection, we want to make certain that everyone understands that there is no warranty for this free library. If the library is modified by someone else and passed on, we want its recipients to know that what they have is not the original version, 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 companies distributing free software will individually obtain patent licenses, thus in effect transforming the program into proprietary software. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License, which was designed for utility programs. This license, the GNU Library General Public License, applies to certain designated libraries. This license is quite different from the ordinary one; be sure to read it in full, and don't assume that anything in it is the same as in the ordinary license. The reason we have a separate public license for some libraries is that they blur the distinction we usually make between modifying or adding to a program and simply using it. Linking a program with a library, without changing the library, is in some sense simply using the library, and is analogous to running a utility program or application program. However, in a textual and legal sense, the linked executable is a combined work, a derivative of the original library, and the ordinary General Public License treats it as such. Because of this blurred distinction, using the ordinary General Public License for libraries did not effectively promote software sharing, because most developers did not use the libraries. We concluded that weaker conditions might promote sharing better. However, unrestricted linking of non-free programs would deprive the users of those programs of all benefit from the free status of the libraries themselves. This Library General Public License is intended to permit developers of non-free programs to use free libraries, while preserving your freedom as a user of such programs to change the free libraries that are incorporated in them. (We have not seen how to achieve this as regards changes in header files, but we have achieved it as regards changes in the actual functions of the Library.) The hope is that this will lead to faster development of free libraries. 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, while the latter only works together with the library. Note that it is possible for a library to be covered by the ordinary General Public License rather than by this special one. GNU LIBRARY GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any software library which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Library 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 compile 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) 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. c) 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. d) 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 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. 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 to 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 Library 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. END OF TERMS AND CONDITIONS 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. <one line to give the library's name and a brief 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 Library General Public License as published by the Free Software Foundation; either version 2 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 Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with this library; if not, write to the Free Foundation, Inc., 59 Temple 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! PK �P[�A�� � ! usr/share/man/man5/FontDatabase.5nu �[��� .TH FONTDATABASE 5 .SH NAME FontDataBase \- database of fonts accessible to t1lib. .SH DESCRIPTION This manual page has been written for the Debian GNU/Linux distribution. It has been adapted from the documentation included in the upstream .B t1lib distribution. .PP .B /etc/t1lib/FontDataBase is a text file which contains, minimally, the basenames of Type 1 font files to be made accessible to the .B t1lib font rasterizer library. The format is intentionally similar to that of the .B fonts.dir and .B fonts.scale files used by X11. .PP Line 1 of this file contains a positive integer specifying the number of fonts declared in that file. This is as in the .B fonts.dir files of the X11 system. .PP All remaining lines contain declarations of one font each. The only thing taken from such a line is the last string (delimited by white space) in it. It is assumed to be a filename of the format \fIbasename\fR.\fIsomeextension\fR. .PP The \fIbasename\fR part is assumed to be the .BR basename (1) of a fontfile. After the a string has been parsed, the .I extension is cut off and replaced in turn with .I .pfa and .I .pfb. The initialization routine tries to open a font file in its search path with one of the resulting filenames. .PP The remainder of the line, i.e., from beginning to the start of the filename string, is completely ignored and thus may contain information for other programs. .SH EXAMPLES Here is a minimal font database file for 4 fonts: .sp .nf 4 isvl.afm isvli.afm isvd.afm isvdi.afm .fi .PP This file is \fIminimal\fR, because it contains just the information needed, and nothing not needed by the library. .PP Here is a more realistic example, which allows an application to match a fully qualified X11 fontname to a FontID in .B t1lib. This is also a valid font database file: .sp .nf 4 Souvenir Souvenir-Light --- -itc-souvenir-light-r-normal--#-0-0-0-p-0-iso8859-1 isvl.afm Souvenir Souvenir-LightItalic -*- -itc-souvenir-light-i-normal--#-0-0-0-p-0-iso8859-1 isvli.afm Souvenir-Demi *-- -itc-souvenir-demi-r-normal--#-0-0-0-p-0-iso8859-1 isvd.afm Souvenir-DemiItalic **- -itc-souvenir-demi-i-normal--#-0-0-0-p-0-iso8859-1 isvdi.afm .fi .PP .SH FILES .I /etc/t1lib/FontDataBase .SH "SEE ALSO" .BR mkfontdir (1x) PK �P[|v�� � usr/share/man/man8/t1libconfig.8nu �[��� .TH T1LIBCONFIG 8 .SH NAME .B t1libconfig \- create the t1lib.config and FontDataBase files for t1lib .SH SYNOPSIS .B t1libconfig [ .BR \-v\fP, \fB\-\-version ] [ .BR \-h\fP, \fB\-\-help ] .B \-\-force ] [ .B fontdirectory... ] .SH DESCRIPTION .B t1libconfig scans a list of directories for Type 1 fonts and font metric files, and generates a configuration file and font database file for the .B t1lib rasterizer library accordingly. By default, it looks in all subdirectories of /usr/X11R6/lib/X11/fonts, and in /usr/lib/ghostscript. Extra directories to search may be specified on the command line. The .B t1libconfig script tries not to scan the same directory twice (this is, however, not foolproof, since /usr/X11R6/lib/X11/fonts and /usr/lib/X11/fonts typically point to the same directory on GNU/Linux systems). .SH OPTIONS .TP .BR \-v\fP, \fB\-\-version Print the version of .B t1libconfig and exit. .TP .BR \-h\fP, \fB\-\-help Print help about usage and exit. .TP .B \-\-force Force the generation of new configuration files even if these files already exist on the system. .SH FILES .TP 25 .B /etc/t1lib/t1lib.config Contains configuration information for t1lib, including colon-separated lists of paths to Type 1 font files and font metrics files, and the location of the default font database file .TP 25 .B /etc/t1lib/FontDataBase Contains a list of the names of Type 1 font files to be used by t1lib. .SH AUTHOR David Huggins-Daines <dhd@debian.org> .SH SEE ALSO .BR FontDataBase (5) PK �P[~�m� � usr/sbin/t1libconfignu ȯ�� #!/bin/sh -e # to test POSIX-correctness, change hash-bang to /bin/bash and uncomment # the following line: # set -o posix # Very simple configuration script for t1lib. Checks a couple of # directories that might contain fonts, and if they exist, adds # anything ending in .pfa or pfb to the font database. A few things # borrowed from paperconfig, (C) 1996, Yves Arrouye # <arrouye@debian.org> # note that this creates the "minimal" font database accepted by t1lib, # and doesn't look in every possible place for fonts. It is mostly # provided so that xglyph will work out of the box... # Written by David Huggins-Daines <dhd@debian.org> usage() { if [ "$1" = -h ] then exec 1>&2 echo -n U else echo -n u fi echo "sage: `basename $0` [ -v, --version ] [ -h, --help ] [ --force ]" echo " [ fontdirs... ]" if [ "$1" = -h ] then cat <<EOF Options: -v, --verbose print version information and exit -h, --help print this help and exit --force force configuration EOF exit 0 else exit 1 fi } version=0.2 topfontdirs="/usr/share/fonts /usr/share/texmf/fonts /usr/share/fonts/X11" for dir in $topfontdirs; do if [ -d $dir ]; then subdirs=$(find $dir -type d -printf "%p ") fontdirs="$subdirs $fontdirs" fi done conffile=/opt/alt/t1lib/usr/share/t1lib/t1lib.config confdir=/opt/alt/t1lib/usr/share/t1lib/ dbase=/opt/alt/t1lib/usr/share/t1lib/FontDatabase temp=/opt/alt/t1lib/usr/share/t1lib/FontDatabase.tmp force=0 while [ $# -ne 0 ] do case "$1" in -v|--version) echo "`basename $0` version $version" \ "by David Huggins-Daines <dhd@debian.org>" exit 0 ;; -h|--help) usage -h ;; --force) force=1 ;; *) # hairy way to remove a trailing backslash (should use perl) pat=`expr $1 : "\(.*\)\/\$" || echo $1` # hairier way to find a string anywhere in another string # should really use perl. if ! grep $pat <<EOF >/dev/null 2>&1 $fontdirs EOF then fontdirs="$fontdirs $1" fi ;; esac shift done # We presume that if the database exists, then so does the # configuration file. Hopefully this won't break anything. if [ $force -eq 1 ] || [ ! -e $dbase ]; then fontpath="" afmpath="" mkdir -p $confdir || true echo -n "Searching for Type 1 fonts and AFM files..." for i in $fontdirs do if [ -d $i ] && ls $i/*.pf[ab] > /dev/null 2>&1; then if [ -n "$fontpath" ]; then fontpath="$fontpath:$i" else fontpath="$i" fi if ls $i/*.afm > /dev/null 2>&1; then if [ -n "$afmpath" ]; then afmpath="$afmpath:$i" else afmpath="$i" fi fi # get a listing of all the fonts in each dir find $i -maxdepth 1 -name *.pf[ab] -printf '%f\n' >> $temp fi done if [ -z "$fontpath" ]; then cat <<EOF No Type 1 fonts were found in the expected locations. If you want t1lib to be aware of your fonts, you should run /usr/sbin/t1libconfig with the names of your local font directories as arguments, or you should edit the /opt/alt/t1lib/usr/share/t1lib/FontDatabase file manually. See the FontDatabase(5) manual page for more information. Press [return] to continue. EOF read foo || true rm -f $temp else echo "done." echo -n "Building font database..." fontcount=`wc -l $temp || true` echo $fontcount > $dbase cat $temp >> $dbase rm -f $temp echo "done." fi # now set the paths in the config file cat <<EOF >$conffile t1lib.config - global configuration file for t1lib. It was created automatically on `date` by the t1libconfig script. Run /usr/sbin/t1libconfig --force to rebuild it. ENCODING=. AFM=$afmpath TYPE1=$fontpath FONTDATABASE=$dbase EOF else echo "Configuration and font database files already exist." echo "Run /usr/sbin/t1libconfig --force to rebuild them." fi exit 0 PK �P[�*� pg pg usr/lib64/libt1x.so.5.1.2nu ȯ�� ELF >