Page 1 of 1

Fuzzy translation messages?

PostPosted: Tue Feb 17, 2009 5:13 pm
by kimmov
I just started wondering how should we handle messages having that fuzzy comment?

I think I've just messed this up now. As the fuzzy is inside comment, I've just been merging PO files with filter that ignored lines beginning with # char. So I've practically ignored additions/removals of fuzzy comments. So probably there are many messages in some translations marked as fuzzy even though they really should not be.

Should we just remove all fuzzy comments? At least in 2.12 branch?

And how to avoid this in future? Having better filter that doesn't ignore lines with word fuzzy?

Re: Fuzzy translation messages?

PostPosted: Wed Feb 18, 2009 2:30 pm
by gerundt
I think fuzzy comments are important informations for translators! There are also some other important comments for translators, that should sync in Trunk and Branch.

Currently support PO(T) files 4 types of comments:

  • # translator-comments
    Comments from translator to other translators
  • #. extracted-comments
    Comments from developer to translator
  • #: reference...
    Reference where are the string is used
  • #, flag...
    Flags like fuzzy, c-format, ...

Here are a real-life example from a extracted comment (#.):

French.po wrote:#. Zoom to normal
#: Merge.rc:397
#, c-format
msgid "&Normal\tCtrl+*"
msgstr "&Normal\tCtrl+*"


In Poedit will the translator see, that "Normal" means in this case "Zoom to normal", which can be a important information.

Only the reference (#:) is not important to sync between Trunk and Branch, since the line numbers anyway not fit. ;)

So I would suggest ^#: as line filter for WinMerge...

Re: Fuzzy translation messages?

PostPosted: Wed Feb 18, 2009 3:12 pm
by kimmov
gerundt wrote:I think fuzzy comments are important informations for translators!

What is the information it gives? That the string has changed?

I think we have changed 5 or 6 strings after 2.10.x. And most of those were removing one space. We simply should not change existing strings without a very good reason. I'd even say we should in future change the string ID if we change it. So that it simply is not possible to miss change in string.

gerundt wrote:So I would suggest ^#: as line filter for WinMerge...

Thanks, I'll update my filter.

Re: Fuzzy translation messages?

PostPosted: Wed Feb 18, 2009 3:50 pm
by gerundt
kimmov wrote:What is the information it gives? That the string has changed?


Fuzzy means something like "I don't know if the translation is perfect or correct, but it is better then nothing!" for a translator. :mrgreen:

So it is more or less a TODO flag for the translator...