Page 1 of 1

mdimport for debugging

PostPosted: Mon Sep 07, 2015 2:58 am
by sportsnapper
Hi,

I think you should add to the pinned troublshooting post the use of mdimport to aid understanding of what exactly is in the pdf file that you're working on. I spend some time searching the forum for this command - as I'd used it before but couldn't remember exactly what I'd used (and searching for something you don't knwo the name of is always fun :-) ).

Code: Select all
mdimport -d2 [i]filename[/i]
and looking at the kMDItemTextContent filed really helped me fix some rules that weren't working.

Re: mdimport for debugging

PostPosted: Tue Sep 08, 2015 11:21 am
by Mr_Noodle
Actually, an easier way to do this (for those who don't want to use the commandline) is to open the file in Preview, select all the text and paste it into a plain text document in TextEdit. I'm not sure if the results are identical but it's easier to deal with and should help with content matching.