Bug#487874: Problem of duff words in myspell-en-gb is more widespread

[Rene Engelhard <rene@debian.org>]

severity 487874 important
thanks

Hi,

John Winters wrote:
> >> I would suggest that the severity of this error needs increasing
> >> markedly, because the dictionary is useless with this many errors in it.
> > 
> > And what would you suggest? Remove the package? Revert to an ancient
> > version?
> 
e> I thought it was perfectly clear what I was suggesting - escalating the
> severity because the package is seriously broken.  If you want to go

I know that you said that. But when we make it RC we have to fi in in
one way or another quickly. I'be just marked it as important.

> further, and if it can't be determined how it was broken, then perhaps
> reverting to the last known good version would be the best bet.  It's
> not after all that ancient.

The point is that the last known version is 2.0.4. You don't really
suggest reverting to that? The other alternative is just not build
myspell-en-gb.

> > And are you sure this is a dictionary bug after all (i.e. are the words
> > really missing there - didn't check myself yet) or whether OOo or iceweasel
> > or whatever you use myspell-en-gb with just doesn't handle it correctly
> > in some manner?
> 
> No, I'm not sure, but the problem seems to manifest itself in both OOo
> and iceweasel, so it suggests that the problem is in the dictionary.

OK.

> Now, if you want to be constructive instead of getting silly then you
> can perhaps suggest how one could test where the problem is.  It seems

I *WAS* constructive, I try to find out
 a) where the problem exactly is
 b) when it appeared
 c) what you suggested.

> to be a systemic thing (all the duff words are derivatives) so it could
> be an algorithmic error.  The addition of lots of broken versions of the
> words also suggests this.

As I already said in my mail I didn't yet check the dictionary file.

> If you think the bug is filed against the wrong package, then make a
> suggestion of what it should be filed against, but don't post such
> inflammatory silliness.

One more comment like that and that bug will loose severity from my
processing queue (not that it's that far up on it anyway, have other
important stuff to do in other packages). I tried to just acquire more
info..

Regards,

Rene