REXML - Credits

# Credits

#### 2.3.6

I've had help from a number of resources; if I haven't listed you here, it means that I just haven't gotten around to adding you, or that I'm a dork and have forgotten. In either case, feel free to write me and complain. I may ignore you, but at least you tried. (Actually, I don't conciously ignore anybody except spammers.)

- Mike Stok has been very active, sending not only fixes for bugs (especially in Functions), but also by providing unit tests and making sure REXML runs under Ruby 1.7.
- Kouhei Sutou translated the REXML API documentation to Japanese! Links are in the API docs section of the main documentation.
- Erik Terpstra heard my pleas and submitted several logos for REXML. After sagely avoiding choosing one for several weeks, I finally forced my poor slave of a wife to pick one (this is what we call "delegation"). She did, with caveats; Erik quickly made the changes, and the result is what you now see at the top of this page. He also supplied a smaller version that you can include with your projects that use REXML, if you'd like.
- Ernest Ellingson contributed the sourcecode for turning UTF16 and UNILE encodings into UTF8, which allowed REXML to get the 100% OASIS valid tests rating.
- Ian Macdonald provided me with a comprehensive, well written RPM spec file.
- Oliver M . Bolzer is maintaining a Debian package distribution of REXML. He also has provided good feedback and bug reports about namespace support.
- Michael Granger supplied a patch for REXML that make the unit tests pass under Ruby 1.7.
- James Britt contributed code that makes using Document.parse_stream easier to use by allowing it to be passed either a Source, File, or String.
- Tobias Reif: Numerous bug reports, and suggestions for improvement.
- Stefan Scholl, who provided a lot of feedback and bug reports while I was trying to get ISO-8859-1 support working.
- Steven E Lumos for volunteering information about XPath particulars.
- Fumitoshi UKAI provided some bug fixes for CData metacharacter quoting.
- TAKAHASHI Masayoshi, for information on UTF
- Robert Feldt: Bug reports and suggestions/recommendations about improving REXML. Testing is one of the most important aspects of software development.
- Electric XML: This was, after all, the inspiration for REXML. Originally, I was just going to do a straight port, and although REXML doesn't in any way, shape or form resemble Electric XML, still the basic framework and philosophy was inspired by E-XML. And I still use E-XML in my Java projects.
- NQXML: While I may complain about the NQXML API, I wrote a few applications using it that wouldn't have been written otherwise, and it was very useful to me. It also encouraged me to write REXML. Never complain about free software *slap*.
- See my technologies page for a more comprehensive list of computer technologies that I depend on for my day-to-day work.
- rdoc, an excellent JavaDoc analog12.
- Many, many other people who've submitted bug reports, suggestions, and positive feedback. You're all co-developers!

12) When I was first working on REXML, rdoc wasn't, IMO, very good, so I wrote API2XML. API2XML was good enough for a while, and then there was a flurry of work on rdoc, and it quickly surpassed API2XML in features. Since I was never really interested in maintaining a JavaDoc analog, I stopped support of API2XML, and am now recommending that people use rdoc.