Re: [xwiki-devs] [Idea] XWiki Translation Application

On Wed, Sep 12, 2012 at 11:20 AM, Thomas Mortagne &lt;thomas.mortagne(a)xwiki.com > On Tue, Sep 11, 2012 at 9:51 PM, Vincent Massol &lt;vincent(a)massol.net&gt; > > Hi devs, > > > > We've been talking about this for a long time already. We've even seen > what Jenkins does (go to http://ci.xwiki.org and click on the bottom left > link). > > > > Today I've seen an article showing a cool new plugin for JIRA to help > localize JIRA: > > http://blogs.atlassian.com/2012/09/inproduct-translation-plugin-beta/ > > > > Since XWiki allows overriding translation in wiki pages we have almost > the same features OOB as those touted on the JIRA plugin page: > > > > * "Access Management: control which groups can translate JIRA". We have > that too with wiki right management > > * "Instant updates: translations are saved automatically and appear > immediately for all users". Same for us > > • "Mouse-hover: items turn green to let you know they are translatable". > This is the cool part we're missing. It would be awesome to be able to do > this. We should brainstorm about how to be able to do that. > > Already tough about it actually and that's one of the reasons to have > translation macro actually. When you have the macro you can very easy > find all the translatable content in the page when using the annotated > xhtml renderer. > Can`t we use some trick on the $msg tool and remember each $msg.get('some.key') call that are made on a single request? If we can assign an ID to a just finished request, we could then call the $msg tool and ask for all the translation keys in that request (ID), corresponding to all the keys in the page. Something like: $msg.requestId -> String $msg.getRequestKeys($requestId) -> List<String> Of course, in the case of AJAX calls that add content from another page (and request), there would be problems with both this and the translation macro approach. Thanks, Eduard