nokogiri 1.5.2-java → 1.5.3-java

data/CHANGELOG.ja.rdoc

@@ -1,3 +1,38 @@
+== 1.5.3 / 2012-06-01
+
+* Features
+
+  * Support for "prefixless" CSS selectors ~, > and + like jQuery
+    supports. #621, #623. (Thanks, David Lee!)
+  * Attempting to improve installation on homebrew 0.9 (with regards
+    to iconv). Isn't package management convenient?
+
+* Bugfixes
+
+  * Custom xpath functions with empty nodeset arguments cause a
+    segfault. #634.
+  * Nokogiri::XML::Node#css now works for XML documents with default
+    namespaces when the rule contains attribute selector without
+    namespace.
+  * Fixed marshalling bugs around how arguments are passed to (and
+    returned from) XSLT custom xpath functions. #640.
+  * Nokogiri::XML::Reader#outer_xml がJRubyで正しく動作しない #617
+  * Nokogiri::XML::Attribute が JRuby 上で　nil namespace を返す　#647
+  * Nokogiri::XML::Node#namespace= メソッドが JRuby　上で prefix
+  　が無い namespace を設定できない #648
+  * [JRuby] 1.9 モードで rake を実行するとデッドロックを引き起こす #571
+  * HTML::Document#meta_encoding does not raise exception on docs with
+    malformed content-type. #655
+  * Fixing segfault related to unsupported encodings in in-context
+    parsing on 1.8.7. #643
+  * [JRuby] Concurrency issue in XPath parsing. #682
+
+
+== 1.5.2 / 2012-03-09
+
+Repackaging of 1.5.1 with a gemspec that is compatible with older Rubies. #631, #632.
+
+
 == 1.5.1 / 2012年3月9日
 
 * 新機能

data/CHANGELOG.rdoc

@@ -1,3 +1,38 @@
+== 1.5.3 / 2012-06-01
+
+* Features
+
+  * Support for "prefixless" CSS selectors ~, > and + like jQuery
+    supports. #621, #623. (Thanks, David Lee!)
+  * Attempting to improve installation on homebrew 0.9 (with regards
+    to iconv). Isn't package management convenient?
+
+* Bugfixes
+
+  * Custom xpath functions with empty nodeset arguments cause a
+    segfault. #634.
+  * Nokogiri::XML::Node#css now works for XML documents with default
+    namespaces when the rule contains attribute selector without
+    namespace.
+  * Fixed marshalling bugs around how arguments are passed to (and
+    returned from) XSLT custom xpath functions. #640.
+  * Nokogiri::XML::Reader#outer_xml is broken in JRuby #617
+  * Nokogiri::XML::Attribute on JRuby returns a nil namespace #647
+  * Nokogiri::XML::Node#namespace= cannot set a namespace without a
+    prefix on JRuby #648
+  * [JRuby] 1.9 mode causes dead lock while running rake #571
+  * HTML::Document#meta_encoding does not raise exception on docs with
+    malformed content-type. #655
+  * Fixing segfault related to unsupported encodings in in-context
+    parsing on 1.8.7. #643
+  * [JRuby] Concurrency issue in XPath parsing. #682
+
+
+== 1.5.2 / 2012-03-09
+
+Repackaging of 1.5.1 with a gemspec that is compatible with older Rubies. #631, #632.
+
+
 == 1.5.1 / 2012-03-09
 
 * Features
