Parchment

Parchment is a simple, flexible library for interacting with word processing document files. Initially intended for outputting .docx and .odt files as HTML fragments, it is built to be flexible for future use.

You may ask, is there really a need for another document parsing library? Apparently so.

I had a seemingly simple task I wanted to do: Take a Microsoft Word or Open Office Writer file and display it as an HTML fragment within a larger page, with as much formatting as necessary. I couldn't find a decent solution for this, especially from within a Rails app. Most other libraries are focused on converting whole documents, such as a Word file into a complete fully-compliant HTML page.

I wanted the simplicity of what is seen under usage below, without patching together several different command-line tools. That's Parchment.

Add this line to your application's Gemfile:

gem 'parchment'

And then execute:

$ bundle

Or install it yourself as:

$ gem install parchment

require 'parchment'
doc = Parchment.read('path/to/file.odt')
doc.to_html

1. Fork it ( https://github.com/apetlock/parchment/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

I love TDD/BDD, but not to an insane level. Any tests written should test input and output. Did the file get read properly? Is it outputting properly? Internals do not need to be tested. For example, testing if a paragraph is aligned_right? is necessary. Making sure that the class stores the alignment as String 'right' is not.