Go to file

Yorick Peterse 3ff9057858 Renamed the XPath axes_spec file.		2014-06-13 09:32:46 +02:00
benchmark	Simple benchmarks for the XPath lexer.	2014-06-13 00:49:24 +02:00
checksum	Basic project layout.	2014-02-26 19:50:16 +01:00
doc	Basic project layout.	2014-02-26 19:50:16 +01:00
ext	Removed the on_newline XML lexer callback.	2014-05-29 14:21:48 +02:00
lib	Support for parsing basic XPath expressions.	2014-06-12 00:20:46 +02:00
profile	Namespaced the profile directories.	2014-06-13 00:33:53 +02:00
spec	Renamed the XPath axes_spec file.	2014-06-13 09:32:46 +02:00
task	Basic XPath parser setup.	2014-06-01 23:02:28 +02:00
.editorconfig	Updated editor configuration.	2014-05-08 00:17:12 +02:00
.gitignore	Namespaced the profile directories.	2014-06-13 00:33:53 +02:00
.ruby-version	Added a .ruby-version file.	2014-03-18 18:08:25 +01:00
.travis.yml	Travis: don't notify for every failure.	2014-05-08 10:20:35 +02:00
.yardopts	Basic project layout.	2014-02-26 19:50:16 +01:00
CONTRIBUTING.md	Added a contributing guide.	2014-05-09 00:32:44 +02:00
Gemfile	Basic project layout.	2014-02-26 19:50:16 +01:00
LICENSE	Added a license.	2014-02-26 22:20:47 +01:00
README.md	Removed outdated paragraph from the README.	2014-05-09 00:34:25 +02:00
Rakefile	Basic XPath parser setup.	2014-06-01 23:02:28 +02:00
oga.gemspec	Upgrade to RSpec 3.0.	2014-06-02 12:09:38 +02:00

README.md

Oga

Oga is an XML/HTML parser written in Ruby. Oga aims to provide an easy to use and high performance API for all your XML/HTML parsing needs. Oga requires nothing other than Ruby, it does not depend on libxml and the likes.

To achieve high performance Oga uses a C or Java extension depending on your Ruby platform. Pure Ruby is sadly not fast enough to process large amounts of text in reasonable time.

From Wikipedia:

Oga: A large two-person saw used for ripping large boards in the days before power saws. One person stood on a raised platform, with the board below him, and the other person stood underneath them.

Features

Support for parsing XML and HTML(5)
- DOM parsing
- Stream/pull parsing
High performance and low memory usage (depending on the parsing API)
Support for XPath 1.0 (planned)
CSS selectors support (planned)

Requirements

Oga runs on MRI 1.9.3 or newer, Rubinius 2.2 or newer and JRuby 1.7 or newer. Ruby 1.8.7 is not supported. Maglev, Topaz and mruby are currently not supported.

To install Oga on MRI or Rubinius you'll need to have a working compiler such as gcc or clang. Oga's C extension can be compiled with any capable C compiler.

Native Extension Setup

The native extensions can be found in ext/ and are divided into a C and Java extension. These extensions are only used for the XML lexer built using Ragel. The grammar for this lexer is shared between C and Java and can be found in ext/ragel/base_lexer.rl.

The extensions delegate most of their work back to Ruby code. As a result of this maintenance of this codebase is much easier. If one wants to change the grammar they only have to do so in one place and they don't have to worry about C and/or Java specific details.

For more details on calling Ruby methods from Ragel see the source documentation in ext/ragel/base_lexer.rl.

Why Another HTML/XML parser?

Currently there are a few existing parser out there, the most famous one being Nokogiri. Another parser that's becoming more popular these days is Ox. Ruby's standard library also comes with REXML.

The sad truth is that these existing libraries are problematic in their own ways. Nokogiri for example is extremely unstable on Rubinius. On MRI it works because of the non conccurent nature of MRI, on JRuby it works because it's implemented as Java. Nokogiri also uses libxml2 which is a massive beast of a library, is not thread-safe and problematic to install on certain platforms (apparently). I don't want to compile libxml2 every time I install Nokogiri either.

To give an example about the issues with Nokogiri on Rubinius (or any other Ruby implementation that is not MRI or JRuby), take a look at these issues:

Some of these have been fixed, some have not. The core problem remains: Nokogiri acts in a way that there can be a large number of places where it might break due to throwing around void pointers and what not and expecting that things magically work. Note that I have nothing against the people running these projects, I just heavily, heavily dislike the resulting codebase one has to deal with today.

Ox looks very promising but it lacks a rather crucial feature: parsing HTML (without using a SAX API). It's also again a C extension making debugging more of a pain (at least for me).

I just want an HTML parser that I can rely on stability wise and that is written in Ruby so I can actually debug it. In theory it should also make it easier for other Ruby developers to contribute.

License

All source code in this repository is licensed under the MIT license unless specified otherwise. A copy of this license can be found in the file "LICENSE" in the root directory of this repository.