diff options
author | Christian Grothoff <christian@grothoff.org> | 2012-09-06 11:19:05 +0000 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2012-09-06 11:19:05 +0000 |
commit | d4b798ab8e490638f9b201cfaaacec0504cd9184 (patch) | |
tree | 78bed4cef3fc5158ef5b27b96b169fdeb06ada60 | |
parent | 7f89e1310ac49abd17c8bec91e47deec137b9bc1 (diff) | |
download | libextractor-d4b798ab8e490638f9b201cfaaacec0504cd9184.tar.gz libextractor-d4b798ab8e490638f9b201cfaaacec0504cd9184.zip |
-typos
-rw-r--r-- | doc/libextractor.3 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/libextractor.3 b/doc/libextractor.3 index 7c7c004..043b193 100644 --- a/doc/libextractor.3 +++ b/doc/libextractor.3 | |||
@@ -34,12 +34,12 @@ GNU libextractor \- meta\-information extraction library 1.0.0 | |||
34 | .P | 34 | .P |
35 | GNU libextractor is a simple library for keyword extraction. libextractor does not support all formats but supports a simple plugging mechanism such that you can quickly add extractors for additional formats, even without recompiling libextractor. libextractor typically ships with dozens of plugins that can be used to obtain meta data from common file-types. If you want to write your own plugin for some filetype, all you need to do is write a little library that implements a single method with this signature: | 35 | GNU libextractor is a simple library for keyword extraction. libextractor does not support all formats but supports a simple plugging mechanism such that you can quickly add extractors for additional formats, even without recompiling libextractor. libextractor typically ships with dozens of plugins that can be used to obtain meta data from common file-types. If you want to write your own plugin for some filetype, all you need to do is write a little library that implements a single method with this signature: |
36 | 36 | ||
37 | \fBvoid EXTRACTOR_XXX_extract_method (struct EXTRACTOR_ExtractContext *ec); | 37 | \fBvoid EXTRACTOR_XXX_extract_method (struct EXTRACTOR_ExtractContext *\fIec\fB);\fP |
38 | 38 | ||
39 | .P | 39 | .P |
40 | 'ec' contains function pointers for reading, seeking, getting the overall file size and returning meta data. There is also a field with options for the plugin. New plugins will be automatically located and used once they are installed in the respective directory (typically something like /usr/lib/libextractor/). | 40 | \fIec\fP contains function pointers for reading, seeking, getting the overall file size and returning meta data. There is also a field with options for the plugin. New plugins will be automatically located and used once they are installed in the respective directory (typically something like /usr/lib/libextractor/). |
41 | .P | 41 | .P |
42 | The application 'extract' gives an example how to use libextractor. | 42 | The application \fBextract\fP gives an example how to use libextractor. |
43 | .P | 43 | .P |
44 | The basic use of libextractor is to load the plugins (for example with \fBEXTRACTOR_plugin_add_defaults\fP), then to extract the keyword list using \fBEXTRACTOR_extract\fP, and finally unloading the plugins (with \fBEXTRACTOR_plugin_remove_all\fP). | 44 | The basic use of libextractor is to load the plugins (for example with \fBEXTRACTOR_plugin_add_defaults\fP), then to extract the keyword list using \fBEXTRACTOR_extract\fP, and finally unloading the plugins (with \fBEXTRACTOR_plugin_remove_all\fP). |
45 | .P | 45 | .P |