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

List:       kde-bugs-dist
Subject:    [Bug 99013] New: Multiline strings are not changed in database
From:       Hasso Tepper <hasso () linux ! ee>
Date:       2005-02-10 10:41:29
Message-ID: 20050210114123.99013.hasso () linux ! ee
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=99013         
           Summary: Multiline strings are not changed in database
                    automatically
           Product: kbabel
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: visnovsky kde org
        ReportedBy: hasso linux ee


Version:           1.10 (using KDE 3.3.92 (beta2), compiled sources)
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-7)
OS:                Linux (i686) release 2.6.10

I expect strings added/updated in database when I change translation ("Auto add entry \
to database" checked in database settings). It seems that it works with small strings \
(menu commands for example), but not with large multiline strings (documentation).

I work with automatic search enabled. Choose some tiny transaltion to change, I made \
test with kdegames/kmines.po. I added just one letter to the translation - the \
correct transaltion is "Ruudu suurus.", I made it "Ruudu suurust.". New translation \
is added database - ie. if I move to the next enrty in the file and back to the this \
one, I see already new translation in the search result. Just for case performed \
search with dictionary application - yes, new translation is there already.

But the same scenario doesn't work with large documentation strings, seems. At least \
it's the only difference I see between strings which transaltions are updated and \
which not.

It seems to be related with #42192. Automatic database update works already and it \
have been working for ages AFAIR. But it seems to have bug I didn't notice earlier, \
translating documentation is quite new for me.


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