<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - LibO 6: Windows 10 content indexing does not work" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130320#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - LibO 6: Windows 10 content indexing does not work" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130320">bug 130320</a> from <a class="email" href="mailto:painful8th@gmail.com" title="Michail Pappas <painful8th@gmail.com>"> Michail Pappas</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=130320#c1">comment #1</a>) > In the Windows shell, document thumbnails are being extracted and built (so > show in the Windows explorer view for Icons & Tiles) while the Search bar > returns items to the Start Menu or populates the 'See more results' At work, on the systems where my LibO version is installed, windows explorer shows thumbnails but content is not indexed for searching > A review of the system 'Indexing Options' dialog (now via the Action Center > -> Search -> Searching Winodws -> 'Advanced Search Indexer Settings') > 'Advanced Options' -> 'File Types' tab, shows the ODF formats are assigned > the filter "OpenDocument Format Filter" and radio buttons are all set to > "index properties and file contents" Same settings. > Need info to check what filter is being assigned, if not the LibreOffice > provided "OpenDocument Format Filter" look to the Windows registry for the > string that shows. (In reply to Mike Kaganski from <a href="show_bug.cgi?id=130320#c2">comment #2</a>) > I also can't confirm (testing with 6.4.0.3 on Win10 right now, searching > term "lorem" typing in Start menu, and getting ODT documents in my Documents > directory among results). However, please open a document you expect to be > found using some search term; and check if it's written using the same > language (and so its language isn't changing in the middle of the word). > Windows indexer expects that parts of documents written in different > languages be split to separate chunks; so a search term that is part-English > part-German in the document will not be found. Here's the strange thing. I tried to reproduce the issue at home, on my own Windows 10 system (x64, build 1909). The issue does *not* appear. Indexing happens instantly. Additionally, the filter name is the same, "OpenDocument Format Filter", however a newer LibO is installed at home, 6.2.7.1 (also x64). I'm not sure of how one finds the GUID of the filter. Perhaps it's 7BC0E710-5703-45BE-A29D-5D46D8B39262 ? I'll be back to work on Monday, at that time I'll report back on the filter GUID used on the problematic office installation. With any luck, a newer LibO version will solve this problem for my users.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>