Objects that are coercible to numbers, such as Dates, are often more usefully
interpolated as numbers rather than as objects.

For backwards-compatibility, bisector checks the arity of the specified
function, and if the function only takes a single argument, it is wrapped with a
suitable comparator.

Fixes #1766. Unlike d3.bisector(accessor), this allows you to define a bisector
that works in reverse order.

An awkward aspect of implementing bisection on top of a comparator is that it is
often the case that the sorted array contains objects (e.g., rows from a TSV),
while the search value is a primitive value (e.g., a number). Thus, you want to
apply an accessor to the array elements but not to the search value.

The solution here is to invoke the comparator deterministically: the first
argument is always an element from the array, and the second argument is always
the search value. This lets a comparator apply an accessor to array elements but
not to search values.

Add ca-ES for localization

Fix quadtree tests that check the children of a node

Updated quadtree tests to check the `nodes` property of the node (a d3_geom_quadtreeNode) instead of treating the node as an array (which it is not) and trying to check indexes within it. e.g. `node[2]`.

Also, expose the optional zh_CN locale as d3.locale.zh_CN.

Add pt-BR for localization.

Taken into account multiple locales support, and not custom build.

Add zh-CN for localization

Chrome 33 included some sin/cos optimisations, which unfortunately broke
our assumption that sin(-x) + sin(x) = 0 for all x.  More details here:

  https://code.google.com/p/v8/issues/detail?id=3006

This fix uses:

  sin(x) = sgn(x) * sin(abs(x))

and:

  cos(x) = cos(abs(x))

where it matters, which fixes area calculations for degenerate polygons
such as:

  {"type":"Polygon",
   "coordinates":[[[-0.0002,0.0001],[0.0002,0.0001],[-0.0002,0.0001]]]}

Fixes #1753.

update copyright year

Corrects bug where currency suffix was overwritten by SI-prefix formatting.

add _site

adds composer.json closes #1674

Introduced by bfce5d5d (<= vs <).

The tests are run in a sandboxed environment, and so didn’t have access to the
same global Math whose random was being overridden.