Gary,
I'm not sure how I would present this as a patch - it affects a number
of different methods of the StringEscapeUtils class. I have created a
JIRA item [LANG-935] https://issues.apache.org/jira/browse/LANG-935 and
I have attached a zip file with source code for my alternative
implementa
tial lengt. That does not look like a efficient
implementation to the problem to me. Not sure where I have seen the
functions which handle that, maybe in one of the xml parsers.
BTW: maybe also the input should be a CharSequence not a String?
Greetings
Bernd
Am 10.12.2013, 05:14 Uhr, schrieb Peter Wall
ge of entity names) and URI percent encoding, and I have versions
that handle UTF-16 surrogate codes. They all perform approxiamtely an
order of magnitude better than the existing Apache Commons functons.
They are currently under LGPL and I have JUnit tests
