docset doc html2htmlps
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 516
DocSet::Doc::HTML2HTMLPS 0.19
DocSet::Doc::HTML2HTMLPS is a HTML source to PS (intermediate HTML) target converter. more>>
DocSet::Doc::HTML2HTMLPS is a HTML source to PS (intermediate HTML) target converter.
See DocSet::Doc::HTML2HTML. This sub-class only extends the postprocess() method.
METHODS
For the rest of the super class methods see DocSet::Doc::HTML2HTML.
postprocess()
Convert the generated HTML doc to PS and PDF.
<<lessSee DocSet::Doc::HTML2HTML. This sub-class only extends the postprocess() method.
METHODS
For the rest of the super class methods see DocSet::Doc::HTML2HTML.
postprocess()
Convert the generated HTML doc to PS and PDF.
Download (0.36MB)
Added: 2007-03-10 License: Perl Artistic License Price:
961 downloads
DocSet::Doc::Common 0.19
DocSet::Doc::Common is a Perl module with common functions used in DocSet::Doc subclasses. more>>
DocSet::Doc::Common is a Perl module with common functions used in DocSet::Doc subclasses.
Implements functions and bits of code which otherwise needed to be duplicated in many modules. These functions couldnt be put into the base class DocSet::Doc. Certainly we could devise one more subclassing level but for now this gentle mix of inheritance and inclusion is doing its job just fine.
METHODS
postprocess_ps_pdf
$self->postprocess_ps_pdf()
renders ps and pdf version of a the current doc
fetch_pdf_doc_ver
%pdf_data = %{ $self->fetch_pdf_doc_ver() }
search for a pdf version of the same document in the parallel tree (usually the dst_html tree) and copy it to the same dir as the html version. Later we link to it from the html version of the document if the pdf version is found in the same directory as the html one.
The function returns a reference to a hash with the keys: size -- for the size of the file and the location of the file relative to the current document (its in the same directory after all).
fetch_src_doc_ver
similar to fetch_pdf_doc_ver() but works with the source version of the document.
%src_data = %{ $self->fetch_src_doc_ver() }
fetch the source version of the same document in the parallel tree (usually the src tree) and copy it to the same dir as the html version. Later we link to it from the html version of the document if the source version is found in the same directory as the html one. Notice that we add a .orig extension, because otherwise the rendered version of the source document may have the same full name as the source file (e.g. if the source was .html and destination one is .html too).
The function returns a reference to a hash with the keys: size -- for the size of the source file and the location of the file relative to the current document (its in the same directory after all).
pod_pom_html_view_seq_link_transform_path
my $linked_doc_path =
$self->pod_pom_html_view_seq_link_transform_path($src_path)
this is an implementation of the view_seq_link_transform_path() callback used in Pod::POM::HTML::view_seq_link(), using the DocSet::Docs transform_src_doc() method over pre-scanned cache of the source documents the $src_path is resolved into the path in the generated docset. So for example a the resource devel::help in L pod_pom_html_anchor($title);
this is a common function that takes the $title Pod::POM object, converts it into a < a name > html anchor and returns it.
<<lessImplements functions and bits of code which otherwise needed to be duplicated in many modules. These functions couldnt be put into the base class DocSet::Doc. Certainly we could devise one more subclassing level but for now this gentle mix of inheritance and inclusion is doing its job just fine.
METHODS
postprocess_ps_pdf
$self->postprocess_ps_pdf()
renders ps and pdf version of a the current doc
fetch_pdf_doc_ver
%pdf_data = %{ $self->fetch_pdf_doc_ver() }
search for a pdf version of the same document in the parallel tree (usually the dst_html tree) and copy it to the same dir as the html version. Later we link to it from the html version of the document if the pdf version is found in the same directory as the html one.
The function returns a reference to a hash with the keys: size -- for the size of the file and the location of the file relative to the current document (its in the same directory after all).
fetch_src_doc_ver
similar to fetch_pdf_doc_ver() but works with the source version of the document.
%src_data = %{ $self->fetch_src_doc_ver() }
fetch the source version of the same document in the parallel tree (usually the src tree) and copy it to the same dir as the html version. Later we link to it from the html version of the document if the source version is found in the same directory as the html one. Notice that we add a .orig extension, because otherwise the rendered version of the source document may have the same full name as the source file (e.g. if the source was .html and destination one is .html too).
The function returns a reference to a hash with the keys: size -- for the size of the source file and the location of the file relative to the current document (its in the same directory after all).
pod_pom_html_view_seq_link_transform_path
my $linked_doc_path =
$self->pod_pom_html_view_seq_link_transform_path($src_path)
this is an implementation of the view_seq_link_transform_path() callback used in Pod::POM::HTML::view_seq_link(), using the DocSet::Docs transform_src_doc() method over pre-scanned cache of the source documents the $src_path is resolved into the path in the generated docset. So for example a the resource devel::help in L pod_pom_html_anchor($title);
this is a common function that takes the $title Pod::POM object, converts it into a < a name > html anchor and returns it.
Download (0.37MB)
Added: 2007-03-10 License: Perl Artistic License Price:
958 downloads
idl2html 2.41
idl2html is a Perl module that enerates HTML documentation from IDL source files. more>>
idl2html is a Perl module that enerates HTML documentation from IDL source files.
SYNOPSIS
idl2html [options] spec.idl
OPTIONS
All options are forwarded to C preprocessor, except -f -h -i -o -s -t -v -x.
With the GNU C Compatible Compiler Processor, useful options are :
-D name
-D name=definition
-I directory
-I-
-nostdinc
Specific options :
-f
Enable the frameset mode.
-h
Display help.
-i directory
Specify a path for import (only for version 3.0).
-o file
Specificy the outfile for HTML Help (default "htmlhelp").
-s style
Generate an external Cascading Style Sheet file.
-t title
Specificy the title of HTML Help.
-v
Display version.
-x
Enable export (only for version 3.0).
idl2html parses the declarations and doc comments in a IDL source file and formats these into a set of HTML pages. idl2html generates some helper files for HTML Help compiler.
idl2html works like javadoc.
Within doc comments, idl2html supports the use of special doc tags to augment the documentation. idl2html also supports standard HTML within doc comments. This is useful for formatting text.
idl2html reformats and displays declaration for:
Modules, interfaces and value types
Operations (with parameters) and attributes
Types (typedef, enum, struct, union with members)
Exceptions (with members)
Constants
Pragma (ID, version as tag)
<<lessSYNOPSIS
idl2html [options] spec.idl
OPTIONS
All options are forwarded to C preprocessor, except -f -h -i -o -s -t -v -x.
With the GNU C Compatible Compiler Processor, useful options are :
-D name
-D name=definition
-I directory
-I-
-nostdinc
Specific options :
-f
Enable the frameset mode.
-h
Display help.
-i directory
Specify a path for import (only for version 3.0).
-o file
Specificy the outfile for HTML Help (default "htmlhelp").
-s style
Generate an external Cascading Style Sheet file.
-t title
Specificy the title of HTML Help.
-v
Display version.
-x
Enable export (only for version 3.0).
idl2html parses the declarations and doc comments in a IDL source file and formats these into a set of HTML pages. idl2html generates some helper files for HTML Help compiler.
idl2html works like javadoc.
Within doc comments, idl2html supports the use of special doc tags to augment the documentation. idl2html also supports standard HTML within doc comments. This is useful for formatting text.
idl2html reformats and displays declaration for:
Modules, interfaces and value types
Operations (with parameters) and attributes
Types (typedef, enum, struct, union with members)
Exceptions (with members)
Constants
Pragma (ID, version as tag)
Download (0.14MB)
Added: 2007-05-30 License: Perl Artistic License Price:
877 downloads
Gantry::Docs::TOC 3.38
Gantry::Docs::TOC is a table of contents for Gantry::Docs::* documentation modules. more>>
Gantry::Docs::TOC is a table of contents for Gantry::Docs::* documentation modules.
What should I read?
This document is a brief annotated list of each Gantry::Docs::* module.
About.pm
Describes the history, features, and motivation behind Gantry.
DBConn.pm
Explains how database connection information flows from app configuration to DBI. The process should be seamless for app developers, but if you need to work on the engines or add support for in ORMs, you may find useful information here.
FAQ.pm
A list of questions we think people are likely to ask along with answers. This is not a philosphical document, it is filled with code examples.
QuickStart.pm
If you are new Gantry and want to get your first app running with a minimum of fuss, this is for you.
TOC.pm
This document.
Tutorial.pm
More detailed than the Quick Start, this document walks through building a simple application with Gantry.
Why.pm
Explains you should use a framework at all, whether it is Gantry or one of the many others.
<<lessWhat should I read?
This document is a brief annotated list of each Gantry::Docs::* module.
About.pm
Describes the history, features, and motivation behind Gantry.
DBConn.pm
Explains how database connection information flows from app configuration to DBI. The process should be seamless for app developers, but if you need to work on the engines or add support for in ORMs, you may find useful information here.
FAQ.pm
A list of questions we think people are likely to ask along with answers. This is not a philosphical document, it is filled with code examples.
QuickStart.pm
If you are new Gantry and want to get your first app running with a minimum of fuss, this is for you.
TOC.pm
This document.
Tutorial.pm
More detailed than the Quick Start, this document walks through building a simple application with Gantry.
Why.pm
Explains you should use a framework at all, whether it is Gantry or one of the many others.
Download (0.19MB)
Added: 2006-10-17 License: GPL (GNU General Public License) Price:
1103 downloads
Bigtop::Docs::TOC 0.18
Bigtop::Docs::TOC is a table of contents for Bigtop::Docs::* documentation modules. more>>
Bigtop::Docs::TOC is a table of contents for Bigtop::Docs::* documentation modules.
What Should I Read?
This document is a brief annotated list of each Bigtop::Docs::* module.
Here are the highlights:
Lazy people should start with Bigtop::Docs::TentTut
Those allergic to web apps should start with Bigtop::Docs::Tutorial
Pedants should look in Bigtop::Docs::Syntax instead
Developers should carefully read Bigtop::Docs::Modules
Bigtop::Docs::About
Describes the features and motivations of Bigtop.
Bigtop::Docs::Cookbook
Modeled after the Perl Cookbook, this provides a list of things you might want to do, the syntax needed to make Bigtop do them for you, and the output produced by them. It focuses on hand written bigtop files, rather than on tentmaker.
Bigtop::Docs::Keywords
A (fairly) complete list of keywords Bigtop understands in a compact text file. See Bigtop::Docs::QuickRef for most of the same information in html tabular formatting or run tentmaker which shows complete information in your browser.
Bigtop::Docs::Modules
Documents many of the modules in the bigtop distribution including at least: Bigtop.pm, Bigtop::Parser. This includes a description of the grammar of the Bigtop language and how to work with it. (Note that the grammar is now in its own file called bigtop.grammar, but this has no effect on the docs in Bigtop::Docs::Modules. It may be out of date, but the extraction of the grammar is not the reason.)
Bigtop::Docs::QuickRef
This provides a somewhat complete list of all the keywords Bigtop understands along with some examples in html form. The depth of the tables involved makes it somewhat difficult to use. For a more compact version in plain text, see Bigtop::Docs::Keywords or run tentmaker for complete information in a different web format.
Bigtop::Docs::Syntax
This is meant to fully describe all of the syntax (including deprecations) in the Bigtop language. It is the encyclopedic version of Bigtop::Docs::Keywords.
Bigtop::Docs::TentTut
The tentmaker tutorial. Explains in detail how to use tentmaker to edit Bigtop files. Filled with beautiful screen shots.
Bigtop::Docs::TentRef
A comprehensive tour of tentmaker which assumes you understand the material from Bigtop::Docs::TentTut.
Bigtop::Docs::Tutorial
If you dont like tentmaker, this is where you should start. It walks through building a moderately complex application from scratch using a text editor to enter the proper Bigtop syntax.
Bigtop::Docs::Vim
Explains how to install vim syntax highlighting for Bigtop source files.
<<lessWhat Should I Read?
This document is a brief annotated list of each Bigtop::Docs::* module.
Here are the highlights:
Lazy people should start with Bigtop::Docs::TentTut
Those allergic to web apps should start with Bigtop::Docs::Tutorial
Pedants should look in Bigtop::Docs::Syntax instead
Developers should carefully read Bigtop::Docs::Modules
Bigtop::Docs::About
Describes the features and motivations of Bigtop.
Bigtop::Docs::Cookbook
Modeled after the Perl Cookbook, this provides a list of things you might want to do, the syntax needed to make Bigtop do them for you, and the output produced by them. It focuses on hand written bigtop files, rather than on tentmaker.
Bigtop::Docs::Keywords
A (fairly) complete list of keywords Bigtop understands in a compact text file. See Bigtop::Docs::QuickRef for most of the same information in html tabular formatting or run tentmaker which shows complete information in your browser.
Bigtop::Docs::Modules
Documents many of the modules in the bigtop distribution including at least: Bigtop.pm, Bigtop::Parser. This includes a description of the grammar of the Bigtop language and how to work with it. (Note that the grammar is now in its own file called bigtop.grammar, but this has no effect on the docs in Bigtop::Docs::Modules. It may be out of date, but the extraction of the grammar is not the reason.)
Bigtop::Docs::QuickRef
This provides a somewhat complete list of all the keywords Bigtop understands along with some examples in html form. The depth of the tables involved makes it somewhat difficult to use. For a more compact version in plain text, see Bigtop::Docs::Keywords or run tentmaker for complete information in a different web format.
Bigtop::Docs::Syntax
This is meant to fully describe all of the syntax (including deprecations) in the Bigtop language. It is the encyclopedic version of Bigtop::Docs::Keywords.
Bigtop::Docs::TentTut
The tentmaker tutorial. Explains in detail how to use tentmaker to edit Bigtop files. Filled with beautiful screen shots.
Bigtop::Docs::TentRef
A comprehensive tour of tentmaker which assumes you understand the material from Bigtop::Docs::TentTut.
Bigtop::Docs::Tutorial
If you dont like tentmaker, this is where you should start. It walks through building a moderately complex application from scratch using a text editor to enter the proper Bigtop syntax.
Bigtop::Docs::Vim
Explains how to install vim syntax highlighting for Bigtop source files.
Download (0.39MB)
Added: 2006-10-18 License: Perl Artistic License Price:
1101 downloads
KinoSearch::Document::Doc 0.15
KinoSearch::Document::Doc is a Doc object that is akin to a row in a database, in that it is made up of several fields. more>>
KinoSearch::Document::Doc is a Doc object that is akin to a row in a database, in that it is made up of several fields, each of which has a value. Doc objects are only created via factory methods of other classes.
SYNOPSIS
my $doc = $invindexer->new_doc;
$doc->set_value( title => $title );
$doc->set_value( bodytext => $bodytext );
$invindexer->add($doc);
METHODS
set_value get_value
$doc->set_value( title => $title_text );
my $text = $doc->get_value( title );
set_value and get_value are used to modify and access the values of the fields within a Doc object.
set_boost get_boost
$doc->set_boost(2.5);
boost is a scoring multiplier. Setting boost to something other than 1 causes a document to score better or worse against a given query relative to other documents.
<<lessSYNOPSIS
my $doc = $invindexer->new_doc;
$doc->set_value( title => $title );
$doc->set_value( bodytext => $bodytext );
$invindexer->add($doc);
METHODS
set_value get_value
$doc->set_value( title => $title_text );
my $text = $doc->get_value( title );
set_value and get_value are used to modify and access the values of the fields within a Doc object.
set_boost get_boost
$doc->set_boost(2.5);
boost is a scoring multiplier. Setting boost to something other than 1 causes a document to score better or worse against a given query relative to other documents.
Download (0.22MB)
Added: 2007-03-09 License: Perl Artistic License Price:
959 downloads
Parrot::Docs::Section::C 0.4.5
Parrot::Docs::Section::C is a C source code documentation section. more>>
Parrot::Docs::Section::C is a C source code documentation section.
SYNOPSIS
use Parrot::Docs::Section::C;
A documentation section describing all the C source code in Parrot.
Class Methods
header_item($text, @names)
Returns a C header files documentation item.
c_source_item($text, @names)
Returns a C source files documentation item.
c_pair_item($text, $name)
Returns a new C source and header file documentation item.
c_item($text, %contents)
Returns a new C source and/or header files documentation item. Recognized keys for %contents are pairs, sources, headers and contents.
new()
Returns a new section.
<<lessSYNOPSIS
use Parrot::Docs::Section::C;
A documentation section describing all the C source code in Parrot.
Class Methods
header_item($text, @names)
Returns a C header files documentation item.
c_source_item($text, @names)
Returns a C source files documentation item.
c_pair_item($text, $name)
Returns a new C source and header file documentation item.
c_item($text, %contents)
Returns a new C source and/or header files documentation item. Recognized keys for %contents are pairs, sources, headers and contents.
new()
Returns a new section.
Download (3.1MB)
Added: 2006-07-05 License: Perl Artistic License Price:
1206 downloads
csvdiff 0.1 (English Docs)
csvdiff is a simple script for comparing two files of comma-separated values with each other. more>>
csvdiff is a simple script for comparing two files of comma-separated values with each other. In contrast to standard diff, it will show the number of the record where the difference occurs, the column number, and (if provided) the fieldname which is different.
The separator can be set to any value you want, not just a comma. It also provides support for multiple column keys, the ability to ignore case and trim leading/tailing spaces, and the ability to ignore selected columns such as timestamps.
<<lessThe separator can be set to any value you want, not just a comma. It also provides support for multiple column keys, the ability to ignore case and trim leading/tailing spaces, and the ability to ignore selected columns such as timestamps.
Download (0.31MB)
Added: 2007-07-24 License: GPL (GNU General Public License) Price:
837 downloads
Doc_comment 1.0
Doc_comment provides a PHP/MySQL document collaboration/review wiki. more>>
Doc_comment provides a PHP/MySQL document collaboration/review wiki.
Doc_comment is a simple PHP/MySQL document collaboration system that lets admin users upload documents/files for viewing and wiki-style commenting by other users.
It uses .htaccess to provide 3 security tiers, plus an additional password for admin.
It relies on browser plugins to display non-HTML files in the viewing frame (.pdf, .doc, .ppt, .xls, etc.).
INSTALL
-Use DATABASE.txt to create a MySQL database
-Use htpasswd -c to create password files corresponding to the doc, doc2, doc3 documents directories.
-If you want .htaccess for the first level of docs and the menu screen, then confgure .htaccess in the doc_comment directory
-Set correct path to AuthUserFile in .htaccess in doc2, doc3 directories (or configure .htaccess for directory in httpd.conf)
-Set variables in includes/config.php
-Make sure PHP can write to doc directories
<<lessDoc_comment is a simple PHP/MySQL document collaboration system that lets admin users upload documents/files for viewing and wiki-style commenting by other users.
It uses .htaccess to provide 3 security tiers, plus an additional password for admin.
It relies on browser plugins to display non-HTML files in the viewing frame (.pdf, .doc, .ppt, .xls, etc.).
INSTALL
-Use DATABASE.txt to create a MySQL database
-Use htpasswd -c to create password files corresponding to the doc, doc2, doc3 documents directories.
-If you want .htaccess for the first level of docs and the menu screen, then confgure .htaccess in the doc_comment directory
-Set correct path to AuthUserFile in .htaccess in doc2, doc3 directories (or configure .htaccess for directory in httpd.conf)
-Set variables in includes/config.php
-Make sure PHP can write to doc directories
Download (0.010MB)
Added: 2007-02-07 License: GPL (GNU General Public License) Price:
990 downloads
OODoc 0.95
OODoc is an Object Oriented documentation generator. more>>
OODoc is an Object Oriented documentation generator.
SYNOPSIS
use OODoc;
my $doc = OODoc->new(distribution => My Name, version => 0.02);
$doc->processFiles(workdir => $dest);
$doc->prepare;
$doc->create(pod, workdir => $dest);
$doc->create(html, workdir => /tmp/html);
OODoc stands for "Object Oriented Documentation": to produce manual-pages in HTML or the usual man-page UNIX format, describing Perl programs. The OO part refers to two things: this module simplifies writing documentation for Object Oriented programs, and at the same time, it is Object Oriented itself: easily extensible.
OODoc has been used for small and for very large modules. It can also be used to integrate manual-pages from many modules into one homogeneous set.
The documentation syntax can be changed, by configuring the parser or adding a new one. The OODoc::Parser::Markov parser understands POD and has additional logical markup tags. See OODoc::Parser about what each parser needs to support.
The output is produced by formatters. The current implementation contains two POD formatters and one HTML formatter. See OODoc::Format.
Do not forget to read the DETAILS section, later on this manual-page to get started. Please contribute ideas. Have a look at the main website of this project at http://perl.overmeer.net/oodoc/. That is also an example of the produced output.
<<lessSYNOPSIS
use OODoc;
my $doc = OODoc->new(distribution => My Name, version => 0.02);
$doc->processFiles(workdir => $dest);
$doc->prepare;
$doc->create(pod, workdir => $dest);
$doc->create(html, workdir => /tmp/html);
OODoc stands for "Object Oriented Documentation": to produce manual-pages in HTML or the usual man-page UNIX format, describing Perl programs. The OO part refers to two things: this module simplifies writing documentation for Object Oriented programs, and at the same time, it is Object Oriented itself: easily extensible.
OODoc has been used for small and for very large modules. It can also be used to integrate manual-pages from many modules into one homogeneous set.
The documentation syntax can be changed, by configuring the parser or adding a new one. The OODoc::Parser::Markov parser understands POD and has additional logical markup tags. See OODoc::Parser about what each parser needs to support.
The output is produced by formatters. The current implementation contains two POD formatters and one HTML formatter. See OODoc::Format.
Do not forget to read the DETAILS section, later on this manual-page to get started. Please contribute ideas. Have a look at the main website of this project at http://perl.overmeer.net/oodoc/. That is also an example of the produced output.
Download (0.095MB)
Added: 2006-09-28 License: Perl Artistic License Price:
1122 downloads
Docs::US_DOD::STrP 0.06
Docs::US_DOD::STrP is a Perl module. more>>
Docs::US_DOD::STrP is a Perl module.
The Software Transition Plan (STrP) identifies the hardware, software, and other resources needed for life cycle support of deliverable software and describes the developers plans for transitioning deliverable items to the support agency.
The STrP is developed if the software support concept calls for transition of responsibility from the developer to a separate support agency. The STrP may also be used by the acquirer for updating the Computer Resources Life Cycle Management Plan.
<<lessThe Software Transition Plan (STrP) identifies the hardware, software, and other resources needed for life cycle support of deliverable software and describes the developers plans for transitioning deliverable items to the support agency.
The STrP is developed if the software support concept calls for transition of responsibility from the developer to a separate support agency. The STrP may also be used by the acquirer for updating the Computer Resources Life Cycle Management Plan.
Download (0.16MB)
Added: 2006-09-26 License: Perl Artistic License Price:
1123 downloads
OODoc::Format::Pod 0.98
OODoc::Format::Pod is a Perl module to produce POD pages from the doc tree. more>>
OODoc::Format::Pod is a Perl module to produce POD pages from the doc tree.
INHERITANCE
OODoc::Format::Pod
is an OODoc::Format
is an OODoc::Object
OODoc::Format::Pod is extended by
OODoc::Format::Pod2
SYNOPSIS
my $doc = OODoc->new(...);
$doc->create
( pod
, format_options => [show_examples => NO]
, append => "extra textn"
);
Create manual pages in the POD syntax. POD is the standard document description syntax for Perl. POD can be translated to many different operating system specific manual systems, like the Unix man system.
<<lessINHERITANCE
OODoc::Format::Pod
is an OODoc::Format
is an OODoc::Object
OODoc::Format::Pod is extended by
OODoc::Format::Pod2
SYNOPSIS
my $doc = OODoc->new(...);
$doc->create
( pod
, format_options => [show_examples => NO]
, append => "extra textn"
);
Create manual pages in the POD syntax. POD is the standard document description syntax for Perl. POD can be translated to many different operating system specific manual systems, like the Unix man system.
Download (0.10MB)
Added: 2007-03-09 License: Perl Artistic License Price:
962 downloads
MARC::Doc::Tutorial 2.00
MARC::Doc::Tutorial is a documentation-only module for new users of MARC::Record. more>>
MARC::Doc::Tutorial is a documentation-only module for new users of MARC::Record.
SYNOPSIS
perldoc MARC::Doc::Tutorial
What is MARC?
The MAchine Readable Cataloging format was designed by the Library of Congress in the late 1960s in order to allow libraries to convert their card catalogs into a digital format. The advantages of having computerized card catalogs were soon realized, and now MARC is being used by all sorts of libraries around the world to provide computerized access to their collections. MARC data in transmission format is optimized for processing by computers, so its not very readable for the normal human. For more about the MARC format, visit the Library of Congress at http://www.loc.gov/marc/
What is this Tutorial?
The document you are reading is a beginners guide to using Perl to processing MARC data, written in the cookbook style. Inside, you will find recipes on how to read, write, update and convert MARC data using the MARC::Record CPAN package. As with any cookbook, you should feel free to dip in at any section and use the recipe you find interesting.
If you are new to Perl, you may want to read from the beginning.
The document you are reading is distributed with the MARC::Record package, however in case you are reading it somewhere else, you can find the latest version at CPAN: http://www.cpan.org/modules/by-module/MARC/. Youll notice that some sections arent filled in yet, which is a result of this document being a work in progress. If you have ideas for new sections please make a suggestion to perl4lib: http://www.rice.edu/perl4lib/.
<<lessSYNOPSIS
perldoc MARC::Doc::Tutorial
What is MARC?
The MAchine Readable Cataloging format was designed by the Library of Congress in the late 1960s in order to allow libraries to convert their card catalogs into a digital format. The advantages of having computerized card catalogs were soon realized, and now MARC is being used by all sorts of libraries around the world to provide computerized access to their collections. MARC data in transmission format is optimized for processing by computers, so its not very readable for the normal human. For more about the MARC format, visit the Library of Congress at http://www.loc.gov/marc/
What is this Tutorial?
The document you are reading is a beginners guide to using Perl to processing MARC data, written in the cookbook style. Inside, you will find recipes on how to read, write, update and convert MARC data using the MARC::Record CPAN package. As with any cookbook, you should feel free to dip in at any section and use the recipe you find interesting.
If you are new to Perl, you may want to read from the beginning.
The document you are reading is distributed with the MARC::Record package, however in case you are reading it somewhere else, you can find the latest version at CPAN: http://www.cpan.org/modules/by-module/MARC/. Youll notice that some sections arent filled in yet, which is a result of this document being a work in progress. If you have ideas for new sections please make a suggestion to perl4lib: http://www.rice.edu/perl4lib/.
Download (0.77MB)
Added: 2007-07-10 License: GPL (GNU General Public License) Price:
836 downloads
GTK-Doc 1.8
GTK-Doc is a GTK+ DocBook Documentation Generator. more>>
GTK-Doc is used to document C code. It is typically used to document the public API of libraries, such as the GTK+ and GNOME libraries, but it can also be used to document application code.
Note that GTK-Doc wasnt originally intended to be a general-purpose documentation tool, so it can be a bit awkward to setup and use. For a more polished general-purpose documentation tool you may want to look at Doxygen (http://www.doxygen.org/). However GTK-Doc has some special code to document the signals and properties of GTK+ widgets and GObject classes which other tools may not have.
GTK-Doc allows your documentation to be written in 2 ways:
a) Embedded inside the source code in specially-formatted comments.
or
b) Added to the template files which gtk-doc outputs after scanning all the header files and parsing the declarations.
From these source code comments and template files GTK-Doc generates a Docbook XML (or SGML) document, which is then transformed into HTML. The generated HTML documentation can be browsed in an ordinary web browser or by using the special Devhelp API browser (see http://developer.imendio.com/wiki/Devhelp).
<<lessNote that GTK-Doc wasnt originally intended to be a general-purpose documentation tool, so it can be a bit awkward to setup and use. For a more polished general-purpose documentation tool you may want to look at Doxygen (http://www.doxygen.org/). However GTK-Doc has some special code to document the signals and properties of GTK+ widgets and GObject classes which other tools may not have.
GTK-Doc allows your documentation to be written in 2 ways:
a) Embedded inside the source code in specially-formatted comments.
or
b) Added to the template files which gtk-doc outputs after scanning all the header files and parsing the declarations.
From these source code comments and template files GTK-Doc generates a Docbook XML (or SGML) document, which is then transformed into HTML. The generated HTML documentation can be browsed in an ordinary web browser or by using the special Devhelp API browser (see http://developer.imendio.com/wiki/Devhelp).
Download (0.23MB)
Added: 2007-02-19 License: LGPL (GNU Lesser General Public License) Price:
980 downloads
SekHost 1.2
SekHost is a host based firewall and packet prioritization utility for Linux systems. more>>
SekHost is a host based firewall and packet prioritization utility for Linux systems. The configuration is simple yet powerful functionality is available.
Installation of sekhost is very straightforward and actually only requires 2 things;
the sekhost script itself, which is in the src directory a configuration file. (examples in ./doc/examples) name your config file either /etc/default/sekhost or /etc/sekhost.conf
and you are ready to go!
You will find an interactive configuration option (sekhost configure).
After testing, you will want sekhost to start automatically on boot, so you will need to link it into the appropriate init level start up scripts.
A man page and a full Configuration doc file are in ./doc.
<<lessInstallation of sekhost is very straightforward and actually only requires 2 things;
the sekhost script itself, which is in the src directory a configuration file. (examples in ./doc/examples) name your config file either /etc/default/sekhost or /etc/sekhost.conf
and you are ready to go!
You will find an interactive configuration option (sekhost configure).
After testing, you will want sekhost to start automatically on boot, so you will need to link it into the appropriate init level start up scripts.
A man page and a full Configuration doc file are in ./doc.
Download (0.017MB)
Added: 2006-07-12 License: GPL (GNU General Public License) Price:
1199 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above docset doc html2htmlps search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