@@ -422,7 +457,7 @@
   * Nokogiri::HTML.fragment will properly handle text only nodes (LH #43)
   * Nokogiri::XML::Node#before will prepend text nodes (LH #44)
   * Nokogiri::XML::Node#after will append text nodes
-  * Nokogiri::XML::Node#search automatically registers root namepsaces (LH #42)
+  * Nokogiri::XML::Node#search automatically registers root namespaces (LH #42)
   * Nokogiri::XML::NodeSet#search automatically registers namespaces
   * Nokogiri::HTML::NamedCharacters delegates to libxml2
   * Nokogiri::XML::Node#[] can take a symbol (LH #48)
@@ -542,7 +577,7 @@
 
 * Bugfixes
 
-  * Changed memory mangement from weak refs to document refs
+  * Changed memory management from weak refs to document refs
   * Plugged some memory leaks
   * Builder blocks can call methods from surrounding contexts
 

data/Manifest.txt

@@ -2,11 +2,16 @@
 .gemtest
 CHANGELOG.ja.rdoc
 CHANGELOG.rdoc
+C_CODING_STYLE.rdoc
 Manifest.txt
 README.ja.rdoc
 README.rdoc
+ROADMAP.md
 Rakefile
+STANDARD_RESPONSES.md
+Y_U_NO_GEMSPEC.md
 bin/nokogiri
+build_all
 ext/java/nokogiri/EncodingHandler.java
 ext/java/nokogiri/HtmlDocument.java
 ext/java/nokogiri/HtmlElementDescription.java
@@ -53,7 +58,6 @@ ext/java/nokogiri/internals/NokogiriXPathFunctionResolver.java
 ext/java/nokogiri/internals/NokogiriXPathVariableResolver.java
 ext/java/nokogiri/internals/NokogiriXsltErrorListener.java
 ext/java/nokogiri/internals/ParserContext.java
-ext/java/nokogiri/internals/PushInputStream.java
 ext/java/nokogiri/internals/ReaderNode.java
 ext/java/nokogiri/internals/SaveContextVisitor.java
 ext/java/nokogiri/internals/SchemaErrorHandler.java
@@ -198,7 +202,6 @@ lib/nokogiri/xslt.rb
 lib/nokogiri/xslt/stylesheet.rb
 lib/xercesImpl.jar
 lib/xsd/xmlparser/nokogiri.rb
-nokogiri_help_responses.md
 tasks/cross_compile.rb
 tasks/nokogiri.org.rb
 tasks/test.rb
@@ -228,7 +231,9 @@ test/files/staff.dtd
 test/files/staff.xml
 test/files/staff.xslt
 test/files/tlm.html
+test/files/to_be_xincluded.xml
 test/files/valid_bar.xml
+test/files/xinclude.xml
 test/helper.rb
 test/html/sax/test_parser.rb
 test/html/sax/test_parser_context.rb
@@ -256,6 +261,7 @@ test/xml/sax/test_push_parser.rb
 test/xml/test_attr.rb
 test/xml/test_attribute_decl.rb
 test/xml/test_builder.rb
+test/xml/test_c14n.rb
 test/xml/test_cdata.rb
 test/xml/test_comment.rb
 test/xml/test_document.rb
@@ -271,9 +277,9 @@ test/xml/test_namespace.rb
 test/xml/test_node.rb
 test/xml/test_node_attributes.rb
 test/xml/test_node_encoding.rb
+test/xml/test_node_inheritance.rb
 test/xml/test_node_reparenting.rb
 test/xml/test_node_set.rb
-test/xml/test_node_inheritance.rb
 test/xml/test_parse_options.rb
 test/xml/test_processing_instruction.rb
 test/xml/test_reader_encoding.rb
@@ -282,6 +288,8 @@ test/xml/test_schema.rb
 test/xml/test_syntax_error.rb
 test/xml/test_text.rb
 test/xml/test_unparented_node.rb
+test/xml/test_xinclude.rb
 test/xml/test_xpath.rb
 test/xslt/test_custom_functions.rb
 test/xslt/test_exception_handling.rb
+test_all

data/README.rdoc

@@ -91,7 +91,7 @@ encoded like the source document.
 Some documents declare one particular encoding, but use a different
 one. So, which encoding should the parser choose?
 
-Remember that data is just a stream of bytes. Only us humans add
+Remember that data is just a stream of bytes. Only we humans add
 meaning to that stream. Any particular set of bytes could be valid
 characters in multiple encodings, so detecting encoding with 100%
 accuracy is not possible. libxml2 does its best, but it can't be right

data/ROADMAP.md

@@ -0,0 +1,86 @@
+# Roadmap for 2.0
+
+## overhaul serialize/pretty printing API
+
+* https://github.com/tenderlove/nokogiri/issues/530
+  XHTML formatting can't be turned off
+
+* https://github.com/tenderlove/nokogiri/issues/415
+  XML formatting should be no formatting
+
+
+## overhaul and optimize the SAX parsing
+
+* see fairy wing throwdown - SAX parsing is wicked slow.
+
+
+## Node should not be Enumerable; and should have a better attributes API
+
+* https://github.com/tenderlove/nokogiri/issues/679
+  Mixing in Enumerable has some unintended consequences; plus we want to improve the attributes API
+
+* (closed) https://github.com/tenderlove/nokogiri/issues/666
+  Some ideas for a better attributes API?
+
+
+## improve CSS query parsing
+
+* https://github.com/tenderlove/nokogiri/issues/528
+  support `:not()` with a nontrivial argument, like `:not(div p.c)`
+
+* https://github.com/tenderlove/nokogiri/issues/451
+  chained :not pseudoselectors
+
+* better jQuery selector support:
+  * https://github.com/tenderlove/nokogiri/issues/621
+  * https://github.com/tenderlove/nokogiri/issues/342
+  * https://github.com/tenderlove/nokogiri/issues/628
+  * https://github.com/tenderlove/nokogiri/issues/652
+  * https://github.com/tenderlove/nokogiri/issues/688
+
+* https://github.com/tenderlove/nokogiri/issues/394
+  nth-of-type is wrong, and possibly other selectors as well
+
+* https://github.com/tenderlove/nokogiri/issues/309
+  incorrect query being executed
+
+* https://github.com/tenderlove/nokogiri/issues/350
+  :has is wrong?
+
+
+## DocumentFragment
+
+* there are a few tickets about searches not working properly if you
+  use or do not use the context node as part of the search.
+  - https://github.com/tenderlove/nokogiri/issues/213
+  - https://github.com/tenderlove/nokogiri/issues/370
+  - https://github.com/tenderlove/nokogiri/issues/454
+  - https://github.com/tenderlove/nokogiri/issues/572
+
+
+## Better Syntax for custom XPath function handler
+
+* https://github.com/tenderlove/nokogiri/pull/464
+
+
+## Better Syntax around Node#xpath and NodeSet#xpath
+
+* look at those methods, and use of Node#extract_params in Node#{css,search}
+  * we should standardize on a hash of options for these and other calls
+* what should NodeSet#xpath return?
+  * https://github.com/tenderlove/nokogiri/issues/656
+
+## Encoding
+
+We have a lot of issues open around encoding. How bad are things?
+Would it help if we deprecated support for Ruby 1.8.7? Somebody who
+knows encoding well should head this up.
+
+* Extract EncodingReader as a real object that can be injected
+  https://groups.google.com/forum/#!msg/nokogiri-talk/arJeAtMqvkg/tGihB-iBRSAJ
+
+
+## Reader
+
+It's fundamentally broken, in that we can't stop people from crashing
+their application if they want to use object reference unsafely.

data/{nokogiri_help_responses.md → STANDARD_RESPONSES.md}

@@ -1,4 +1,10 @@
-# not-enough-information
+# Standard Responses to Requests
+
+These responses are needed often enough that I figured, let's just
+check them in for future reference and use.
+
+
+# Not enough information to help
 
 Hello!
 
@@ -22,12 +28,13 @@ take a look at http://bit.ly/nokohelp
 
 Thank you so much!
 
-# not-a-bug
+
+# Not a bug
 
 Hello!
 
-Thanks for asking this question! Your request for help will not go
-unanswered!
+Thanks for asking this question! Your request for assistance using
+Nokogiri will not go unanswered!
 
 However, Nokogiri's Github Issues is reserved for reporting bugs or
 submitting patches. If you ask your question on the mailing list, Team

data/Y_U_NO_GEMSPEC.md

@@ -0,0 +1,155 @@
+(note: this was originally a blog post published at http://blog.flavorjon.es/2012/03/y-u-no-gemspec.html)
+
+## tl;dr
+
+1. Team Nokogiri are not 10-foot-tall code-crunching robots, so `master` is usually unstable.
+2. Unstable code can corrupt your data and crash your application, which would make everybody look bad.
+3. Therefore, the _risk_ associated with using unstable code is severe; for you _and_ for Team Nokogiri.
+4. The absence of a gemspec is a risk mitigation tactic.
+5. You can always ask for an RC release.
+
+
+## Why Isn't There a Gemspec!?
+
+OHAI! Thank you for asking this question!
+
+Team Nokogiri gets asked this pretty frequently. Just a sample from
+the historical record:
+
+* [Issue #274](https://github.com/tenderlove/nokogiri/issues/274)
+* [Issue #371](https://github.com/tenderlove/nokogiri/issues/371)
+* [A commit removing nokogiri.gemspec](https://github.com/tenderlove/nokogiri/commit/7f17a643a05ca381d65131515b54d4a3a61ca2e1#commitcomment-667477)
+* [A nokogiri-talk thread](http://groups.google.com/group/nokogiri-talk/browse_thread/thread/4706b002e492d23f)
+* [Another nokogiri-talk thread](http://groups.google.com/group/nokogiri-talk/browse_thread/thread/0b201bb80ea3eea0)
+
+Sometimes people imply that we've forgotten, or that we don't how to
+properly manage our codebase. Those people are super fun to respond
+to!
+
+We've gone back and forth a couple of times over the past few years,
+but the current policy of Team Nokogiri is to **not** provide a
+gemspec in the Github repo. This is a conscious choice, not an
+oversight.
+
+
+## But You Didn't Answer the Question!
+
+Ah, I was hoping you wouldn't notice. Well, OK, let's do this, if
+you're serious about it.
+
+I'd like to start by talking about _risk_. Specifically, the risk
+associated with using a known-unstable version of Nokogiri.
+
+
+### Risk
+
+One common way to evaluate the _risk_ of an incident is:
+
+    risk = probability x impact
+
+You can read more about this on [the internets](http://en.wikipedia.org/wiki/Risk_Matrix).
+
+The _risk_ associated with a Nokogiri bug could be loosely defined by
+answering the questions:
+
+* "How likely is it that a bug exists?" (probability)
+* "How severe will the consequences of a bug be?" (impact)
+
+
+### Probability
+
+The `master` branch should be considered unstable. Team Nokogiri are
+not 10-foot-tall code-crunching robots; we are humans. We make
+mistakes, and as a result, any arbitrary commit on `master` is likely
+to contain bugs.
+
+Just as an example, Nokogiri `master` was unstable for about five
+months between November 2011 and March 2012. It was unstable not
+because we were sloppy, or didn't care, but because the fixes were
+hard and unobvious.
+
+When we release Nokogiri, we test for memory leaks and invalid memory
+access on all kinds of platforms with many flavors of Ruby and lots of
+versions of libxml2. Because these tests are time-consuming, we don't
+run them on every commit. We run them often when preparing a release.
+
+If we're releasing Nokogiri, it means we think it's rock solid.
+
+And if we're not releasing it, it means there are probably bugs.
+
+
+### Impact
+
+Nokogiri is a gem with native extensions. This means it's not pure
+Ruby -- there's C or Java code being compiled and run, which means
+that there's always a chance that the gem will crash your application,
+or worse. Possible outcomes include:
+
+* leaking memory
+* corrupting data
+* making benign code crash (due to memory corruption)
+
+So, then, a bug in a native extension can have much worse downside
+than you might think. It's not just going to do something unexpected;
+it's possibly going to do terrible, awful things to your application
+and data.
+
+**Nobody** wants that to happen. Especially Team Nokogiri.
+
+
+### Risk, Redux
+
+So, if you accept the equation
+
+    risk = probability x impact
+
+and you believe me when I say that:
+
+* the probablility of a bug in unreleased code is high, and
+* the impact of a bug is likely to be severe,
+
+then you should easily see that the _risk_ associated with a bug in
+Nokogiri is quite high.
+
+Part of Team Nokogiri's job is to try to mitigate this risk. We have a
+number of tactics that we use to accomplish this:
+
+* we respond quickly to bug reports, particularly when they are possible memory issues
+* we review each others' commits
+* we have a thorough test suite, and we test-drive new features
+* we discuss code design and issues on a core developer mailing list
+* we use valgrind to test for memory issues (leaks and invalid
+  access) on multiple combinations of OS, libxml2 and Ruby
+* we package release candidates, and encourage devs to use them
+* **we do NOT commit a gemspec in our git repository**
+
+Yes, that's right, the absence of a gemspec is a risk mitigation
+tactic. Not only does Team Nokogiri not want to imply support for
+`master`, we want to **actively discourage** people from using
+it. Because it's not stable.
+
+
+## But I Want to Do It Anyway
+
+Another option, is to email the [nokogiri-talk
+list](http://groups.google.com/group/nokogiri-talk) and ask for a
+release candidate to be built. We're pretty accommodating if there's a
+bugfix that's a blocker for you. And if we can't release an RC, we'll
+tell you why.
+
+And in the end, nothing is stopping you from cloning the repo and
+generating a private gemspec. This is an extra step or two, but it has
+the benefit of making sure developers have thought through the costs
+and risks involved; and it tends to select for developers who know
+what they're doing.
+
+
+## In Conclusion
+
+Team Nokogiri takes stability very seriously. We want everybody who
+uses Nokogiri to have a pleasant experience. And so we want to make
+sure that you're using the best software we can make.
+
+Please keep in mind that we're trying very hard to do the right thing
+for all Nokogiri users out there in Rubyland. Nokogiri loves you very
+much, and we hope you love it back.

data/build_all

@@ -0,0 +1,58 @@
+#! /usr/bin/env bash
+#
+#  script to build gems for all relevant platforms:
+#  - MRI et al (standard gem)
+#  - windows (x86-mingw32 and x86-msin32-60)
+#  - jruby
+#
+#  prerequisite is the mingw32 packages.
+#  on ubuntu, `sudo apt-get install mingw32`
+#  for others, read up at https://github.com/luislavena/rake-compiler
+#
+
+# Load RVM into a shell session *as a function*
+if [[ -s "$HOME/.rvm/scripts/rvm" ]] ; then
+    source "$HOME/.rvm/scripts/rvm"
+elif [[ -s "/usr/local/rvm/scripts/rvm" ]] ; then
+    source "/usr/local/rvm/scripts/rvm"
+else
+    echo "ERROR: An RVM installation was not found.\n"
+fi
+
+function rvm_use {
+    current_ruby=$1
+    rvm use "${1}@nokogiri" --create
+}
+
+set -o errexit
+
+# initialize
+rvm_use 1.8.7
+rm -rf tmp pkg
+bundle exec rake clean clobber
+
+# holding pen
+rm -rf gems
+mkdir -p gems
+
+# MRI
+rvm_use 1.8.7
+bundle exec rake gem
+cp -v pkg/nokogiri*.gem gems # should only be one at this point in the script
+
+# windows
+rvm_use 1.8.7
+bundle exec rake-compiler cross-ruby VERSION=1.8.7-p330
+bundle exec rake-compiler cross-ruby VERSION=1.9.2-p136
+bundle exec rake cross
+rake gem:windows # don't use bundler here. it blows up. *shrug*
+cp -v pkg/nokogiri*x86-{mingw32,mswin32}*.gem gems
+
+# jruby
+rvm_use jruby-1.6.5
+bundle exec rake clean clobber
+rvm_use 1.8.7
+bundle exec rake generate
+rvm_use jruby-1.6.5
+bundle exec rake gem
+cp -v pkg/nokogiri*java.gem gems