RE: [Lucene.Net] VOTE: .NET 2.0 Framework Support After Apache Lucene.Net 2.9.4

2011-05-10 Thread Daniele Fusi
+1, go for .NET 4...
Thanks

-Original Message-
From: Troy Howard [mailto:thowar...@gmail.com]
Sent: 09 May 2011 21:05
To: lucene-net-dev@lucene.apache.org; lucene-net-u...@lucene.apache.org
Subject: [Lucene.Net] VOTE: .NET 2.0 Framework Support After Apache Lucene.Net 
2.9.4

All,

Please cast your votes regarding the topic of .Net Framework support.

The question on the table is:

Should Apache Lucene.Net 2.9.4 be the last release which supports the .Net 2.0 
Framework?

Some options are:

[+1] - Yes, move forward to the latest .Net Framework version, and drop support 
for 2.0 completely. New features and performance are more important than 
backwards compatibility.
[0] - Yes, focus on the latest .Net Framework, but also include patches and/or 
preprocessor directives and conditional compilation blocks to include support 
for 2.0 when needed. New features, performance, and backwards compatibility are 
all equally important and it's worth the additional complexity and coding work 
to meet all of those goals.
[-1] No, .Net Framework 2.0 should remain our target platform. Backwards 
compatibility is more important than new features and performance.


This vote is not limited to the Apache Lucene.Net IPMC. All 
users/contributors/committers/mailing list lurkers are welcome to cast their 
votes with an equal weight. This has been cross posted to both the dev and user 
mailing lists.

Thanks,
Troy



RE: Indexing the multiple words at the same position

2010-08-06 Thread Daniele Fusi
Hi, it also depends on the complexity of your critical apparatus, but you
could just use a custom analyzer which injects synonyms (here variants) of
your tokens in THE SAME POSITION as the original word. This way a search
will match both daddy and happy.

-Original Message-
From: Jeroen Lauwers [mailto:jeroen.lauw...@ctlo.net] 
Sent: venerdì 6 agosto 2010 12:24
To: lucene-net-dev@lucene.apache.org
Subject: Indexing the multiple words at the same position

Has anyone encountered the following problem (and found a solution)

I need to index a classical text that can have multiple words at that same
position. Example: if a publisher isn't sure if Shakespeare wrote To be or
not to be happy or To be or not to be daddy, he will put the 'best' word
(eg. 'happy') in the full text and the second option (eg. 'daddy') in the
notes at the bottom of a page.
Now, our customer wants to search for to be daddy and find to be happy.
So, if I could index daddy at the same position as happy , I would be
very happy too.

Of course you can think of a solution where one would index the full text
for each version, but this is not sustainable when the number of multiple
occupation of a single position increase.

I have been looking at the 'next()' method of the 'Tokenizer' class, but I
haven't found the solution (yet).

Thanks in advance to all who reply.
Jeroen



[jira] Created: (LUCENENET-371) Unit test for Search.Regex port

2010-07-08 Thread Daniele Fusi (JIRA)
Unit test for Search.Regex port
---

 Key: LUCENENET-371
 URL: https://issues.apache.org/jira/browse/LUCENENET-371
 Project: Lucene.Net
  Issue Type: Test
Reporter: Daniele Fusi
Priority: Minor


I added some essential unit tests for my port of Search.Regex. Hope this will 
help you integrating this feature into one of your next releases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (LUCENENET-371) Unit test for Search.Regex port

2010-07-08 Thread Daniele Fusi (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENENET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniele Fusi updated LUCENENET-371:
---

Attachment: TestRegexpQuery.cs

Unit tests

 Unit test for Search.Regex port
 ---

 Key: LUCENENET-371
 URL: https://issues.apache.org/jira/browse/LUCENENET-371
 Project: Lucene.Net
  Issue Type: Test
Reporter: Daniele Fusi
Priority: Minor
 Attachments: TestRegexpQuery.cs


 I added some essential unit tests for my port of Search.Regex. Hope this will 
 help you integrating this feature into one of your next releases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.