On Thursday 02 February 2006 17:33, you wrote:
> On Thu, 2 Feb 2006 15:18:44 +0100 Danny Kukawka
>
> <[EMAIL PROTECTED]> wrote:
> > Thanks for the file. Currently there are 26 fuzzy translations left
> > in the file and I think the most of them are incorrect (they are
> > marked with '#, fuzzy') because they was only automatically merged.
> > This strings are not translated in KPowersave if they marked as fuzzy.
>
> During translation I revised all the strings that were already
> translated by previous translator and those fuzzy ones too.
> Because I had no idea what does this "fuzzy" mark mean I left
> these marks. 

The fuzzy mark is a mark from the automatically merge between existing 
language files and a updated pot file (which contains all translatable 
strings). If already existing strings in the po file are not changed in the 
pot files they are used without any changes (no mark set). But if the strings 
in the code are changed ore maybe new strings intruduced the merge tool try 
to check if there are maybe already translations. In this case this not 100% 
clear strings get the mark #fuzzy. In the most cases the translator need now 
check the strings and need only some litte changes to correct them. Btw. the 
qt/kde translation lib ignore this potential wrong strings. The mark is 
simply a help for the translator. 

One example for fuzzy string is:
#: detailed_dialog.cpp:123
#, fuzzy
msgid "kpowersave"
msgstr "Oszczędzanie energii"

The correct oen would be:
#: detailed_dialog.cpp:123
msgid "kpowersave"
msgstr "KPowersave"

--> I fixed this one ;-)

> So now it was just enough to remove them. Also I 
> made some corrections in my translations and translated that one line I
> forgot to before. Hope it's fine now.

Thanks for your help to translate KPowersave.

>
> > Thanks for your help,
>
> Thanks for this great piece of software :)

;-)

Cheers,

Danny 
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel

Reply via email to