[
https://issues.apache.org/jira/browse/JSPWIKI-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094092#comment-14094092
]
Jürgen Weber commented on JSPWIKI-762:
--------------------------------------
There are still several refences in comments:
./org/apache/wiki/xmlrpc/RPCHandler.java: // from the
TranslatorReader itself. Also, the link format should probably
./org/apache/wiki/search/SearchMatcher.java: * TranslatorReader rewrite will
presumably invalidate this, among other things.
./org/apache/wiki/plugin/Image.java:// do this cleanly, a
TranslatorReader revamp is needed.
./org/apache/wiki/plugin/AbstractReferralPlugin.java: // Make a Wiki
markup link. See TranslatorReader.
./org/apache/wiki/plugin/Denounce.java: // FIXME: Should really call
TranslatorReader
./org/apache/wiki/parser/JSPWikiMarkupParser.java: throw new
InternalWikiException("Faulty camelcasepattern in TranslatorReader");
./org/apache/wiki/parser/JSPWikiMarkupParser.java:
log.warn("TranslatorReader got a faulty page name!",e);
./org/apache/wiki/parser/JSPWikiMarkupParser.java: * where HTMLRenderer
would try and boot a TranslatorReader before
./org/apache/wiki/parser/JSPWikiMarkupParser.java: * the TranslatorReader
it is contained by is up.
./org/apache/wiki/event/PageEventFilter.java: * but not yet been sent
through the TranslatorReader. Note that you cannot
./org/apache/wiki/event/PageEventFilter.java: * do HTML translation here,
because TranslatorReader is likely to escape it.
./org/apache/wiki/event/PageEventFilter.java: * This method is called
after a page has been fed through the TranslatorReader,
> Drop TranslatorReader
> ---------------------
>
> Key: JSPWIKI-762
> URL: https://issues.apache.org/jira/browse/JSPWIKI-762
> Project: JSPWiki
> Issue Type: Task
> Components: Core & storage
> Reporter: Juan Pablo Santos Rodríguez
> Fix For: 2.9.1
>
>
> As talked in http://s.apache.org/IP1, TranslatorReader was deprecated in 2.3,
> and it isn't used in src, so it should be safe to drop it for 2.9.1
--
This message was sent by Atlassian JIRA
(v6.2#6252)