[
https://issues.apache.org/jira/browse/LANG-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361698#comment-14361698
]
Fabian Lange commented on LANG-935:
-----------------------------------
I did some search on github:
https://github.com/search?utf8=%E2%9C%93&q=LookupTranslator+extension%3Ajava&type=Code&ref=advsearch&l=
the most popular usage is like this
{code}
private static final CharSequenceTranslator ESCAPE_QUERY = new LookupTranslator(
new String[][] { { "\"", "\\\"" }, { "\\",
"\\\\" }, })
{code}
And even with that edge case my implementation is faster.
> Possible performance improvement on string escape functions
> -----------------------------------------------------------
>
> Key: LANG-935
> URL: https://issues.apache.org/jira/browse/LANG-935
> Project: Commons Lang
> Issue Type: Improvement
> Components: lang.text.translate.*
> Affects Versions: 3.1
> Reporter: Peter Wall
> Priority: Minor
> Labels: performance
> Fix For: Patch Needed
>
> Attachments: tempproject1.zip
>
>
> The escape functions for HTML etc. use the same code and the same
> initialisation tables for the escape and unescape functions, and while this
> is an elegant approach it leads to a number of deficiencies:
> 1. The code is very much less efficient than it could be
> 2. A new output string is created even when no conversion is required
> 3. No mapping is provided for characters that do not have a specific
> representation (for example HTML 0x101 should become ā )
> The proposal is to use a new mapping technique to address these issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
