11 Sep
2012
11 Sep
'12
9:51 p.m.
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.
* "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
12 Sep
12 Sep
10:20 a.m.
On Tue, Sep 11, 2012 at 9:51 PM, Vincent Massol <vincent(a)massol.net> 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.
* "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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
14 Sep
14 Sep
6:03 p.m.
On Wed, Sep 12, 2012 at 11:20 AM, Thomas Mortagne <thomas.mortagne(a)xwiki.com
wrote:
> On Tue, Sep 11, 2012 at 9:51 PM, Vincent Massol <vincent(a)massol.net>
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? 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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
18 Sep
18 Sep
9:46 a.m.
On Fri, Sep 14, 2012 at 7:03 PM, Eduard Moraru <enygma2002(a)gmail.com> wrote:
On Wed, Sep 12, 2012 at 11:20 AM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com
wrote:
> On Tue, Sep 11, 2012 at 9:51 PM, Vincent Massol <vincent(a)massol.net>
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.
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
*
"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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:18 p.m.
On Tue, Sep 18, 2012 at 10:46 AM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
On Fri, Sep 14, 2012 at 7:03 PM, Eduard Moraru
<enygma2002(a)gmail.com>
wrote:
left
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.
On Wed, Sep 12, 2012 at 11:20 AM, Thomas Mortagne
<
thomas.mortagne(a)xwiki.com
wrote:
> On Tue, Sep 11, 2012 at 9:51 PM, Vincent Massol <vincent(a)massol.net>
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 > 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.
Thanks,
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
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).
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
WDYT? Any idea about how to do the "mouse-over" feature? Anyone
interested by this topic?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5:22 p.m.
Hello Vincent,
I think I mentioned this already, the Pontoon JS toolset seems veeeery appropriate to me
for such a task:
https://wiki.mozilla.org/L10n:Pontoon
As I have met the maker of it when he presented that video:
http://videolectures.net/w3cworkshop2012_horvat_live_localization/
Paul
Le 11 sept. 2012 à 21:51, Vincent Massol a écrit :
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.
* "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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4381
days inactive
4388
days old
5 comments
5 participants
participants (5)
-
Eduard Moraru -
Marius Dumitru Florea -
Paul Libbrecht -
Thomas Mortagne -
Vincent Massol