Hi, Erik, Thanks for your info.
No, I haven't tried it yet. I will give it a try and maybe produce some Chinese/English text search demo online. Currently I used Lucene as the indexing engine for Velocity mailing list search. I have a demo at www.jhsystems.net. It is yet another mailing list search for Velocity, but I combined date as well as full text search together. I only used lucene for indexing the textual content, and combined database search with lucene search in returning the results. The other interesting thought I have is: maybe it is possible to use Lucene's merge segments mechanism to write a java based simple file system. Which of course, does not require constant compact operation. The file system could be based on one file only, where segments are just part of the big file. It might be really efficient in terms of adding/deleting the objects all the time. Lastly, any comments welcome for www.jhsystems.net Velocity search. Thanks, Jian www.jhsystems.net On 5/31/05, Erik Hatcher <[EMAIL PROTECTED]> wrote: > Jian - have you tried Lucene's StandardAnalyzer with Chinese? It > will keep English as-is (removing stop words, lowercasing, and such) > and separate CJK characters into separate tokens also. > > Erik > > > On May 31, 2005, at 5:49 PM, jian chen wrote: > > > Hi, > > > > Interesting topic. I thought about this as well. I wanted to index > > Chinese text with English, i.e., I want to treat the English text > > inside Chinese text as English tokens rather than Chinese text tokens. > > > > Right now I think maybe I have to write a special analyzer that takes > > the text input, and detect if the character is an ASCII char, if it > > is, assembly them together and make it as a token, if not, then, make > > it as a Chinese word token. > > > > So, bottom line is, just one analyzer for all the text and do the > > if/else statement inside the analyzer. > > > > I would like to learn more thoughts about this! > > > > Thanks, > > > > Jian > > > > On 5/31/05, Tansley, Robert <[EMAIL PROTECTED]> wrote: > > > >> Hi all, > >> > >> The DSpace (www.dspace.org) currently uses Lucene to index metadata > >> (Dublin Core standard) and extracted full-text content of documents > >> stored in it. Now the system is being used globally, it needs to > >> support multi-language indexing. > >> > >> I've looked through the mailing list archives etc. and it seems it's > >> easy to plug in analyzers for different languages. > >> > >> What if we're trying to index multiple languages in the same > >> site? Is > >> it best to have: > >> > >> 1/ one index for all languages > >> 2/ one index for all languages, with an extra language field so > >> searches > >> can be constrained to a particular language > >> 3/ separate indices for each language? > >> > >> I don't fully understand the consequences in terms of performance for > >> 1/, but I can see that false hits could turn up where one word > >> appears > >> in different languages (stemming could increase the changes of this). > >> Also some languages' analyzers are quite dramatically different (e.g. > >> the Chinese one which just treats every character as a separate > >> token/word). > >> > >> On the other hand, if people are searching for proper nouns in > >> metadata > >> (e.g. "DSpace") it may be advantageous to search all languages at > >> once. > >> > >> > >> I'm also not sure of the storage and performance consequences of 2/. > >> > >> Approach 3/ seems like it might be the most complex from an > >> implementation/code point of view. > >> > >> Does anyone have any thoughts or recommendations on this? > >> > >> Many thanks, > >> > >> Robert Tansley / Digital Media Systems Programme / HP Labs > >> http://www.hpl.hp.com/personal/Robert_Tansley/ > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
