On 11/7/06, Mark Florian <[EMAIL PROTECTED]> wrote:
Would it be ok to post a copy of the file? Otherwise, could you just paste the output of "file -i <filename>"?
I don't know what beagle does, but perhaps there should be some slack in this rule? At least for file-names, I can see this as a pretty common use (mp3-files,web-pages,....), and I see little risk by interpreting some extra characters as word-delimeters. Also, in texts and documents, words can often be combined using -. Perhaps this must be allowed based on service-type + in filenames? Would it be possible?
On Tue, 2006-11-07 at 13:38 +0000, Jamie McCracken wrote:
> please check the file in nautilus (which also uses xdgmime) to see how
> it identifies it.
Nautilus identifies the file as mimetype text/plain.
> also try opening it in gedit - if its invalid utf8 then it wont be able
> to and therefore tracker was right to ignore it.
Opening it in gedit poses no problems at all. In fact, I think it was
created in gedit...
Would it be ok to post a copy of the file? Otherwise, could you just paste the output of "file -i <filename>"?
> > The second problem is that I have a file called
> > bills_Maids_Causeway.ods. If I run a search for "bills maids causeway"
> > no results are returned. If I search for "bills_maids_causeway" then I
> > get that one result. The same effect can be seen with files
> > named-with-dashes-like-this.txt.
>
> thats deliberate - we do not treat underscores or hyphens as word breaks
> so they are effectively one word
>
> (this is important for searching source code)
>
> if there are good reasons for also breaking them up then please let me
> know (does beagle do this?)
_______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
