The dutch translation is complete with no fuzzy translations at all (which
doesn't mean that it's 100% correct off course). I ALWAYS check the fuzzy
translations and change them if they are wrong, which sometimes occur if
some new strings trigger these fuzzy translations.
I have no problem with either keeping or abandoning the fuzzy translations.

Hoi,
Harry

2010/3/17 Carl von Einem <[email protected]>

> Hi!
>
> Ademar de Souza Reis Jr. schrieb am 17.03.10 00:25:
> >
> > Pablo was discussing with me in PVT the possibility of disabling fuzzy
> > translations on hugin. The reason is that at least in some languages,
> > there are several fuzzy translations which don't make sense at all.
> >
> > A few examples:
> >
> >  * It has been reported that "Author" is being marked as "Automatic" in
> Chinese;
>
> This example might be a clever default since a lot of manuals for
> Chinese products that hit the German market seem to be translated by
> robots ;-)
>
> >  * In pt_BR I see *tons* of mistranslations. One example is "All
> > images at once" being translated to something like "Add image:
> > cancel". :-(
>
> If it's true what Vaclav wrote ("fuzzy matches are actualy not used in
> the GUI, their English counterparts are used instead") I have no problem
> with the way it works now.
>
> These observations about "fuzzy translations" should be documented in
> the wiki, so new translators can make an informed decision about that
> kind of messages.
> Is this ok?
> <
> http://wiki.panotools.org/wiki/index.php?title=Hugin_translation_guide&diff=12215&oldid=12214
> >
>
> > I was believing that one of the reasons why this is happening was that
> > all messages from xrc files are first extracted to a global xrc file
> > before the translation happens. But after cooking a patch to improve
> > this I still see all errors there (tests and ideas and patches are
> > welcome - see the code inside src/translations/ - but I'm afraid the
> > solution would not be so simple).
> >
> > So at least as the pt_BR maintainer, I would like to disable fuzzy
> > mode altoghether... What do other translators think about it?
> >
> > Disabling fuzzy has its cost, as a lot of strings would be marked as
> > untranslated. See below the current statistics:
> > (...)
> > de.po: 1060 translated messages, 28 fuzzy translations, 11
> > untranslated messages.
>
> Comparing the above numbers for de.po with the ones Bruno provided I
> think Bruno's numbers are more accurate. But I better have a look myself
> at the file... :-)
>
> OK, the current de.po (Rev. 4946) tells me: 99% out of 1091 messages
> translated, 1 message needs to be translated. I see no fuzzy messages.
> I will upload the new po file. Done.
>
>
> BTW I found a comment about a possible typo in line 4830 ("Calculate
> crop borders such that the final images has the largest area without
> excess"):
> Possible typo in EN version: "the final images has" - this is only one
> image, right?
>
> Carl
>
> --
> You received this message because you are subscribed to the Google Groups
> "hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<hugin-ptx%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to