Created attachment 59942 [details] This document contains text "abc". It can't be found by search engine by content. 2012/04/13 This query: why libreoffice does not search by content Produces 235,000 hits. For reference pls see: http://en.libreofficeforum.org/node/1141 http://ask.libreoffice.org/question/1814/why-libre-does-not-provide-a-search-by-content This is a problem of coordination between Linux and Open/LibreOffice. I would like to propose to Linux that any new document formats generated by OpenOffice, LibreOffice, WhateverFutureOffice will come with a plugin that gets called by Linux search program. For example Ubuntu has a program called "search for files". The program will not find by content documents like .odt .ott .docx. That is because these documents use nested files format. It should be required for any new word processor with new data format to provide a plugin which would be hookable (I don't mean se-x) into the search engine. Yes, I did find some scripts that can look inside the .odt but those scripts are unusable when you have 100,000 documents. (I do have that many.) Suggestions: While this could be very complex problem if you want to search XML files by tags, I am advocating simple solution that will satisfy most users. The .odt and .docx and others contain a collection of zipped files one of them contains the data called content.xml. I would like you to unzip the .odt/.ott/.docx (etc) into temp dir, then search content.xml and report that f1.odt if f1.odt contains the content we are looking for. This should be integrated with Linux search GUI so that I can click on the link to the file. If you can isolate in content.xml the section that contains the user data, that would be great. Alternately, If you treat the whole content.xml as the user data, you will get some false hits but I am willing to live with that until you write something that looks only at the user's data inside content.xml. But the current situation is so unacceptable that in the last year I started to use .doc format on my Ubuntu because I can then find my files. -- sad story. Thank you for listening. Attachment: This document contains text "abc". It will not be found by search engine by content on Ubuntu/Gnome using Ubuntu search engine.
Hello jim8899, *, I think, it is not our bug, but a bug from the GNOME search. With KDE 4.8.4 under Debian Testing x86 and LO Version 3.6.2.2 (Build ID: da8c1e6), I can use dolphin (with nepomuk in the background) to search for the string "abc in my test files and it finds the string in your file. And I think, this should be a feature request, not a bug, if it is LO's fault and not the one from the GNOME search ... ;) HTH Thomas.
(In reply to comment #1) > Hello jim8899, *, > I think, it is not our bug, but a bug from the GNOME search. With KDE 4.8.4 > under Debian Testing x86 and LO Version 3.6.2.2 (Build ID: da8c1e6), I can > use dolphin (with nepomuk in the background) to search for the string "abc > in my test files and it finds the string in your file. And I think, this > should be a feature request, not a bug, if it is LO's fault and not the one > from the GNOME search ... ;) @jim8899: Could you comment, please?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO