2014-11-27 18:21 GMT+02:00 Vishesh Handa <m...@vhanda.in>: > > On Thu, Nov 27, 2014 at 12:32 PM, Sebastian Kügler <se...@kde.org> wrote: >> >> > It really seems to specialized. >> >> What's wrong with specialized? Our software is used in very specialized >> environments, and often the argument to do so is one of these "fringe" >> features which we support very well. That sets us apart from the >> mainstream. >> And it's a feature. > > > I'm fine with targeting specialized cases if they are thought out. I'm not > sure if that is the case over here. > > Maybe I don't know translators workflow. Do they actually search for these > properties? Here are the ones that have been added - > > + TranslationUnitsTotal, > + TranslationUnitsWithTranslation, > + TranslationUnitsWithDraftTranslation, > + TranslationLastAuthor, > + TranslationLastUpDate, > + TranslationTemplateDate, > > It seemed to me that these properties are only specific to the Localize > application.
As a translator I don't search files by these properties, but have appreciated seeing these in Dolphin's information panel when browsing po files. To see statistics for po files in some folder in Lokalize you need to create a project for that folder (or for a folder up in the folder hierarchy). For me seeing the statistics in Dolphin is great when dealing with miscellaneous po files for which I haven't created a project. By the way: The Strigi extractor was in kdesdk-strigi-analyzers and thus had to be installed separately. Is that still a possible solution? >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
