Closed GoogleCodeExporter closed 9 years ago
The issue was actually in us using the \u internally to represent special
characters and mistranslating that. So the stream got around fine but the
hardcoded string was translated as & instead of as \u0026 so replace didn't
work...
This should be fixed now, instead of using \u we are using ~~u as a shorthand
internally which should see less conflict.
Original comment by shai.almog
on 31 Jan 2015 at 10:58
Original issue reported on code.google.com by
timun....@mattioli-woods.com
on 29 Jan 2015 at 11:10