https://bugs.kde.org/show_bug.cgi?id=387280

Jack <ostrof...@users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ostroffjh@users.sourceforge
                   |                            |.net

--- Comment #1 from Jack <ostrof...@users.sourceforge.net> ---
Is it possible to check the timestamp of the files to compare the translation
to the original?  How do the automated tools determine whether a translation is
up to date, or am I wrong in thinking that proces is automated?

I have not looked at what other applications do, but this issue of not all
docbook files having releaseinfo the same as the released version has been the
case with KMyMoney for a long time, and I don't remember anyone complaining or
questioning it.  

In order to update those values, someone will have to carefully read each
docbook file, and determine whether or not it will need any changes to reflect
the behavior of the program in the current release (in this case 4.8.2).  If
the file does not require any changes, then it is OK to update the releaseinfo
value.  As I would prefer to spend the little time I have available to make the
5.0 documentation ready, I am not willing to spend the time on this task. 
However, if someone else determines that a docbook file does not accurately
reflect 4.8.2, then I am willing to update the file as necessary.

The 4.8.x series has a limited lifetime, and I think most of the developers,
and even the users, would prefer to get 5.0 released as soon as possible, even
if it means missing some translations for 4.8.2.

Also, even if 4.8.2 is released with incomplete translations, as translations
are completed after the release, they will be available in the online docs, and
I am willing to make a note to that effect in the introduction section of the
manual, and we could also repeat it on the main web page.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to