Free producing documents software for linux

Print OpenOffice 2 documents is a service menu that enables the user to right click on an OpenOffice 2 document and print it.

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.

Auto Save Document is an extension used to store the currently shown document in a separate directory automatically.

Autosave is a small extension, which can be used to store the currently shown document in a seperate directory automatically when browsing a certain site. You may configure the sites, where all pages will be stored to cache, by adding them to a list. The documents are stored as html-text only (no embedded objects like pictures etc.)

The files are cyclic reused, e.g. if you set the cache size to 100, Autosave will store the document contents to X:/MyCache/Autosave_0.html ... AutoSave_100.html and start again with AutoSave_0.htm when the 101st page is browsed. A small Icon in the statusbar will change its colour each time to indicate a page was written.

If you click this small icon, the current page will be dumped, regardless if the site is in the autosave list or not.

NOTE: this extension is really, really simple! Only plain text is saved, no external .css,.js => the result may look ugly! The one and only intention for this extension is, to save the text for external parsing or similar! Look for Scrapbook etc. in case you want to store more than the plain text!

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.

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

Document Library is a Web application for document management in larger organizations with a lot of documents.
Organizations deal with numerous documents, such as word processor documents and PDFs. These documents often reside on someones computer and are not network accessible. Versions of documents are hard to track - the same document may be passed around using email in multiple versions over time. In large organizations it therefore becomes important to structure the flow of documents and present them in a common format. This is typically done using a document management system. Document Library is one such document management system.
Information in the Document Library can be accessed using the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), meaning that besides being open source, the Document Library is also a good example of an open data application. Because it is open data, the Document Library is easier to integrate with other applications, such as the Silva CMS or any other application capable of OAI-PMH harvesting.
Main features:
- Automatic conversion service: using OpenOffice, the Document Library can convert Word documents into PDFs and plain text, PDFs into plain text. The plain text version is important in that it allows for full-text indexing of document contents, and also makes documents more accessible to people with disabilities.
- Publication workflow: documents only become available for harvesting and download after a review process.
- Delegation of control: reviewers ("librarians") can be assigned to particular sections.
- Dynamic access: authors have automatic access to all the documents that list them as an author.
- Versions: multiple versions of the same document can coexist, one public and one under preparation.
- Email reminder functionality: users receive emails of the progress of the document through the workflow.
- OAI-PMH data provider: allows other systems to harvest document metadata using standard protocol.
- Integration with Silva CMS (using OAI-PMH).
- Fast upload and download integration with Apache using Tramline.
- Easy overview screens for librarians.
- Smart file upload user interface: files need to be uploaded only once even if rest of form needs to be amended.
- Document Library is built using the powerful Zope 3 application server platform.
Enhancements:
- Installation was made easier by using zc.buildout.
- Optional LDAP support was added.
- Filesystem storage was integrated with Tramline.
- The conversion provided by OooConv was improved.
- Table rendering was improved using zc.table.
- Zope was updated to 3.3.

SDMS is an open-source system that allows you to store any document in a database via a bunch of webpages.

That was the short description, now comes the long one. SDMS uses PHP to provide you with a pretty interface to a MySQL server that allows you to store and retrieve documents and to share those documents between users.

In addition, the system uses ACL (Access Control Lists) to grant access rights to documents on a per-user basis.

So what is all this good for? Well, it for instance allows you to distribute project documentation on a need-to-know basis, whilst keeping a central repository of documents that is accessible to all team members and easy to manage.