I have downloaded ubuntu-help xenial (100% translated) and zesty
(Untranslated: 252), merged the two, and the result was this: Not ready
171, Untranslated 83.
I checked and approved the fuzzies in Lokalize (my favourite CAT), this
doesn't take much time, and uploaded the new file to Launchpad.
All we have to do now is translate the remaining 83 messages (instead of
252!!) in Launchpad.
Hannie
Op 13-03-17 om 15:06 schreef Krzysztof T:
If anyone interested in fuzzy translations, there is a bug
https://bugs.launchpad.net/launchpad/+bug/1591941
2017-03-10 0:56 GMT+01:00 Ask Hjorth Larsen <asklar...@gmail.com
<mailto:asklar...@gmail.com>>:
2017-03-10 0:32 GMT+01:00 Gunnar Hjalmarsson <gunna...@ubuntu.com
<mailto:gunna...@ubuntu.com>>:
> On 2017-03-09 20:15, Ask Hjorth Larsen wrote:
>>
>> To elaborate, msgmerge is the mechanism by which fuzzies are
>> always(-ish) generated when source code is updated. It simply
>> fuzzy-matches all current strings against all previous strings when
>> the translations are updated from the source tree.
>
>
> Thanks for clarifying. I slowly get the picture. ;)
>
> Furthermore, I think I was wrong in my reply to Hannie: The
translations at
> the bottom of the PO files are *old* translations, which you may
make use of
> manually, but they are not really fuzzy entries. As you already
pointed out,
> Launchpad doesn't do that.
Right. For no particular reason here is some more info :)
When generating/updating po-file from source code, gettext parses the
source code to recognize translatable strings.
When this process starts, there are still 0 strings, and all
translations are effectively "obsolete" for the moment.
For each string in the source code, gettext checks whether an obsolete
(or existing) string *exactly* matches that string. If it does, that
string will appear as translated (and will be removed from obsoletes).
If it does not match exactly, it will instead do a fuzzy match, and
the string will be fuzzy. Else the string will be untranslated.
Gettext has no idea whether a particular string was "changed" or is
"new" - all it knows is if it resembles a previous string or not.
So the po-file is rebuilt from the old one, and most old translations
will (normally) be matched exactly, some will be fuzzy, and any that
were never matched will be obsolete.
A consequence of this is that if some day the programmer reintroduces
a string, it will immediately be translated again, provided it exactly
matches an obsolete. (Or it could be fuzzy if it is only similar.)
(I have not verified all of the above behaviour 100%, but it is true
enough for household purposes.)
Best regards
Ask
>
> --
> Gunnar Hjalmarsson
> https://launchpad.net/~gunnarhj <https://launchpad.net/%7Egunnarhj>
>
--
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
