I realise that this list (general discussion), may not be the correct place
for such a nerdy tour de force. Let me see if there's another or maybe
create an explicit hermes-dev list.
I also realise that I may end up talking mostly to myself, what with Pete
on hiatus and all, but a hermes-dev list would double as a public
whiteboard. One all can take a look at at will.
I realise that this list (general discussion), may not be the correct
place for such a nerdy tour de force. Let me see if there's another or
maybe create an explicit hermes-dev list.
I also realise that I may end up talking mostly to myself, what with Pete
on hiatus and all, but a hermes-dev list would double as a public
whiteboard. One all can take a look at at will.
I realise that this list (general discussion), may not be the correct
place for such a nerdy tour de force. Let me see if there's another or
maybe create an explicit hermes-dev list.
That's neater than I thought it would be. I'll send you a photo of mine and you'll understand :D Let's just say, don't go in my office without a pair of hard-soled footwear and possibly a fire extinguisher.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's neater than I thought it would be. I'll send you a photo of mine
and you'll understand :D Let's just say, don't go in my office without a
pair of hard-soled footwear and possibly a fire extinguisher.
Honestly, I don't know why I manually compiled hunspell as it is
available as a package (libhunspell), containing the dynamic lib. Maybe
because I couldn't find a nuspell lib and just assumed the same would be
the case with hunspell.
Either way, it's there. I like the fact that it was originally intended for
Hungarian.
I'll check a little around for nuspell. The only difference I can find is
that nuspell is a pure C++ version of hunspell. How much speed difference
we're talking about, I don't know.
To be brutally honest though, it seems as if nuspell is not entirely
finished...
Was this C++ thing the only argument for using one over the other?
Well, notice how I consciously avoided getting the floor on the pic. :)
Regards
On Friday, September 14, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
That's neater than I thought it would be. I'll send you a photo of mine
and you'll understand :D Let's just say, don't go in my office without a
pair of hard-soled footwear and possibly a fire extinguisher.
The Qualcomm headers should already make reference to the BSD licence. If they don't, feel free to replace the notice with something like Cop't (c) 1991-2005 Qualcomm, 2018 HERMES, All rights reserved, use of this code is governed by [text of three-clause BSD licence]
If I get nuspell to work, or, indeed, end up with hunspell, we still have
the question of static vs dynamic. How will we use it?
Regards
--
Søren Bro Thygesen
(AFK)
This looks relevant, on the face of it:
https://www.quora.com/What-are-the-pros-and-cons-of-static-and-dynamic-linking-in-c++
Regards
On Friday, September 14, 2018, Soren Bro sbrothy@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
(AFK)
I realise that this list (general discussion), may not be the correct place
for such a nerdy tour de force. Let me see if there's another or maybe
create an explicit hermes-dev list.
Regards
On Friday, September 14, 2018, Soren Bro sbrothy@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
(AFK)
I also realise that I may end up talking mostly to myself, what with Pete
on hiatus and all, but a hermes-dev list would double as a public
whiteboard. One all can take a look at at will.
Regards
On Friday, September 14, 2018, sbrothy@gmail.com wrote:
--
Søren Bro Thygesen
(AFK)
I seem to be unable to create one. Perhaps because I'm on my cell, though
I doubt that's the reason.
Maybe someone, with the proper credentials, would create one as
"hermesmail-development"?
You would be free from my rants. :)
Regards
On Friday, September 14, 2018, sbrothy@gmail.com wrote:
--
Søren Bro Thygesen
My workstation after an all-nighter. Attached.
Regards
--
Søren Bro Thygesen
OK. That "Yo" in there was an error. I'm too old running around and saying
"Yo". That's for sure.
Regards.
On Fri, Sep 14, 2018 at 5:45 PM sbrothy@gmail.com wrote:
nuspell / hunspell.
hunspell has a pretty darn impressive list of clients / users:
https://en.wikipedia.org/wiki/Hunspell
Regards.
On Fri, Sep 14, 2018 at 5:52 PM Soren Bro sbrothy@users.sourceforge.net
wrote:
That's neater than I thought it would be. I'll send you a photo of mine and you'll understand :D Let's just say, don't go in my office without a pair of hard-soled footwear and possibly a fire extinguisher.
(AFK)
Well, notice how I consciously avoided getting the floor on the pic. :)
Regards
On Friday, September 14, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
(AFK)
Honestly, I don't know why I manually compiled hunspell as it is
available as a package (libhunspell), containing the dynamic lib. Maybe
because I couldn't find a nuspell lib and just assumed the same would be
the case with hunspell.
Either way, it's there. I like the fact that it was originally intended for
Hungarian.
I'll check a little around for nuspell. The only difference I can find is
that nuspell is a pure C++ version of hunspell. How much speed difference
we're talking about, I don't know.
To be brutally honest though, it seems as if nuspell is not entirely
finished...
Was this C++ thing the only argument for using one over the other?
Regards
On Saturday, September 15, 2018, Soren Bro sbrothy@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
But I like your rants, I'm managing this project, and I absolutely can't do my job without status reports!
You won't end up talking to yourself - there's always me, and I should be able to provide direction and support, even if I can't provide code.
Cute. Because, as you see, the intro headers saying "QualComm" are all
worth replacing right?
On Fri, Sep 14, 2018 at 8:17 PM Ted Matavka nmatavka@users.sourceforge.net
wrote:
I may not be able to compile nuspell, but hunspell is the engine in some
pretty hefty programs:
https://en.wikipedia.org/wiki/Hunspell
If we start with hunspell , which nuspell is based upon, we'll be able to
replace it quite easily...
Regards.
On Fri, Sep 14, 2018 at 8:30 PM sbrothy@gmail.com wrote:
The Qualcomm headers should already make reference to the BSD licence. If they don't, feel free to replace the notice with something like Cop't (c) 1991-2005 Qualcomm, 2018 HERMES, All rights reserved, use of this code is governed by [text of three-clause BSD licence]
Text of BSD licence available here: https://en.wikipedia.org/wiki/BSD_licenses#3-clause_license_(%22BSD_License_2.0%22,%22Revised_BSD_License%22,%22New_BSD_License%22,or%22Modified_BSD_License%22)
Let's link dynamically, please. This allows us to do in-place upgrades, like we did with QCSSL. :-)
That is the choice I would make too.
(AFK)
You mean choosing nuspell?
The current spell module is a DLL, right?
Regards
On Saturday, September 15, 2018, Pete Maclean petemaclean@users.sourceforge .net wrote:
--
Søren Bro Thygesen
(AFK)
Highly likely there's a job here for one of the structural patterns from
Gamma et al.
I'm pretty sure this will speed up the process.
The whole book is online as a PDF file. 3'rd or 4'rd (ca) link just
searching for "gamma et al"
Totally unrelated:
Does Google throw away "et" and "al" you think? It probably does. Nevermind.
You can tell I'm bored right? I'm in a gigantic line here.
Regards
On Saturday, September 15, 2018, sbrothy@gmail.com wrote:
--
Søren Bro Thygesen