attribute values containing '0' not correctly parsed

[adamtwo]

Line 9339 of asciidoctor.js seems to replace blanks with 0's in attributes string. Then line 93340 does the inverse using 0's to split into an array. The issue arises when attribute name or value contain 0. In such a case the code below incorrectly splits attribute name or value and inserts partial key or value in the target array.

If we have to do such an ugly hack I recommend using some more unique string than only '0' character.

Adam

attrs = attrs.$gsub($scope.REGEXP['$[]']("space_delim"), "\\10").$gsub($scope.REGEXP['$[]']("escaped_space"), "1");
          attrs = options['$[]=']("attributes", ($a = ($c = attrs.$split("0")).$inject, $a._p = (TMP_4 = function(accum, entry){var self = TMP_4._s || this, $a, k = nil, v = nil;if (accum == null) accum = nil;if (entry == null) entry = nil;

[mojavelinux]

Aha! This is happening because Opal is interpreting the null character as a
0. I have a fix I've used for other control characters. I'll apply it to
the null character as well for the upcoming 1.5.0.preview.2 release of
Asciidoctor.

I believe Opal has corrected this parse issue in master, but until the
0.6.0 release, we'll use the workaround.

[adamtwo]

Great, thanks for looking into it.

[mojavelinux]

I filed this issue as #883. I've also resolved it. Once I release preview2,
I'll update the Asciidoctor.js build, since some other changes are
necessary as well.

asciidoctor/asciidoctor#883

[mojavelinux]

Resolved upstream by asciidoctor/asciidoctor#884. This will be reflected in the 1.5.0.preview.2 build of Asciidoctor.js.

[ggrossetie]

Fix in master (upgrade to 1.5.0.preview.5)