Wrong keyname extraction from konversation.kcfg

Bug #530103 reported by Yuri Chornoivan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Translations
Fix Released
Medium
Unassigned
konversation (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: konversation

Parsing of konversation.kcfg by Ubuntu scripts (10.04 and 9.10) is wrong.

Code (src/config/konversation.kcfg, git):

    <entry key="TreeSplitterSizes" type="IntList">
      <default></default>
      <label></label>
      <whatsthis></whatsthis>
    </entry>

"TreeSplitterSizes" should not be extracted, but it does (message 1089, 10.04). Such a mistakes lead to more than 140 extra "messages" in LP translation over upstream translation (1699 vs. 1556).

Tags: i18n l10n
Revision history for this message
David Planella (dpm) wrote :

Yurchor,

Thanks for opening the bug. On second thoughts, after having seen the fix for bug 529483, perhaps this is indeed related, so Konversation might need a binary rebuild with the new pkg-kde-tools package.

Changed in ubuntu-translations:
status: New → Triaged
importance: Undecided → High
Revision history for this message
David Planella (dpm) wrote :

yurchor,

bug 529483 has now been fixed, but I think now it is not related. I cannot quite understand the problem, could you perhaps expand a bit more on this?

I see that https://translations.launchpad.net/ubuntu/lucid/+source/konversation/+pots/konversation/uk/+translate?batch=10&show=all&search=TreeSplitterSizes shows the "TreeSplitterSizes" string, but that's the only thing I can see. You are talking of some 140 additional messages from the Ubuntu in comparison with upstream. Could you point us to one of these messages, so that we can compare the Launchpad template with the upstream one?

The scripts used to generate the konversation templates should, if I'm not mistaken, the same ones used upstream.

Changed in ubuntu-translations:
importance: High → Medium
status: Triaged → Incomplete
Revision history for this message
Yuri Chornoivan (yurchor-gmail) wrote :

In reply on comment #2:

Yes, it is not fixed. :(

If we talk about extra messages, detecting them using Ukrainian translation is not easy now. Shame on me (those magical green bars etc. ;) ). I just copy-pasted original key fields from original. In fact, almost all "Newly translated in Launchpad" (except 1 or 2) messages in Ukrainian translation are "translated" this way. So the list of these messages can be obtained by filtering LP download by "Only strings that differ from imported versions". As a maintainer of upstream version I can guarantee that upstream was 100%-translated before meeting LP.

In upstream messages in LP block that starts from #1089 to #1242 (https://translations.launchpad.net/ubuntu/lucid/+source/konversation/+pots/konversation/uk/+translate?start=1088 ) are not extracted (and imho there is no reason to translate things that are invisible to the user). These messages can also be detected by the strange camel case.

David Planella (dpm)
Changed in ubuntu-translations:
status: Incomplete → Triaged
Jonathan Riddell (jr)
Changed in konversation (Ubuntu):
status: New → Fix Released
Changed in ubuntu-translations:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.