Free documents software for linux

Borges is an open-source project aimed at XML-aware documentation projects which care about internationalisation, reusable contents, teamwork, etc. The system currently supports the DocBook DTD.
Main features:
- Easily write modular documentation in XML DocBook;
- Compile the source files into various formats, including PDF and HTML;
- Manage different versions of a single manual by easily defining derived versions based on conditional parts;
- Track the state of each module according to six predefined states (from "writing" to "final language proofreading"). Once a task is completed, the corresponding state is passed and the module switches to the next one;
- Each module is assigned a set of contributors: author/translators/proofreaders, each one responsible for one state of a module. Each contributor can easily review his attributions through web pages, and can receive e-mails with his current todo list;
- Track the work in progress, from the whole project (made of various manuals) to the most basic components (paragraphs), and their translations.
Enhancements:
- the modules images compilation issue is now solved
- requires xmllint

Structured Document Validator project implements a generalized method for validating both the structure and content of structured documents.

Any data format that can be deterministically divided into tags and data is classed as a structured document. This definition applies to a wide array of data formats, including XML, Java properties files, and delimited value files.

The application performs validations based on user-defined Structured Document Definitions (SDDs). It provides an environment for validation, SDD development, and document editing.

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.

XML::DOM::Document is an XML document node in XML::DOM.

XML::DOM::Document extends XML::DOM::Node.

It is the main root of the XML document structure as returned by XML::DOM::Parser::parse and XML::DOM::Parser::parsefile.

Since elements, text nodes, comments, processing instructions, etc. cannot exist outside the context of a Document, the Document interface also contains the factory methods needed to create these objects. The Node objects created have a getOwnerDocument method which associates them with the Document within whose context they were created.

METHODS

getDocumentElement

This is a convenience method that allows direct access to the child node that is the root Element of the document.

getDoctype

The Document Type Declaration (see DocumentType) associated with this document. For HTML documents as well as XML documents without a document type declaration this returns undef. The DOM Level 1 does not support editing the Document Type Declaration.

Not In DOM Spec: This implementation allows editing the doctype. See XML::DOM::ignoreReadOnly for details.

getImplementation

The DOMImplementation object that handles this document. A DOM application may use objects from multiple implementations.

createElement (tagName)

Creates an element of the type specified. Note that the instance returned implements the Element interface, so attributes can be specified directly on the returned object.

DOMExceptions:

INVALID_CHARACTER_ERR

Raised if the tagName does not conform to the XML spec.

createTextNode (data)

Creates a Text node given the specified string.

createComment (data)

Creates a Comment node given the specified string.

createCDATASection (data)

Creates a CDATASection node given the specified string.

createAttribute (name [, value [, specified ]])

Creates an Attr of the given name. Note that the Attr instance can then be set on an Element using the setAttribute method.

Not In DOM Spec: The DOM Spec does not allow passing the value or the specified property in this method. In this implementation they are optional.

Parameters: value The attributes value. See Attr::setValue for details. If the value is not supplied, the specified property is set to 0. specified Whether the attribute value was specified or whether the default value was used. If not supplied, its assumed to be 1.

DOMExceptions:

INVALID_CHARACTER_ERR

Raised if the name does not conform to the XML spec.

createProcessingInstruction (target, data)

Creates a ProcessingInstruction node given the specified name and data strings.

Parameters: target The target part of the processing instruction. data The data for the node.

DOMExceptions:

INVALID_CHARACTER_ERR

Raised if the target does not conform to the XML spec.

createDocumentFragment

Creates an empty DocumentFragment object.

createEntityReference (name)

Creates an EntityReference object.

Document clustering project is a data mining suite to cluster a document set. This set of tools was implemented from a series of papers: "Clustering Web Pages Semantically using Combinatorial Topology", "Data mining using granular computing", and "A fast association rule algorithm based on bitmap and granular computing".
Enhancements:
- A bug with hash table has been fixed.

Personel Document Manager (or PDM for short) is a simple easy to use document management system using platform independent programming to make it work in both worlds, Windows and Linux.

It supports archiving from scanner as well as from file, mailing, editing and printing out of the application using the computers default applications on the running system. So for example, if you choosed Gimp as your favorite program for images in your Operating System, PDM will open a document you want to edit in Gimp -> without any need for configuration.

On this page you can download the Program, access the projects forums and of cause make donations to the project.

OpenOffice::OODoc::Document is a top level component for content and layout processing.

SYNOPSIS

# get an OOo file handler
my $oofile = ooFile("myfile.odt");
# connect a content-focused document interface
my $content = ooDocument
(
file => $oofile,
member => content
);
# connect a style-focused document interface
my $styles = ooDocument
(
file => $oofile,
member => styles
);
# process any content and style element
$content->appendParagraph
(
text => "An additional paragraph",
style => "BlueStyle"
);
$styles->createStyle
(
"BlueStyle",
parent => Text body,
family => paragraph,
properties =>
{
area => text,
fo:color => rgb2oo(blue)
}
);
# commit the changes using the file handler
$oofile->save;

This module defines the top level Document class, which is a connector allowing any kind of content and presentation processing. It inherits from OODoc::XPath, OODoc::Text, OODoc::Styles and OODoc::Image.

The most usual instruction to get access to any member of a document, with the exception if the metadata (meta.xml) should be something like:

my $doc = ooDocument([options]);

This constructor, if successful, returns an object that can be used (according to its "member" option) to process styles, images and text.

This module is designed simply to create objects which include all the functionality of OODoc::Text, OODoc::Image, OODoc::Styles and OODoc::XPath (which should not be called directly by applications).

For example

my $styles = ooDocument(file => "source.odt", member => "styles");

is generally better than

my styles = ooStyles(file => "source.odt");

While OODoc::Document inherits all the methods and properties of these classes, its detailed documentation in essentially provided in the following manual pages:

OpenOffice::OODoc::Text -> text content
OpenOffice::OODoc::Styles -> style & layout
OpenOffice::OODoc::Image -> graphic objects
OpenOffice::OODoc::XPath -> common features & low-level API

For example, the appendParagraph() and createStyle() methods used in the synopsis above are respectively described in OpenOffice::OODoc::Text and OpenOffice::OODoc::Styles.
The present manual page only describes those methods (there are very few) which combine layout and content processing.