Comment 21 for bug 1798187

The XUL client took any whitespace/newline/comma characters to be separators between barcodes.

So
28383883883, 28282828288282, 2828282828828828, 92993939939393
and
28383883883 28282828288282 2828282828828828 92993939939393
and
28383883883
     28282828288282
  2828282828828828
    92993939939393
and
28383883883
28282828288282
2828282828828828
92993939939393

all had the same result. which is why spaces inside barcodes would cause the behavior described.

So is that the wanted behavior?

Or do we want to say that each barcode must be on a separate line, and strip all whitespace?

So
38838384848484848, 282828838383 ,28288882822
would be read as one barcode.
3883838484848484828282883838328288882822
so we wouldn't support csv format.

28828 282828 8282882
200303 030303 30030
200200 200200 20020
would be
288282828288282882
20030303030330030
20020020020020020

Josh