Cart
[Home] [By Thread] [By Date] [Recent Entries]
Hi Ken,
In your case, you undoubtedly had context phrases in the text that required special treatment. Unlike indexing a full text as you were attempting, I am indexing a much smaller universe: the words that appear on Czech stamps and their translations into English. Also, I am not going to pay attention to case, number, or any other part of speech [I donbt have to unite references to the same word in different forms, nor collect specific ideas]. I am constructing a simple word list - indexing may be too strong a term for the end product. I was a professional indexer years ago, and was head of research and development for a firm that wrote software for public, university, and school libraries, so I have a very sound command of those parts of indexing and information theory: its my XPath and XSLT that are so very, very weak :-) When I abstracted out the words from my XML file for indexing, I also collected ( constructed, actually) the links and link names, so that part is all taken care of. Let me absorb what you have given me and see where it takes me. Thanks for showing me how deal with the tokenize() output. I'll let you know how it turns out. Regards, Mark -----Original Message----- From: G. Ken Holman Sent: Sunday, October 30, 2011 3:07 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: Using XSLT to build an index At 2011-10-30 14:47 -0700, Mark wrote: The list archives did not seem to contain an XSLT stylesheet that could index an XML file, but I may have missed it. Is it practical to write my own XSLT 2 indexing stylesheet? If so, I have a bilingual XML file that I want to index.
My assumptions are that I must get rid of the punctuation properly, then isolate the words, sort them, remove stop words, and so on. To get started, I need a bit of help. All of the phrases are found in two attributes: @czech and @eng.
translate($inValue,'-,#.$%',' ') ... where the first argument is your input, the second starts with a "-" and then you put anything else in there as characters to remove, the third indicates the hyphen becomes a space and the rest are to be removed. (2) I assume that to get rid of extra spaces (if any), I can use a construct like: normalize-space(replace(@czech, C"b,K some regex expressionC"b,b")). That will reduce all sequences of white-space characters to a single space. (3) I assume that tokenize(normalize-space(replace(@czech, 'some regex expression'))) will permit me to write out a list of the words found in those attributes to an XML document. I am not completely clear as to what tokenize() returns, or how to access that return. tokenize() returns a sequence. But the input is only a single string. Actually, you want to turn the expression inside-out to get a list of words from the entire document then something along these lines should work: distinct-values( (//@czech)/tokenize(translate(normalize-space(.),'-,$%.#',' ')) ) That gives you a sequence of unique words. Can you work from that in order to do the hyperlinking, or do you need help there as well? Remember you will have to do the same translation when creating your links, so perhaps you should have a user function: mark:words(.) as tokenize(translate(normalize-space($arg),'-,$%.#',' ')) ... then use: (//@czech)/mark:words(.) ... then when creating your links you'll have the function available to ensure the same tokenizing is done at the point in time. I hope this helps. . . . . . . . . . . Ken
|
