Don't you also need: #@deprecated "because we stopped this application in release 1.12.2" #@deprecated "new.key.name: either this or that or that" ? I'm afraid your syntax is a bit too tiny. I'm definitely encouraging the use of deprecation in i18n messages. Is there or will there be a server to monitor the use of deprecation, and/or analyze it so that they can be removed by proper changes inside the code?? This would be very valuable! paul Le 18 janv. 2012 à 17:50, Thomas Mortagne a écrit :
Hi devs,
Right now renaming a key is a pain if we don't want to loose the existing translations associated to it. Basically it require to rename the key in all languages and reimport all of them on l10n.xwiki.org.
We already have a section in the translation file to indicate which translations are deprecated. The idea is to indicate what is the new name of a deprecated translation key directly in the translation file so that l10n.xwiki.org can automatically copy the translation to the new key when it find a new deprecated key while importing default translation file.
For that we need to decide a syntax to indicate what is the new name of the key.
I propose to do something similar to java and indicate it in a comment like the following:
new.key.name=Default translation
#@deprecated new.key.name old.key.name=Default translation
Here are some other alternatives to "deprecated":
* replacedBy * new
others ?
Here is my +1 for "deprecated", more intuitive for Java developers and it's clear it's a deprecated translation key.
Thanks, -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs