Bug #3417
closedunparsed-text-lines() incorrect behaviour with blank lines
100%
Description
Tests fn-uparsed-text-lines-5[3|4]
fail due to incorrect handling of blank lines. This is for two reasons:
-
Iter.oneToOne .next()@, when provided with a @ForArray
argument, tests for an end of sequence valueitem = _base.next()
by using!item@. Unfortunately in this case, under @unparsed-text-lines()@, the input is a series of JavaScript strings, for which @!""
istrue@!. Hence the result is terminated at the first blank line. Switching the test to @item === null
seems to sort the problem -
The logic on
CoreFn.unparsed-text-lines
does not handle a blank line as the last, i.e. when the last character is a line break, for which that blank line should be ommitted from the result.
Updated by John Lumley over 7 years ago
- Fix Committed on JS Branch 1.0, Trunk added
Updated by Debbie Lockett about 7 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in JS Release set to Saxon-JS 1.0.2
Bug fix applied in Saxon-JS 1.0.2 maintenance release.
Please register to edit this issue
Also available in: Atom PDF Tracking page