Statistics Help

Introduction

The KDE messages statistics application use is straighforward at first glance. But exploiting full potential of information require aditional info for reading numbers and interpreting colors in status tables.

Applications / Documentations

KDE Localization process is separated in two main trees : Applications and Documentations translations. Generally translators consider that the most important process is the applications translation, because it's first thing the user see when he launches his KDE program, and the localization helps him understand each elements of the application. However, the Documentation process is very important too, because it helps users to understand specifical points of KDE programs in their own locale.

Generally, Applications are better translated than Documentation, because they are easier to translate. For example Documentation contains big blocks of text which need severals reading and translating iterations before considering as ready while applications generally are made of little strings, easier to translate and verify. Unfortunately those two processes are important, so do not hesitate to help your KDE translation teams, there are a lot of jobs left !

Stable / Trunk

The Applications and Documentations files are available from KDE Subversion Repository. The Stable and Trunk represents in fact the same files, but applied to different targets.

The stable branch reflects the current translation status of your language in the current version of KDE (or in the next maintenance release, for example: KDE 3.5.2), these pages help you to see if all files are ready to be distributed with KDE packages, or in your favorite distribution. Look at these statistics when KDE is about to release a new version, because in good days, non-translated string must not be present in your language.

The trunk branch, though, represents the status of the development version of KDE (example: KDE 4.0). It allows you to see if projects have modified a lot their localization files, and if you need to translate some of them. Look at these pages if you just want to see the current status of localization in KDE, or if you want to find a PO file which needs a lot of work to be fully translated.

Browsing between levels

The all statistical pages are organized by levels. There are 4. The top level page is that with welcome message and which list KDE braches for which statistics are generated. The second level pages are the ones for each processed branch. In the "top" (or index) page you can see the panel which list branch names and date and time when last statistics update occured. Click on the branch name and voila: you're on the second level statistics page. Here you'll find totals for every KDE translation team. Click on any team name and you will jump to third level status page. This page contain totals for KDE packages regarding selected branch and team name. At this point you have listed on left side the KDE translation teams to navigate easy between 3-rd level statistics without using back and forward browsers buttons. This way you can see easy how your concurent teams perform on various KDE packages. Next to the 4 level: click on desired KDE package name to view message catalogs statistic. At this point you're on the last level. Any click on PO or POT filename start downloading the respective file from KDE CVS via webcvs interface.

The browsing can be made in two ways: by team and by package. When is made by team then content is structured like top/branch/teamcode/package/. When is made by package then content is structured like top/branch/package/teamcode/.

What colors and numbers means

Applications and Documentations Statistics

There are two categories where colors are used: on graphical bars and on texts from tables (as background and/or foreground).

Team	Translated	%	Fuzzy	%	Untranslated	%	Total	Graph
kdeaddons	n/a	n/a	n/a	n/a	n/a	n/a	n/a

The magenta bar (which is always full) mean that there's no package directory made for the translation team. This can be seen on level 2 and 3 statistic pages. When you click on package name, then is shown a level 4 page which explain that there's no translation for respective package.

Team	Translated	%	Fuzzy	%	Untranslated	%	Total	Graph
kappfinder.po	7	46.67	3	20.00	5	33.33	15

The above bar can be seen on any level pages when statistics data are available. First item is the name of translation team, KDE package or PO/POT filename.

Team	Translated	%	Fuzzy	%	Untranslated	%	Total	Graph
kfind.po	73	100.00	0	0.00	0	0.00	73

You can observe the light blue background in the above bar. This can happen when you have PO file which don't have coresponding POT file. This indicate that you should delete from CVS the message catalog file.

Team	Translated	%	Fuzzy	%	Untranslated	%	Total	Graph
kpresenter.po	7	46.67	3	20.00	5	33.33	15

Documentation Statistics

The above bar can be seen on any level pages when statistics data are available. First item is the name of translation team, KDE package or PO/POT filename.

Team	Translated	%	Fuzzy	%	Untranslated	%	Total	Graph	Status
kfind.po	73	100.00	0	0.00	0	0.00	73

You can observe the light blue background in the above bar. This can happen when you have PO file which don't have coresponding POT file. This indicate that you should delete from CVS the message catalog file.

Team	Translated	%	Fuzzy	%	Untranslated	%	Total	Graph	Status
kpresenter.po	7	46.67	3	20.00	5	33.33	15

When a PO file is not correct, then it is marked with red and the red marker is shown on higher levels: packages page, then teams page.

Every status table (which have a graphic bars) have the following columns: PO/POT filename or KDE package name, translated messages, translated messages percentage, fuzzy messages, fuzzy messages percentage, untranslated messages, untranslated messages percentage, total number messages in PO file / KDE package and graphic bar. The percentage columns have darken background color to be easily spoted.

Types of statistics

Level 2 pages show statistics for all translating teams:

• Info by team: list totals for translation teams
• Info by package: list totals by KDE package
• Full info page: a table which have teams as rows and KDE packages as columns; the percentages are hyperlinks
• Top List: a table which show ordered list with first 10 translating teams by number of translated messages; fuzzy and untranslated messages are not considered
• Essential: a table similar with that "info by team", but which display only statistics for PO files and KDE packages that must be translated prior to a team be included in next KDE release; the completeness percentage levels that must be meet are on this page. The "completeness" column show if a team meet distribution requirements (when background is deep green and number is 100%).
• Partial: list only files which have no translation (i.e. only POT file) and are partialy translated. Teams which have almost complete translation, will be very pleased to focus only on these files.
• General Info: lots of general statistics are show here. Some are usefull just to know how big KDE is. Another ones can tell if something goes wrong not only with statistics, but even with KDE CVS or team translations.

DocBook files status

In the last column in the tables on the level 1, 2, and 3 the DocBook files translation status is displayed as an icon. For level 1 and 2, status represent the overall package or team status and can be in one of the states:

• - the all package or team DocBook files are translated and up-to-date regarding coresponding PO files.
• - some of DocBook files in package or team need translation or to be regenerated.

If you need the in-detail at the DocBook XML files, descend on the level 3 and look for the one of the following states:

• - (no icon) nothing to tell about DocBook file because it doesn't exists. You need to fully translate at least once the PO file and generate the XML file.
• - DocBook file is up to date, being regenerated after the PO file was fully translated. This is where we want to arrive.
• - The PO file is not finished. You need to fully translate it and then (re)generate the DocBook XML file.
• - The associated PO file is fully translated, but the DocBook file contents doesn't reflect the actual PO source file. You need to regenerate the DocBook XML file from the PO file. In the square parens you can read how old is DocBook file than the PO file.
• - Nothing relevant can be told about PO and associated DocBook file because either one CVS date info cannot be obtained. Some form of filesystem or CVS corruption occured. If this state persist for more than few days, please contact the DOC Stats maintainer.

History Graphs

To view how much a team work on translating essential files and essential packages, every team statistics page (level 2 with sorting by team) have a bottom graph. That way, KDE release and internationalization coordinators can decide if a team translations will be included in upcomming release judging by activity.

Graph can be view enlarged if you click on them and you may have a more accurate view for calendaristic dates and number of translated messages.

Values on the Y-axis represent number of translated messages counting from previous day. Note that when messages from POT templates are merged with PO's is very likely that will appear fuzzy entries. This will reduce the number of translated messages and will show up in next day graphs as negative values.

On the "Essential" pages is displayed the graph which sumarize messages translated for all the teams and for essential files and packages.