Re: [text] Next steps.

2016-11-29 Thread Rob Tompkins
ving the human name parser elsewhere, >>> reviewing the edit distances, >>> and checking if there's anything else we could put into this initial >>> release from [lang]. >>> >>> Once it has been released, we will be able to add things from Lothaire &

Re: [text] Next steps.

2016-11-29 Thread Benedikt Ritter
dd things from Lothaire > > book, > > more edit distances, maybe bring back the name parser, as well as any > > enhancement > > bug fixing. > > > > Bruno > > > > > > > > From: Rob Tompkins > > >To: Common

Re: [text] Next steps.

2016-11-28 Thread Gary Gregory
book, > more edit distances, maybe bring back the name parser, as well as any > enhancement > bug fixing. > > Bruno > > >________ > > From: Rob Tompkins > >To: Commons Developers List > >Sent: Tuesday, 29 November 2016 11:45 AM > >Subject: [text] N

Re: [text] Next steps.

2016-11-28 Thread Gary Gregory
If it were just me, I would: - Port all relevant (with appropriate agreements from the community) code from [lang] to [text]. - Release [text] 1.0 - Deprecate code in [lang] - Release [lang] 3.6. - Continue [text] on to 1.1 with NEW functionality. IOW, I do not see the point of delaying [text] 1.

Re: [text] Next steps.

2016-11-28 Thread Bruno P. Kinoshita
maybe bring back the name parser, as well as any enhancement bug fixing. Bruno > > From: Rob Tompkins >To: Commons Developers List >Sent: Tuesday, 29 November 2016 11:45 AM >Subject: [text] Next steps. > > >Hello, > >I'm a

[text] Next steps.

2016-11-28 Thread Rob Tompkins
Hello, I'm a tad curious what folks (along with Gary, Benedikt, and Bruno) think the next steps are for text in the hopeful thought that we are eventually heading towards a 1.0 release. Some thoughts that come to mind are: (1) Go over lang with fine tooth comb and see what we think should move, (