rescuing argument error on split so cucumber won't stop tests due bad encoding
Support embedding images directly in html files
Prefer encoding included in mime-type when embedding images direcly
Pass output from step definitions on to gherkin formatters
Embedding in the json-formatter works, no need for @wip-jruby
Add default task for I18n fr examples
Remove warning should to expect for I18n fr examples
Fix error backtrace for the JSON formatter output

@wip-new-core removed for three scenarios in the json_formatter.feature
The step backtrace in not only needed for the print_exception method in
StepInvocation, but also for the before_step_result/after_step_result
methods. Therefore add the step backtrace line when the StepInvocation
is created.
A DocString object cannot be raised as en exception in JRuby
Make the modified backtrace not leak to @exception

The modification of the backtrace in filtered_step_exception should not
affect the backtrace of @exception.
Merge pull request #704 from brasmusson/json-formatter-error-backtrace

wip-new-core: Fix error backtrace for the JSON formatter output
Collect result along with the nodes

Inline the print_step_container conditionals to expose the ugly!
Add seed to random.

Hopefully should fix those flickering tests.
New OpenStruct syntax no worky on older Rubys

cc @tooky
Fix handling of embed for the JSON formatter

The legacy_formatter need to make sure that the embed calls from the
step definitions are not passed to the formatter until it got
information about the corresponding step.
Add @spawn to the scenario: embedding screenshot

If the scenario is not @spawn:ed the scenario: "
features/docs/gherkin/background.feature:346 #
Scenario: run a feature with a background that is pending"
fails in the JRuby build on Travis (due to that a full error backtrace
is emitted, so it seems that the -b flag is carried over somehow).
Pass output from step definitions on to gherkin formatters

The legacy_formatter need also to make sure that the puts calls from
the step definitions are not passed to the formatter until it got
information about the corresponding step.
The JSON formatter does not work with scenario outlines in v2.0
Handle that scenario outline steps do not contain result
Rename method