[GitHub] lucenenet issue #181: Analysis work

2016-08-27 Thread ChristopherHaws
Github user ChristopherHaws commented on the issue: https://github.com/apache/lucenenet/pull/181 @NightOwl888 I didnt see your message until just now. I was working on converting from Locale to CultureInfo. I made a stub class for `Collator`, but this should probably be changed to an

[GitHub] lucenenet issue #181: Analysis work

2016-08-27 Thread NightOwl888
Github user NightOwl888 commented on the issue: https://github.com/apache/lucenenet/pull/181 I am pulling down your work on Collation so I can work with it. I'll see if I can merge these worlds together - most likely we just need to add some overloads that accept culture to some of

[GitHub] lucenenet issue #181: Analysis work

2016-08-27 Thread ChristopherHaws
Github user ChristopherHaws commented on the issue: https://github.com/apache/lucenenet/pull/181 Yes, I pretty much have them all cleaned up, but the Collator class is specific to Java. I noticed that there is a reference to ICU4NET in the project, however that project only has the

[GitHub] lucenenet issue #181: Analysis work

2016-08-26 Thread NightOwl888
Github user NightOwl888 commented on the issue: https://github.com/apache/lucenenet/pull/181 @ChristopherHaws - Hey, I am thinking about taking another shot at porting over Collation. Did you get anything done and/or are you working on it? --- If your project is set up for it, you

[GitHub] lucenenet issue #181: Analysis work

2016-08-23 Thread ChristopherHaws
Github user ChristopherHaws commented on the issue: https://github.com/apache/lucenenet/pull/181 Yes, I think we can close this pull request. Thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[GitHub] lucenenet issue #181: Analysis work

2016-08-22 Thread ChristopherHaws
Github user ChristopherHaws commented on the issue: https://github.com/apache/lucenenet/pull/181 Sounds good. I will take a look at the collation namespace tonight when I get home from work. Thanks! --- If your project is set up for it, you can reply to this email and have

[GitHub] lucenenet issue #181: Analysis work

2016-08-22 Thread NightOwl888
Github user NightOwl888 commented on the issue: https://github.com/apache/lucenenet/pull/181 Sure. I am currently working on https://github.com/NightOwl888/lucenenet/commits/analysis-work-2, which I plan to merge into #179 (probably within the next few hours). About the only

[GitHub] lucenenet issue #181: Analysis work

2016-08-22 Thread NightOwl888
Github user NightOwl888 commented on the issue: https://github.com/apache/lucenenet/pull/181 Actually, all of this is already done in #179. I am intrigued about the EntryIterator bug fix, though. The solution I came up with was to maintain an internal dictionary and return

[GitHub] lucenenet issue #181: Analysis work

2016-08-22 Thread synhershko
Github user synhershko commented on the issue: https://github.com/apache/lucenenet/pull/181 Awesome, thanks! Can you please check https://github.com/apache/lucenenet/pull/179 to see you and @NightOwl888 aren't working on the same stuff? --- If your project is set up for it, you can