Eric, Tom Bradford is the one working on the full text indexer. You will have to check with him to see what his time-frame is for delivery. As far as the "contains", it is part of the XPath Query. Try:
http://www.zvon.org/xxl/XPathTutorial/General/examples.html for a good introduction to XPath Queries. Also, check out the W3C XPath definition. My code is designed around attribute searching, not text. Maybe someone has a sample, I don't know what is available in the docs. HTH, Mark Unknown wrote: > Mark, > Thanks for the reply. Would you know when the 'full text indexer' will be > implimented? And, would you have any sample code for doing an XPath query with > 'Contains'? > Thanks again, > Eric > > "Mark J. Stang" wrote: > > > Eric, > > Xindice would work, but the current version might be a bit slow. There > > are plans for a full text indexer. However, currently, you would have to > > do an "XPath" query using "contains". That will search, the entire > > document. Probably not as fast as you would like. Once the > > full text indexer comes out, then it should work fine. It depends on > > your time frame. > > > > Xindice is well suited to returning individual Chapters and all the > > other items, if you break it up into the right set of documents and > > collections. I haven't used FrameMakers' xml so, I don't know > > how it stores the documents. > > > > HTH, > > > > Mark > > > > Eric Thoman wrote: > > > > > Hi, > > > > > > I'm looking at Xindice to store literary documents that will be created > > > with FrameMaker 7. > > > > > > The user will enter keywords to search the entire text of the all of the > > > xml documents and return individual Chapters with their titles, the book > > > titles and the contents of the chapters. > > > > > > How well might Xindice work against a 4000 page literary work? And, can > > > anyone > > > suggest a good approach? Sample code is always neat:) > > > > > > Last, if anyone has any comments about FrameMakers' xml ability vis-a-vis > > > Xindice > > > I would be most appreciative. > > > > > > Thanks, > > > Eric Thoman
