5 Jul
2011
5 Jul
'11
10:16 p.m.
Hello XWiki developers,
In Curriki, we have about 4000 translation keys... and we're sure there are parts we
could deprecate somehow so as to get rid of them one day.
They are mostly used in XWiki, a little in JavaScript.
Has there been any effort done in this direction?
Would it be possible for example to flag the phrases of one page as being deprecated so
that it outputs a warning if used which one would collect later?
Or... would it be possible to move away already a page of phrases and load it on demand
for some legacy pages?
thanks for ideas
paul
6 Jul
6 Jul
11:06 a.m.
On Tue, Jul 5, 2011 at 22:16, Paul Libbrecht <paul(a)hoplahup.net> wrote:
Hello XWiki developers,
In Curriki, we have about 4000 translation keys... and we're sure there are parts we
could deprecate somehow so as to get rid of them one day.
They are mostly used in XWiki, a little in JavaScript.
Has there been any effort done in this direction?
Would it be possible for example to flag the phrases of one page as being deprecated so
that it outputs a warning if used which one would collect later?
Or... would it be possible to move away already a page of phrases and load it on demand
for some legacy pages?
Nothing is implemented on XWiki platform yet but some standard as been
applied to the translation resource already and part of it is used by
l10n.xwiki.org already.
If you look at
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
you will find 2 kind of deprecated sections one with actually useless
translations keys for the current dev branch (we are supposed to
removed the unsupported branches but that has been forgotten a bit in
the latest releases) and another one with more technical keys not
directly used by the current dev branch but that should still be kept
because we feel that them are used by other applications.
The second section is seen by l10n as dead translations. I need to add
"deprecated" keys in l10n (exported but not displayed in the
translation UI) and then add second for the first section to make
translators life easier.
If should not be too hard to add support for theses sections in the
new translation component and print warning when theses kind of
translation keys are used.
thanks for ideas
paul
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
3:17 p.m.
On Wed, Jul 6, 2011 at 11:06 AM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
On Tue, Jul 5, 2011 at 22:16, Paul Libbrecht
<paul(a)hoplahup.net> wrote:
Could also be done easily in an aspect for the old msg.get tool (if we
say a section as a prefix for example)
Jerome
Hello XWiki developers,
In Curriki, we have about 4000 translation keys... and we're sure there are parts we
could deprecate somehow so as to get rid of them one day.
They are mostly used in XWiki, a little in JavaScript.
Has there been any effort done in this direction?
Would it be possible for example to flag the phrases of one page as being deprecated so
that it outputs a warning if used which one would collect later?
Or... would it be possible to move away already a page of phrases and load it on demand
for some legacy pages?
Nothing is implemented on XWiki platform yet but some standard as been
applied to the translation resource already and part of it is used by
l10n.xwiki.org already.
If you look at
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
you will find 2 kind of deprecated sections one with actually useless
translations keys for the current dev branch (we are supposed to
removed the unsupported branches but that has been forgotten a bit in
the latest releases) and another one with more technical keys not
directly used by the current dev branch but that should still be kept
because we feel that them are used by other applications.
The second section is seen by l10n as dead translations. I need to add
"deprecated" keys in l10n (exported but not displayed in the
translation UI) and then add second for the first section to make
translators life easier.
If should not be too hard to add support for theses sections in the
new translation component and print warning when theses kind of
translation keys are used.
thanks for ideas
paul
_______________________________________________
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
3:30 p.m.
Le 6 juil. 2011 à 15:17, Jerome Velociter a écrit :
Injecting is what an aspect does right?
Whatever the method, a clean separate logging channel is needed I think.
paul
If should not
be too hard to add support for theses sections in the
new translation component and print warning when theses kind of
translation keys are used.
Could also be done easily in an aspect for the old msg.get tool (if we
say a section as a prefix for example)
4821
days inactive
4822
days old
3 comments
3 participants
participants (3)
-
Jerome Velociter -
Paul Libbrecht -
Thomas Mortagne