Created attachment 117308 [details] Translation Units Hi all, since Lokalize has been updated to 18.12 I notice the strange behaviour I write in title; referring to my screenshot I'm talking about messages 635 and 637 in the "Unità di traduzione", the others are 1-row only. If I open them they are ok, as you can see. STEPS TO REPRODUCE 1. Open Lokalize and choose a .po file with some message longer than a row; 2. Look at "Translation Units". OBSERVED RESULT It seems it want to display a "preview" of the message instead of its beginning. EXPECTED RESULT It would be better to have only the first words of a long message. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53 Qt Version: 5.12.0
Git commit 61d1d9a0df16ac5d82afa867cd7b00f8da263a44 by Simon Depiets. Committed on 05/02/2019 at 10:36. Pushed by sdepiets into branch 'master'. Only display the first line of messages in the catalog M +4 -4 src/catalog/catalog.cpp M +2 -2 src/catalog/catalog.h M +2 -2 src/catalog/catalogstorage.h M +34 -6 src/catalog/gettext/gettextstorage.cpp M +2 -2 src/catalog/gettext/gettextstorage.h M +19 -5 src/catalog/ts/tsstorage.cpp M +2 -2 src/catalog/ts/tsstorage.h M +18 -4 src/catalog/xliff/xliffstorage.cpp M +2 -2 src/catalog/xliff/xliffstorage.h M +3 -3 src/cataloglistview/catalogmodel.cpp https://commits.kde.org/lokalize/61d1d9a0df16ac5d82afa867cd7b00f8da263a44
Git commit d9ceed7f6ed42f49ee042a1132ab0f7efbf061da by Simon Depiets. Committed on 05/02/2019 at 10:40. Pushed by sdepiets into branch 'Applications/18.12'. Only display the first line of messages in the catalog M +4 -4 src/catalog/catalog.cpp M +2 -2 src/catalog/catalog.h M +2 -2 src/catalog/catalogstorage.h M +34 -6 src/catalog/gettext/gettextstorage.cpp M +2 -2 src/catalog/gettext/gettextstorage.h M +19 -5 src/catalog/ts/tsstorage.cpp M +2 -2 src/catalog/ts/tsstorage.h M +18 -4 src/catalog/xliff/xliffstorage.cpp M +2 -2 src/catalog/xliff/xliffstorage.h M +3 -3 src/cataloglistview/catalogmodel.cpp https://commits.kde.org/lokalize/d9ceed7f6ed42f49ee042a1132ab0f7efbf061da
*** Bug 404170 has been marked as a duplicate of this bug. ***