summaryrefslogtreecommitdiff
path: root/bits/bbdb-filters/doc/formatted/bbdb-filters.info
diff options
context:
space:
mode:
Diffstat (limited to 'bits/bbdb-filters/doc/formatted/bbdb-filters.info')
-rw-r--r--bits/bbdb-filters/doc/formatted/bbdb-filters.info1101
1 files changed, 1101 insertions, 0 deletions
diff --git a/bits/bbdb-filters/doc/formatted/bbdb-filters.info b/bits/bbdb-filters/doc/formatted/bbdb-filters.info
new file mode 100644
index 0000000..c66edef
--- /dev/null
+++ b/bits/bbdb-filters/doc/formatted/bbdb-filters.info
@@ -0,0 +1,1101 @@
+Info file: bbdb-filters.info, -*-Text-*-
+produced by latexinfo-format-buffer
+from file: main.tex
+
+
+
+File: bbdb-filters.info Node: Top, Prev: (dir), Up: (dir), Next: Introduction
+
+{BBDB Filters}
+
+{6}
+
+Copyright (C)1995 NEDA COMMUNICATIONS, INC.
+
+
+* Menu:
+
+* Introduction::
+* Output Filters::
+* Input Filters::
+* Miscellany::
+* GNU LIBRARY GENERAL PUBLIC LICENSE::
+* Concept Index::
+* Command Index::
+
+ --- The Detailed Node Listing ---
+
+Introduction
+
+* About This Package::
+* About This Manual::
+
+Output Filters
+
+* HP 200LX Phone Book::
+* PC Eudora::
+* Lotus cc:Mail Nicknames::
+* PH::
+* Emacs Lisp Export::
+
+PC Eudora
+
+* PC Eudora Nickname Database::
+* PC Eudora Recipient Database::
+
+Input Filters
+
+* General Facilities for Input Filtering::
+* UNIX Password Files::
+
+Miscellany
+
+* TODO List::
+* Credits::
+
+GNU LIBRARY GENERAL PUBLIC LICENSE
+
+* Preamble::
+* TERMS AND CONDITIONS FOR COPYING:: *
+* NO WARRANTY::
+* END OF TERMS AND CONDITIONS::
+* How to Apply These Terms to Your New Libraries::
+
+
+
+File: bbdb-filters.info Node: Introduction, Prev: Top, Up: Top, Next: Output Filters
+
+Introduction
+************
+
+
+Over time much valuable data has been gathered in BBDB database files.
+Many wish to share parts or all of this information with others. They
+also wish to have access to this same information from other systems
+(like personal digital assistants) lacking straightforward BBDB
+access.
+
+For these reasons, we have prepared a family of filters that convert
+the information in BBDB to and from a variety of other
+formats. "Output filters" export BBDB information to other formats
+while "input filters" import information from other formats into
+BBDB.
+
+Our hope is that over time this collection of BBDB filters will grow
+through contributed code.
+
+
+* Menu:
+
+* About This Package::
+* About This Manual::
+
+
+
+File: bbdb-filters.info Node: About This Package, Prev: Introduction, Up: Introduction, Next: About This Manual
+
+About This Package
+==================
+
+
+This package is a collection of filters and is called "BBDB Input and
+Output Filters". It has been somewhat tested with BBDB version 1.50.
+The present state of the software is still preliminary although it has
+proved useful.
+
+
+File: bbdb-filters.info Node: About This Manual, Prev: About This Package, Up: Introduction
+
+About This Manual
+=================
+
+
+This documentation applies to Version 0.2 of the "BBDB Input and
+Output Filters" package. The documentation is presently skeletal and
+very preliminary. It mostly provides the user with instructions for
+use, and very little background is included. Familiarity with Emacs
+Lisp is assumed for some sections.
+
+
+File: bbdb-filters.info Node: Output Filters, Prev: Introduction, Up: Top, Next: Input Filters
+
+Output Filters
+**************
+
+
+"Output filters" are used to export BBDB information into formats
+used by other systems.
+
+In general, an output filter uses the contents of your
+`*BBDB*' buffer as input. Note that output filters do not use
+BBDB files (typically ``~/.bbdb'') directly.
+
+An output filter is invoked by executing its associated lisp function.
+The name of the function is conventionally named `bbdb-<system>-output'
+(e.g., `M-x bbdb-hp200lx-output').
+
+The result of running an output filter is to create a new buffer that
+contains the `*BBDB*' information appropriately transformed into a
+format suitable for use by the target system. The new buffer is given
+a file name that you specify.
+
+
+* Menu:
+
+* HP 200LX Phone Book::
+* PC Eudora::
+* Lotus cc:Mail Nicknames::
+* PH::
+* Emacs Lisp Export::
+
+
+
+File: bbdb-filters.info Node: HP 200LX Phone Book, Prev: Output Filters, Up: Output Filters, Next: PC Eudora
+
+HP 200LX Phone Book
+===================
+
+
+This package has only been tested on HP 200LX palmtop systems. It
+also requires the "HP 200LX Connectivity Pack" for converting
+comma-delimited ASCII files into binary .PDB files which are read by
+the HP 200LX Phone Book application. Version 1.00 of the "HP 200LX
+Connectivty Pack" was used for testing.
+
+The HP 200LX output filter is in file `bbdb-hp200lx.el'.
+
+
+
+ 1. Invoke `M-x bbdb' to populate the `*BBDB*' buffer
+ with the contents you wish to export.
+
+ 2. Invoke ` bbdb-hp200lx-output' to create an ASCII .CDF
+ (Comma Delimited File).
+
+ 3. Using Xlate/Merge option of HP Connectivity Pack convert the
+ .CDF file into a binary .PDB file used by the Phone Book program.
+
+ 4. Download the .PDB file to your palmtop's internal disk and
+ ensure that the Phone Book program is set use the newly downloaded
+ .PDB file.
+
+
+
+
+File: bbdb-filters.info Node: PC Eudora, Prev: HP 200LX Phone Book, Up: Output Filters, Next: Lotus cc:Mail Nicknames
+
+PC Eudora
+=========
+
+
+BBDB information can be exported to PC Eudora in two formats--as a
+nickname database file and as a recipients database file.
+
+The PC Eudora output filter is in file `bbdb-eudora.el'.
+
+* Menu:
+
+* PC Eudora Nickname Database::
+* PC Eudora Recipient Database::
+
+
+
+File: bbdb-filters.info Node: PC Eudora Nickname Database, Prev: PC Eudora, Up: PC Eudora, Next: PC Eudora Recipient Database
+
+PC Eudora Nickname Database
+---------------------------
+
+
+
+ 1. Invoke `M-x bbdb' to populate the `*BBDB*' buffer
+ with the contents you wish to export.
+
+ 2. Invoke `bbdb-eudora-nndbase-output' to create a PC Eudora
+ Nickname database file.
+
+ 3. Make the file accessible to PC Eudora.
+
+
+
+
+File: bbdb-filters.info Node: PC Eudora Recipient Database, Prev: PC Eudora Nickname Database, Up: PC Eudora
+
+PC Eudora Recipient Database
+----------------------------
+
+
+
+ 1. Invoke `M-x bbdb' to populate the `*BBDB*' buffer
+ with the contents you wish to export.
+
+ 2. Invoke `bbdb-eudora-rcpdbase-output' to create a PC Eudora
+ recipient's database file.
+
+ 3. Make the file accessible to PC Eudora.
+
+
+
+
+File: bbdb-filters.info Node: Lotus cc:Mail Nicknames, Prev: PC Eudora, Up: Output Filters, Next: PH
+
+Lotus cc:Mail Nicknames
+=======================
+
+
+The Lotus cc:Mail output filter is in file `bbdb-ccmail.el'.
+
+
+ 1. Invoke `M-x bbdb' to populate the `*BBDB*' buffer
+ with the contents you wish to export.
+
+ 2. Invoke ` bbdb-ccmail-output' to create a cc:Mail Nicknames file.
+
+ 3. Make the file accessible to cc:Mail.
+
+
+
+
+File: bbdb-filters.info Node: PH, Prev: Lotus cc:Mail Nicknames, Up: Output Filters, Next: Emacs Lisp Export
+
+PH
+==
+
+
+The PH output filter is in file `bbdb-ph.el'.
+
+
+ 1. Invoke `M-x bbdb' to populate the `*BBDB*' buffer
+ with the contents you wish to export.
+
+ 2. Invoke `bbdb-ph-output' to create a `ph' data file for
+ use with the `maked' program.
+
+ 3. Make the file accessible to `ph'.
+
+
+
+
+File: bbdb-filters.info Node: Emacs Lisp Export, Prev: PH, Up: Output Filters
+
+Emacs Lisp Export
+=================
+
+
+The Emacs Lisp Export output filter is in file `bbdb-export.el'.
+
+This output filter uses the current contents of your
+`*BBDB*' buffer to generate a new buffer (`*BBDB* Export')
+that contains a single lisp `(progn ...)' expression. For
+example, a `*BBDB*' buffer containing two records would result in
+the following `*BBDB* Export' buffer:
+
+
+ ;;; ======= Start of Exported BBDB Records =======
+ (progn
+ (require 'bbdb-com)
+ (defun bbdb-maybe-create (name company net &optional addrs phones notes)
+ "Try to add a record to BBDB if it does not already exist."
+ (condition-case err
+ (progn
+ (bbdb-create-internal name company net addrs phones notes)
+ (message "%s %s added." name (if net (concat "<" net ">") ""))
+ (sleep-for 1))
+ (error (ding)
+ (message "%s %s skipped. (%s)"
+ name
+ (if net (concat "<" net ">") "")
+ (car (cdr err)))
+ (sleep-for 1))))
+
+ (bbdb-maybe-create "Jill Doe--IMPORTED"
+ "CBS Corporation"
+ '("jilld@cbs.com")
+ '(
+ ["Home"
+ "368 222ND PL"
+ ""
+ ""
+ "Springfield"
+ "MA" 2117]
+ )
+ '(
+ ["Office" 617 555 9983 0]
+ ) '"Movie Mogul")
+ (bbdb-maybe-create "John Doe--IMPORTED"
+ "ABC Incorporated"
+ '("jdoe@abc.com")
+ '(
+ ["Office"
+ "123 Any Street"
+ ""
+ ""
+ "Any Town"
+ "WA" (98027 7758)]
+ )
+ '(
+ ["Office" 206 555 1234 0]
+ ) '"TV Producer")
+ )
+ ;;; ======= End of Exported BBDB Records =======
+
+
+This lisp expression can then be sent via email or some other
+text-based messaging facility to another user who can then evaluate
+the expression which will add the `BBDB' records to the
+recipient's
+`BBDB' database.
+
+Only new records are added. A record with the same name or net
+address as one already existing in the `BBDB' is skipped
+entirely.
+
+In the sample contents of a `*BBDB* Export' buffer presented, two
+records are being exported--one for "John Doe" and the other for
+"Jill Doe". Notice that their names have been appended with
+`--IMPORTED'. This string can be used to quick locate each record
+that is added to the database using this mechanism.
+
+The following steps are for exporting BBDB records into Emacs Lisp:
+
+
+ 1. Invoke `M-x bbdb' to populate the `*BBDB*' buffer
+ with the contents you wish to export.
+
+ 2. Invoke `bbdb-export' to create a `*BBDB* Export' buffer which contains a
+ single `(progn ...)' can be evaluated to add the records to the
+ existing `BBDB' database (if the records do not already exist).
+
+ 3. Use the contents of `*BBDB* Export' in email and other messaging systems.
+
+
+
+The following steps are for a user wishing to import the contents of a
+`*BBDB* Export' buffer's expression into his or her own database:
+
+
+ 1. Evaluate the region bounded by the lines
+ `;;; ======= Start of Exported BBDB Records ======='
+ and
+ `;;; ======= End of Exported BBDB Records ======='.
+ You can use such commands as
+ `M-x eval-region' or `M-x eval-last-sexp'.
+
+ 2. Review the newly imported entries. To see them, invoke `M-x
+ bbdb' and specify `--IMPORTED' at the `Regular Expression'
+ prompt.
+
+ 3. After reviewing the contents of the imported records, you may
+ wish to remove the `--IMPORTED' that is appended to the name by
+ `bbdb-export'.
+
+
+
+
+File: bbdb-filters.info Node: Input Filters, Prev: Output Filters, Up: Top, Next: Miscellany
+
+Input Filters
+*************
+
+
+"Input filters" are used to import into BBDB information from a
+foreign system's data file.
+
+The name of the function is conventionally named
+`bbdb-<system>-input' (e.g., `bbdb-passwd-input' is the name
+of the Emacs Lisp function for the UNIX password file input filter).
+
+In general, an "input filter" expects the foreign system's data to
+be in the current buffer. The contents of the current buffer are used
+to create an Emacs Lisp file which when loaded will add new records
+into your BBDB database if they don't yet exist--existing BBDB records
+will not be modified.
+
+
+* Menu:
+
+* General Facilities for Input Filtering::
+* UNIX Password Files::
+
+
+
+File: bbdb-filters.info Node: General Facilities for Input Filtering, Prev: Input Filters, Up: Input Filters, Next: UNIX Password Files
+
+General Facilities for Input Filtering
+======================================
+
+
+The result of running an input filter is to produce a new buffer a
+series of `bif-create-record'
+expressions, each corresponding to a single user's record. Notice
+that input filters do not directly modify the contents of the BBDB
+files (typically ``~/.bbdb'').
+
+To actually modify the contents of the BBDB database, you must
+evaluated the expressions in the resultant buffer created by the input
+filter. One way to do so is simply to invoke `M-x eval-buffer'.
+Another way is to simply save the buffer to disk and load its contents
+into Emacs Lisp using `M-x load-file'.
+
+
+File: bbdb-filters.info Node: UNIX Password Files, Prev: General Facilities for Input Filtering, Up: Input Filters
+
+UNIX Password Files
+===================
+
+
+The UNIX password file input filter is in file `bbdb-passwd.el'.
+
+
+ 1. Use `M-x find-file' to visit the UNIX password file you wish to import.
+
+ 2. With the password file in the current buffer, invoke the input
+ filter `M-x bbdb-passwd-input'. You will be prompted for the
+ domain name associated with that host's password file; an organization
+ name; as well as the file name to be associated with the buffer of
+ `bif-create-record' expressions.
+
+ 3. Evaluate the contents of the input filter's buffer to add records
+ into your BBDB database file.
+
+
+
+
+File: bbdb-filters.info Node: Miscellany, Prev: Input Filters, Up: Top, Next: GNU LIBRARY GENERAL PUBLIC LICENSE
+
+Miscellany
+**********
+
+
+
+* Menu:
+
+* TODO List::
+* Credits::
+
+
+
+File: bbdb-filters.info Node: TODO List, Prev: Miscellany, Up: Miscellany, Next: Credits
+
+TODO List
+=========
+
+
+
+ * Move generic input filter functionality out of
+ `bbdb-passwd.el' and into, say, `bbdb-ifilt.el'.
+ The generic functionality code has names typically prefixed with `bif-'.
+
+ * Add support for `gdbload' (as an alternative to the
+ Xlate/Merge application provided in the HP 200LX Connectivity Pack)
+ into the HP 200LX output filter. This is based on input from Robert
+ Nicholson `<robert@steffi.dircon.co.uk>'.
+
+ * Add documentation for variables in the various input and output filters.
+
+ * Check and document all dependencies on other packages.
+
+
+
+
+File: bbdb-filters.info Node: Credits, Prev: TODO List, Up: Miscellany
+
+Credits
+=======
+
+
+Pean Lim `<pean@neda.com>' wrote most of this package. Mohsen
+Banan `<mohsen@neda.com>' put it all together and guided the
+work. Neda Communications, Inc. sponsored the work. The output
+filters code is based on `bbdb-print' by Boris Goldowsky
+`<boris@prodigal.psych.rochester.edu>'.
+
+
+
+File: bbdb-filters.info Node: GNU LIBRARY GENERAL PUBLIC LICENSE, Prev: Miscellany, Up: Top, Next: Concept Index
+
+GNU LIBRARY GENERAL PUBLIC LICENSE
+**********************************
+
+
+ Version 2, June 1991
+
+
+
+ Copyright (C) 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.
+
+ [This is the first released version of the library GPL. It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+
+
+* Menu:
+
+* Preamble::
+* TERMS AND CONDITIONS FOR COPYING:: *
+* NO WARRANTY::
+* END OF TERMS AND CONDITIONS::
+* How to Apply These Terms to Your New Libraries::
+
+
+
+File: bbdb-filters.info Node: Preamble, Prev: GNU LIBRARY GENERAL PUBLIC LICENSE, Up: GNU LIBRARY GENERAL PUBLIC LICENSE, Next: TERMS AND CONDITIONS FOR COPYING
+
+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.
+
+
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+
+
+ 1. 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.
+
+ 2. 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.
+
+ 3. 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:
+
+ 1. The modified work must itself be a software library.
+
+ 2. You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ 3. You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ 4. 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.
+
+ 4. 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.
+
+ 5. 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.
+
+ 6. 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.
+
+ 7. 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:
+
+ 1. 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.)
+
+ 2. 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.
+
+ 3. 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.
+
+ 4. 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.
+
+ 8. 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:
+
+ 1. 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.
+
+ 2. 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.
+
+
+ 9. 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.
+
+ 10. 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.
+
+ 11. 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.
+
+ 12. 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.
+
+ 13. 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.
+
+ 14. 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.
+
+ 15. 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
+
+
+
+ 16. 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.
+
+ 17. 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
+
+
+
+
+
+File: bbdb-filters.info Node: How to Apply These Terms to Your New Libraries, Prev: END OF TERMS AND CONDITIONS, Up: GNU LIBRARY GENERAL PUBLIC LICENSE
+
+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 AN 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 Software Foundation, Inc., 675 Mass Ave, Cambridge,
+ MA 02139, 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!
+
+
+
+
+File: bbdb-filters.info Node: Concept Index, Prev: GNU LIBRARY GENERAL PUBLIC LICENSE, Up: Top, Next: Command Index
+
+Concept Index
+*************
+
+
+
+* Menu:
+
+* About This Manual: About This Manual.
+* About This Package: About This Package.
+* .CDF file, HP 200LX Phone Book: HP 200LX Phone Book.
+* Credits: Credits.
+* Emacs Lisp Export: Emacs Lisp Export.
+* General Facilities for Input Filtering: General Facilities for Input Filtering.
+* GNU LIBRARY GENERAL PUBLIC LICENSE: GNU LIBRARY GENERAL PUBLIC LICENSE.
+* How to Apply These Terms to Your New Libraries: How to Apply These Terms to Your New Libraries.
+* HP 200LX Connectivity Pack: HP 200LX Phone Book.
+* HP 200LX Phone Book: HP 200LX Phone Book.
+* Input Filters: Input Filters.
+* Introduction: Introduction.
+* Lotus cc:Mail Nicknames: Lotus cc:Mail Nicknames.
+* Miscellany: Miscellany.
+* Output Filters: Output Filters.
+* PC Eudora Nickname Database: PC Eudora Nickname Database.
+* PC Eudora: PC Eudora.
+* PC Eudora Recipient Database: PC Eudora Recipient Database.
+* .PDF file, HP 200LX Phone Book: HP 200LX Phone Book.
+* PH: PH.
+* Preamble: Preamble.
+* Sending BBDB records via email: Emacs Lisp Export.
+* TODO List: TODO List.
+* UNIX Password Files: UNIX Password Files.
+
+
+
+
+File: bbdb-filters.info Node: Command Index, Prev: Concept Index, Up: Top
+
+Command Index
+*************
+
+
+
+* Menu:
+
+* bbdb-ccmail-output: Lotus cc:Mail Nicknames.
+* bbdb-eudora-nndbase-output: PC Eudora Nickname Database.
+* bbdb-eudora-rcpdbase-output: PC Eudora Recipient Database.
+* bbdb-export: Emacs Lisp Export.
+* bbdb-hp200lx-output: HP 200LX Phone Book.
+* bbdb-passwd-input: UNIX Password Files.
+* bbdb-ph-output: PH.
+* bif-create-record: General Facilities for Input Filtering.
+
+
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-04 04:43:25 +0000