I don't understand. What are you trying to do?
We track all translations of our web pages on https://www.debian.org/devel/website/stats
For german you see a list of up-to-date and outdated pages
on https://www.debian.org/devel/website/stats/de
And you can directly see which git command will show the differences,
that are not yet applied to the translation.
The differences vary greatly, sometimes it's only a typo or a link
update from http to https, but sometimes larger parts of text are
changed, added or removed. Therefore it's not easy to decide if a
translation that is a couple of git commits behind the english version
should be removed or not.
IMO there's no need that you look for outdated pages manually.
But it seems there's a minor bug the the script that generates theses statistics (stattrans.pl), because the l10n/ddtp page is not listed.
But it seems there's a minor bug the the script that generates theses >statistics (stattrans.pl), because the l10n/ddtp page is not listed.
Hello Thomas,
thanks for the reply and the details.
I know and understand the technical details behind that topic. But that
is not the point.
My apologize but it seems I wasn't clear enough.
The problem is that users (readers of the website) do get the message
that a page's translation is outdated and they should use another one.
That website is Debian. Users don't care if it is an official website, a wiki, a community project or something else. It is just "Debian". And in there perception the website is kind of "broken".
It is a matter of public relations and marketing.
It IMHO harms the project "Debian" having such pages online, no matter
how tiny the git diff is. The problem is the out of date translation
message.
One solution could be to just don't show pages out of date. In this case
you never have to show that out-dated message to users. It is that
simple.
Again: This ticket is not about technical details or problems. It is
about how the project is perceived by outsiders, potential new users and potential new contributors.
In that case, the user would see not many translated pages.
English would be the usual language.
So we could skip the whole translation effort at all.
Please contribute to translation of Debian,
and/or recrute many translators for Debian,
after that you can introduce such rules.
I could think about expand this "outdated translation" message, to
include
something like "We need people to translate this webpage into
<language>.
Please think about contributing to Debians translation effort".
of that issue.Please contribute to translation of Debian,
and/or recrute many translators for Debian,
I understand that you don't mean it that way, but this "card" is rude. Don't play this card to others.
I am also a maintainer and investing spare time and resources in projects. >Don't blame for reporting a problem.
Don't take an issue to personal. I just reported a problem with Debian. That's it. Don't feel pushed. This issue is not about that you or someone else in the team need to fix it now. This is not the point. Managing resources and schedules is not topic
But if maintainers agree with my view that my initial reported problem is a report, other contributors can catch up.
Doing the cost-benefit-calculation I still think it is better do delete or disable/hide out dated translations, until they are up 2 date again.
after that you can introduce such rules.
Do you really feel it that way?
I could think about expand this "outdated translation" message, to include >> something like "We need people to translate this webpage into <language>.
Please think about contributing to Debians translation effort".
That is IMHO not a solution to the problem I reported. No matter which message users will find, it indicates low quality. The issue is about the public view of Debian as a project.
It's as always (or at least at many points) in Debian: the main
issue is lack of manpower.
Removing the work from translators will likely not lead to
more motivation.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 489 |
Nodes: | 16 (2 / 14) |
Uptime: | 24:28:53 |
Calls: | 9,665 |
Files: | 13,716 |
Messages: | 6,168,300 |