|
Posted by EamonnøF¦¢yÝŠÇ.²È¨žÉ¢rº,¡û\¢ on May 30, 2005, 11:51 pm
Please log in for more thread options
I have an IFilter implementation that reports file properties. One of these
properties is 'keywords' for which there can be multiple values. My IFilter
returns each keyword separately so the output of filtdump looks something
like this:
----------------------------------------------------------------------
Attribute = F29F85E0-4FF9-1068-AB9108002B27B3D9
idChunk = 2
BreakType = 2 (Sentence)
Flags(chunkstate) = 0x2 (Value)
Locale = 1033 (0x409)
IdChunkSource = 2
cwcStartSource = 0
cwcLenSource = 0
----------------------------------------------------------------------
Type = 31 (0x1f): keyword1
----------------------------------------------------------------------
Attribute = F29F85E0-4FF9-1068-AB9108002B27B3D9
idChunk = 3
BreakType = 2 (Sentence)
Flags(chunkstate) = 0x2 (Value)
Locale = 1033 (0x409)
IdChunkSource = 3
cwcStartSource = 0
cwcLenSource = 0
----------------------------------------------------------------------
Type = 31 (0x1f): keyword2
This all seems to work just fine with the Windows XP indexing service. The
problem is that using MSN Desktop Search, I can search on the first keyword
reported but not subsequent values.
Looking at Adobe's PDF IFilter implementation, I see the that filtdump
returns a single keyword property with semicolon separated values:
----------------------------------------------------------------------
Attribute = F29F85E0-4FF9-1068-AB9108002B27B3D9
idChunk = 3
BreakType = 2 (Sentence)
Flags(chunkstate) = 0x2 (Value)
Locale = 1033 (0x409)
IdChunkSource = 3
cwcStartSource = 0
cwcLenSource = 0
----------------------------------------------------------------------
Type = 31 (0x1f): keyword1; keyword2
This however isn't ideal since it would not allow for exact matches on
individual keywords.
Can someone explain why MSN Desktop Search appears to be ignoring all but
the first value of multi-value properties?
eamonn
|