Hi Thomas.
Thomas Mortagne wrote:
Yes it's a dead translation issue and the answer is something like:
for now the choice has been to safest one (don't automatically delete
anything to not loose history) and no one had time to think a lot more
about how to deal with dead translations.
We should maybe remove the "Number of translations" and "Number of
dead translations" column since it does not bring any value IMO. The
important ones are "Number of Empty/outdated translations".
Note that if you absolutely want to do some cleanup, each translation
value has it's own document so you just need to delete the
corresponding page (click on the link in the "Key" column to do to the
page).
Ok, I get the point. Thanks.
Just two more doubts:
1. What is expected to get when I click the "Compare with Application
Resource" link? Must I get some kind of list of differences between
ApplicationResources.properties and the same file of any given translation?
2. Concerning dead translations. There are at least two keys in the
Galician translation that I don't understand why are not included in the
default ApplicationResources.properties
http://l10n.xwiki.org/xwiki/bin/view/XE/XEXWikiCoreResources_-1793646742_ga…
http://l10n.xwiki.org/xwiki/bin/view/XE/XEXWikiCoreResources_-899451350_slo…
As far as I understand, each resources file must contain the translation
to its language of all the other available languages, mustn't it? Thus,
each time a new language is available, a new key must be included in all
resources files. Coming back to the same example, I am not able to find
the key galician in the default ApplicationResources.properties file.
Please, am I wrong? Must this key be included in
ApplicationResources.properties?
Thanks!
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team