Bug 160648 - lokalize does not fill (recognize) correctly the stats for translation
Summary: lokalize does not fill (recognize) correctly the stats for translation
Status: RESOLVED WORKSFORME
Alias: None
Product: lokalize
Classification: Applications
Component: general (show other bugs)
Version: 0.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Nick Shaforostoff
URL:
Keywords:
: 162001 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-04-10 12:19 UTC by manolis
Modified: 2008-05-12 21:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of the empty project view (173.34 KB, image/png)
2008-04-10 12:21 UTC, manolis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description manolis 2008-04-10 12:19:27 UTC
Version:           0.2 (using 4.00.68 (KDE 4.0.68 >= 20080402), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.22-gentoo-r8

I use a local svn copy for templates , messages for my team...

I entered the po/template local dir in project settings... 
I entered "trunk" in my project settings

I get the following empty screen in my project view...
There are no stats, like lokalize does not analyse the files...
Comment 1 manolis 2008-04-10 12:21:07 UTC
Created attachment 24286 [details]
screenshot of the empty project view
Comment 2 Nick Shaforostoff 2008-04-10 16:01:30 UTC
did you install po strigi-analyzer?

it is located in http://websvn.kde.org/trunk/KDE/kdesdk/strigi-analyzer/

also, if you installed strigi from pre-compiled packages and compiled kdesdk from SVN, copy strigila_po.so (from your build dir) to /usr/lib/strigi
Comment 3 manolis 2008-04-10 16:58:28 UTC
Yes, the second is right.
I installed strigi from my distro , so there was no strigila_po.so on /usr/lib/strigi
I copied it and now it works fine.
Comment 4 manolis 2008-04-10 17:14:21 UTC
closing as illegal bug report. 
Comment 5 Nick Shaforostoff 2008-05-12 21:14:31 UTC
*** Bug 162001 has been marked as a duplicate of this bug. ***