On Tue, Sep 18, 2012 at 10:46 AM, Marius Dumitru Florea < [email protected]> wrote:
> On Fri, Sep 14, 2012 at 7:03 PM, Eduard Moraru <[email protected]> > wrote: > > On Wed, Sep 12, 2012 at 11:20 AM, Thomas Mortagne < > [email protected] > >> wrote: > > > >> On Tue, Sep 11, 2012 at 9:51 PM, Vincent Massol <[email protected]> > >> wrote: > >> > 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? > > The target is to be able to click on any translatable text (text with > a translation key) from the page and translate it. For this, as Thomas > suggested, you need to include the translation key in the HTML output > (when in "translation" mode), close to its value, so that the > JavaScript code can find it on click and use it with a translation > service. > Right. What I`ve suggested above is valid only if we want to do it the way Jenkins does it. However, I also agree that in-context/mouse-over translation is much nicer. Thanks, Eduard P.S.: The link to the JIRA plugin no longer works, but they probably removed it for some reason. > > Thanks, > Marius > > > 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 > > > > > >> > * "Translate Page: select from your username drop-down". We don't have > >> that either and it would be cool to write/bundle in XE a Translation > app to > >> let users write translations in their wiki and then to contribute them > with > >> one click to l10n.xwiki.org (we'd need to put l10n on SCM too at the > same > >> time). > >> > > >> > WDYT? Any idea about how to do the "mouse-over" feature? Anyone > >> interested by this topic? > >> > > >> > Thanks > >> > -Vincent > >> > > >> > _______________________________________________ > >> > devs mailing list > >> > [email protected] > >> > http://lists.xwiki.org/mailman/listinfo/devs > >> > >> > >> > >> -- > >> Thomas Mortagne > >> _______________________________________________ > >> devs mailing list > >> [email protected] > >> http://lists.xwiki.org/mailman/listinfo/devs > >> > > _______________________________________________ > > devs mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
