Den Friday 06 July 2007 15:34:14 skrev Karl Eichwalder:

Martin Schlander writes:

...

Many files in lcn have strange revision dates and translators - like "Novell Language, 2002". Is it safe to assume that our previous translations are intact in such files, so we can focus on "untranslated" and "fuzzy" or do we need to proofread the entire files to be safe?

I assume that's somehow related to https://bugzilla.novell.com/show_bug.cgi?id=275898 . It was necessary to revert the SVN tree to a sane state. If you have a copy that you know to be fine, pelase submit it.

Submit? In an email to you? or commit to svn? the good copy I have from this april is >2000 strings smaller than the most recent bad one.

Maybe, you must convert the .po to the new format; in this case use 50-tools/kde3_desktop_convert.pl .

Problems here also.. the script uses msgcat.. can't seem to find a package that provides that. (webpin is down as I write.. it's almost impossible to get by without it ;-) And there's a small error in the usage-help in the script, it says: # Use: # msgcat --no-wrap in.po | perl kde3_convert_desktop.pl | msgcat - -o out.po However the script is actually called: kde3_desktop_convert.pl --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Den Sunday 08 July 2007 16:51:25 skrev Ain Vagula:

msgcat is in gettext-devel

Thanks. Now converted. Awaiting info where to submit. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Den Monday 09 July 2007 10:04:15 skrev Karl Eichwalder:

Yes, please submit it directly to the SVN. Then we (coolo/me) will run the usually merge procedures hoping those will honor the good strings.

Done.

I've the gut feeling, that our Danish memory file is somehow tainted, too. Will you please glance through 50-memory/memory.da.po? If it contains bad desktop file translations, I can remove them altogether from the memory file.

Your gut was correct. Memory.da.po has old and bad desktop file translations. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Martin Schlander writes:

When this stuff is used: - Are the strings always marked "fuzzy", so intelligent human translators can easily find them and check them?

No, we use them unconditionally. Yes, that's inherently dangerous. I already thought about this issue. I wanted I can set the whole memory of a language as fuzzy; thus translations coming out of a memory would be marked as fuzzy.

- Is it only applied to untranslated/fuzzy strings or can stuff from the memory.xx.po replace existing translations?

Theoretically, replacing translation is possible, but we never do it

- Is there an easy way of telling whether a *.po has been "affected"? For example by the revision date being strangely old?

No such check is implemented at the moment. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Am Sat 14 Jul 2007 07:17:45 PM CEST schrieb Martin Schlander :

Den Monday 09 July 2007 17:31:55 skrev Karl Eichwalder:

...

No, we use them unconditionally. Yes, that's inherently dangerous. I already thought about this issue. I wanted I can set the whole memory ^If of a language as fuzzy; thus translations coming out of a memory would be marked as fuzzy.

Please do for da (set entire memory fuzzy).

Because I must also check my scripts, applying this change will take a bit longer. There is also one drawback: From time to time we move a considerable amount of messages from one (yast) file to the other. In those case, re-using existing translations is save and I do not want to force the translator to sort out the fuzzies again. If a language is 100% translated, I could remove the fuzzies once the messages are transfered. Or I could use the old file as a mini memory file for the new file. I will probably do the latter--but this means, yast developers must inform me when they relocate messages. That's probably not a big issue, because they already do this very carefully most of the time :-) Cheers, Karl --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Den Monday 09 July 2007 17:27:16 skrev Karl Eichwalder:

I just removed the desktop file translations from the memory. I hope, I got it right.

Didn't check all strings of course, but my sample searches looked correct. Of course now we have a lot more untranslated stings in desktop-po.. good, I was beginning to worry we didn't have much work to do ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org