[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    introducing a new fuzzy in BRANCH?
From:       "Stefan Winter" <mail () stefan-winter ! de>
Date:       2004-04-18 11:53:10
Message-ID: 001301c4253b$b97ea740$0802a8c0 () WorkGroup
[Download RAW message or body]

Hello!

the German team received a bug report about a translation that caused
problems. Namely, in KRegExpEditor, when selecting a range of characters the
input fields are labelled "From:" "To:". The "To:" is translated via
i18n("To:"). Problem is that (at least for German translation, "To:" has to
be translated differently, according to the context. For example a "To:" in
an email would be "An:", but in the KRegExpEditor it would be "Bis:". The
developers already fixed the bug in HEAD by using i18n("end of range","To:")
so that the "To:" is not taken from the libs (where it would become "An:")
but presented as a new string for translators. They did not fix it in the
BRANCH, probably because it would generate a fuzzy. I have CVS access and it
is a one-liner, but I am not sure if fixing in the BRANCH is advisable since
it would generate that fuzzy not only for the German team but for 50+ other
language teams.
So I wonder... is this a problem for other teams as well? Is it worth fixing
in the BRANCH? I īd do it if I get a green light from this list, since this
is where coolo pointed me to. For reference, the bug report for the German
team is at http://bugs.kde.org/show_bug.cgi?id=76727 and was taken to the
kregexpeditor developers http://bugs.kde.org/show_bug.cgi?id=79332 . The
patch is described in the latter link.
Please cc me on comments.

Greetings,

Stefan Winter

[prev in list] [next in list] [prev in thread] [next in thread]