[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#465347: marked as done (Too many messages are marked fuzzy in apt-0.7.10)

Your message dated Tue, 12 Feb 2008 07:15:47 +0100
with message-id <20080212061547.GH17031@mykerinos.kheops.frmug.org>
and subject line Re: Bug#465347: Too many messages are marked fuzzy in apt-0.7.10
has caused the Debian Bug report #465347,
regarding Too many messages are marked fuzzy in apt-0.7.10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
465347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465347
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.7.10
Severity: normal

In apt-0.7.* series many .po messages are marked as fuzzy. Such messages
are not loaded by gettext libraries, and instead only English versions of
messages are used. This results in visual package tools (like synaptic
and update-manager) displaying inconsistent messages - partially translated
and partially in English.

Example:

#: apt-pkg/depcache.cc:172 apt-pkg/depcache.cc:191 apt-pkg/depcache.cc:195
#, fuzzy
msgid "Reading state information"

This status text is visible after many routine package-related activities
(installing, upgrading, etc.)


In fact, running the following command in the /po directory of the apt
source tree gives me this:

for f in apt-0.7.10/po/*.po; do echo -n "${f}  "; grep fuzzy ${f} | wc -l; done
apt-0.7.10/po/ar.po  22
apt-0.7.10/po/bg.po  31
apt-0.7.10/po/bs.po  29
apt-0.7.10/po/ca.po  31
apt-0.7.10/po/cs.po  31
apt-0.7.10/po/cy.po  139
apt-0.7.10/po/da.po  17
apt-0.7.10/po/de.po  31
apt-0.7.10/po/dz.po  31
apt-0.7.10/po/el.po  40
apt-0.7.10/po/en_GB.po  30
apt-0.7.10/po/es.po  17
apt-0.7.10/po/eu.po  14
apt-0.7.10/po/fi.po  30
apt-0.7.10/po/fr.po  2
apt-0.7.10/po/gl.po  13
apt-0.7.10/po/he.po  19
apt-0.7.10/po/hu.po  27
apt-0.7.10/po/it.po  30
apt-0.7.10/po/ja.po  2
apt-0.7.10/po/km.po  31
apt-0.7.10/po/ko.po  13
apt-0.7.10/po/ku.po  51
apt-0.7.10/po/mr.po  50
apt-0.7.10/po/nb.po  8
apt-0.7.10/po/ne.po  33
apt-0.7.10/po/nl.po  31
apt-0.7.10/po/nn.po  58
apt-0.7.10/po/pl.po  36
apt-0.7.10/po/pt_BR.po  30
apt-0.7.10/po/pt.po  28
apt-0.7.10/po/ro.po  31
apt-0.7.10/po/ru.po  30
apt-0.7.10/po/sk.po  30
apt-0.7.10/po/sl.po  58
apt-0.7.10/po/sv.po  13
apt-0.7.10/po/th.po  14
apt-0.7.10/po/tl.po  30
apt-0.7.10/po/uk.po  59
apt-0.7.10/po/vi.po  2
apt-0.7.10/po/zh_CN.po  2
apt-0.7.10/po/zh_TW.po  30

In previous versions (apt-0.6.*) there was no such a big problem. However,
in apt-0.7.* many new strings were introduced, and their contents were
created automatically as fuzzy. I believe the translation teams should
be given a remainder and opportunity to translate the new .po files.

--- End Message ---
--- Begin Message --- 
Version: 0.7.10

Quoting Wiktor Wandachowicz (siryes@gmail.com):
> Package: apt
> Version: 0.7.10
> Severity: normal
> 
> In apt-0.7.* series many .po messages are marked as fuzzy. Such messages
> are not loaded by gettext libraries, and instead only English versions of
> messages are used. This results in visual package tools (like synaptic
> and update-manager) displaying inconsistent messages - partially translated
> and partially in English.

Sure, that's what gettext is about.


> 
> In previous versions (apt-0.6.*) there was no such a big problem. However,
> in apt-0.7.* many new strings were introduced, and their contents were
> created automatically as fuzzy. I believe the translation teams should
> be given a remainder and opportunity to translate the new .po files.


That are constantly "reminded" about this. See
http://d-i.alioth.debian.org/l10n-stats/ (apt is part of "level 5"
there).

However, during the development of new versions, strings change often
and some translators prefer big updates to small, regular
updates. Mileage may vary.

There *will* be a string freeze on APT, probably as soon as lenny's
base system freeze will start. At that time, translators will have the
opportunity to fight against a non-moving target.

Please also note that the changed strings are *often* rarely used
ones. During 0.6->0.7 development, though, some important ones were
changed. Which may explain the behaviour you see.

Finally, also note that many programs used APT strings *and* their own
strings (aptitude, synaptic, etc.). So, the localization result is mor
ecomplicated to achive that only completing a single PO file.



As I don't think that translation completeness is a bug per se, I
therefore close this bug.

PS: as your own name sounds Polish (please forgive me if I'm wrong),
I'd very welcome an update to the Polish translation. It has 30 fuzzy
and 6 untranslated strings out of 536 strings. And this, even if is
hasn't been updated for quite a long time....so that makes the claim
of "incomplete" translations pretty relative...

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: