Free document editor software for linux

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.

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.

PGID3 is an ID3v1 and v2 tag editor for manipulating the information on files such as MP3s. PGID3 Tag Editor project is written in PHP and uses PHP-GTK, so it can take advantage of the GTK+ Toolkit for rendering a GUI.

The program itself is broken into three parts, a PHP Function Library called Pid Three (Pid3), a PHP CLI interface (PCLID3), and the GTK+ GUI itself. All three parts come together ready to go, so do not go freaking about uber amounts of dependencies to fill. All together they create the PGID3 Tag Editor.

"But Bob," you might say, "PHP is for the web!" Sure it is, but you should then check out the link below for the PHP Command Line Interface. That document describes using PHP to develop shell and desktop applications. Why PHP? Because I like to abuse it, that is a little hobby of mine.

Simply, PGID3 is an ID3 tag editor for MP3 files. The ID3 tags are what tell your media player the information about the tune such as title, album, etc. You can get by with slack tags if you just use a player like XMMS or Winamp, but if you have a portable like an iPod or some kind of database for the files, then correct and neat tags are a must. PGID3 can handle both the v1 and v2 of ID3 tags.

As for the program itself, it is the combonation of three seperate pieces that together work to create a user friendly envrionment to manipulate your ID3 tags. The base of it all is the Pid Three Function library, which is a fully custom set of functions for the reading and writing of ID3 tags. Since these are seperate from the application itself, the actual dirty work of messing with the data can be easily updated as well as easily included into other projects.

The second part of PGID3 is the Command Line Interface that I have lovingly called PCLID3. Using this you can manipulate your tags from the command line without using any type of graphical front end. By not having this built into the GUI, the opportunity is left open to build alternate GUIs, or even just not use any at all.

The third and final piece is the PHP-GTK GUI. This is the actual PGID3 component, though all of the parts together form a complete package under the PGID3 name. I designed this GUI to be light, compact, and solve as many problems in one spot as possible. As a bonus feature, PGID3 has built in intergration with QueryXMMS which is a command line utility for Linux that can ask XMMS what is currently playing so PGID3 can open it. This speeds up editing of playlists considerably.

Enough acronymns, what about features? Well, it is an ID3 editor so the features I would expect to find in one is what it has. It has the ability to read, write, and strip ID3v1 and ID3v2 tags from files. You can open a file from anywhere in the filesystem with a dialog, or using the above mentioned QueryXMMS integration you can zap right to whatever XMMS is playing.

If you leave the comment field blank when you write a tag, it fills it in automaticly with "Tagged by PGID3" which might be an easily disabled in future releases - depends if I get any feedback on that. It also automaticly removes excess whitespace on the end of tags which if I recall correctly happens because Winamp pads with spaces instead of nuls. Anyway it cleans that for you. Stripping a tag automaticly unchecks the related checkbox for writing it back, and the boxes are dynamicly checked as you load a file depending if it already has a v1 or v2 tag.

There are also a few keyboard shortcuts. F1 toggles the Write ID3v1 checkbox, and F2 toggles the Write ID3v2 one. F9 opens the currently playing file in XMMS, and naturally Enter writes tags.

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.

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 Copy Editor is an XML editor with DTD/XML Schema/RELAX NG validation, XSLT, XPath, pretty-printing, syntax highlighting, folding, tag completion/locking and lossless import/export of Microsoft Word documents.
Enhancements:
- This release fixes a number of bugs and introduces support for CSS.