On Thursday, November 27, 2014 12:28:44 Vishesh Handa wrote: > On Wed, Nov 26, 2014 at 9:34 PM, Albert Astals Cid <aa...@kde.org> wrote: > > El Dimecres, 26 de novembre de 2014, a les 19:11:11, Vishesh Handa va > > > > > > I noticed that you ported the po extractor of Strigi to KFileMetadata. > > > However, you didn't go through review or actually discuss this change > > > anywhere, which is quite sad. > > > > > > I'm going to have to revert the commit. Could you please go through the > > > proper channels? Also, I'm not really sure if we need a po file > > extractor. > > > > > A po file doesn't seem like a common enough file format for us to be > > > indexing. In fact, I'm not sure how it would be helpful. > > > > Last i knew you index code, no? > > Not quite. > > We index the text of everything that has a mimetype which starts with > 'text/'. This also includes source code, but we do not have specialized > indexers for them. In the case of po files, I wouldn't mind indexing the > plain text content, but in this case we're extracting properties such as > TranslationAuthor, TranslationUnits, etc. These all would land up being > user visible in the list of properties users can search for such as > "artist", "author", "title", etc. > > 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. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
