Mailinglist Archive: opensuse-translation (119 mails)

< Previous Next >
Re: [opensuse-translation] Towards 11.0 (yast)
  • From: Karl Eichwalder <ke@xxxxxxx>
  • Date: Wed, 26 Mar 2008 13:22:50 +0100
  • Message-id: <shiqz965et.fsf@xxxxxxxxxxxxxxx>
wadim dziedzic <wdziedzic@xxxxxxxxx> writes:

How long will this review take?

It ends today and may start or continue later in April.

Does it mean that we will get some fuzzies when results will come back
to repository?

Yes, fuzzies are to be expected.

English proofreading will probably have little impact on translations,
so would it be possible then to merge its results differently? I mean in
the other direction - merge the reviewed msgids to .po files. The normal
merge + translation memory makes the translation work harder, because
some good translations are usually lost or old ones from memory creep
in. Of course the changed items should be marked as fuzzy, but we would
be sure that the translations are "original".

Unfortunately, this is not possible. msgmerge does not know whether a
message is new or just changed up to some degree. In the near future we
a probably able to carry over the old translation somehow; this way, PO
file editors could display diffs easily (I think this already works
somehow in kbabel). Old translation:

msgid "apple"
msgstr "jablko"

Now consider a newly introduced string such as "apples":

#, fuzzy
#| apple
msgid "apples"
msgstr "jablko"

I'm not sure about the final getext syntax, though.

I know there's no tool for such a merge, but maybe half day work of one
person would save some translators' time ;-)

Yes, that's a valid concern. Maybe, later this year ;-( Cheers,

Karl Eichwalder
R&D / Documentation

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-translation+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups