Processing commands for [EMAIL PROTECTED]:
> severity 14929 normal
Bug#14929: ispell: ispell "\macro\ itself" sometimes goes wrong.
Severity set to `normal'.
> merge 14929 32726
Bug#14929: ispell: ispell "\macro\ itself" sometimes goes wrong.
Bug#32726: ispell -t doesn't handle macros like \, or
Package: ispell
Version: 3.1.20-0.6
Severity: wishlist
I'm the new (prospective) ispell package maintainer, and I don't
want to forget about this suggestion...
(copied from debian-devel)
To: Debian Development Mailing List
Subject: update-ispell-hash
From: Piotr Roszatycki <[EMAIL P
I've extracted the following from a recent email conversation
I had with Geoff Kuenning, the upstream author/maintainer:
> ...munchlist.X contains this comment, which may be relevant:>
>
> # -w Passed on to ispell (specify chars that are part of a word)
> # Unfortunately,
I received the following comment from the upstream maintainer.
I'll be packaging 3.2.01 (a pre-release) soon; let me know if
you want to try it.
> There are tons of TeX variants that ispell doesn't understand.
> Fortunately, ispell 3.2 will have two new mechanisms that will address
> the problem.
I received the following request from the upstream maintainer;
please reply to [EMAIL PROTECTED] with the specific warnings,
or to let us know if you can no longer do that yourself. Thanks.
> I've tried to address some of these, but it would be very helpful to
> get a complete list of the warning
I received the following comment from the upstream maintainer:
> On my list, but probably won't be fixed in the next release.
Thomas,
I received the following brief comment from the upstream developer
regarding this bug report; does this help you?
> User error. Ispell does support iso-latin1 in TeX; it's just not the
> default.
The upstream developer reports that these problems are fixed in ispell 3.2.
I'm currently packaging a pre-release of 3.2 (3.2.01) for testing; reply
to [EMAIL PROTECTED] if you'd like to try that.
I received the following comment from the upstream author. I haven't
decided yet what to do about this, but will do so soon. If you have
further comments, please send them to [EMAIL PROTECTED] Thanks.
> Torsten's suggestion of screwing backwards compatibility is not
> acceptable. The real bug
I received the following comment from the upstream author, and
will investigate:
> This is a Debian configuration error. If /usr/dict/words doesn't
> exist, a replacement should be specified by defining WORDS in config.X.
Processing commands for [EMAIL PROTECTED]:
> close 38169
Bug#38169: relink with openssl
Bug closed, ack sent to submitter - they'd better know why !
> thanks
Stopping processing here.
Please contact me if you need assistance.
Ian Jackson
(administrator, Debian bugs database)
On 1999-07-22 02:14:13 +, David Coe wrote:
> I received the following brief comment from the upstream developer
> regarding this bug report; does this help you?
Errm. Looking at this once more, this was indeed a pilot error.
Forget it, sorry.
Your message dated Thu, 22 Jul 1999 04:09:39 +
with message-id <[EMAIL PROTECTED]>
and subject line (no subject)
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reo
Your message dated Thu, 22 Jul 1999 04:57:01 +
with message-id <[EMAIL PROTECTED]>
and subject line ispell...should permit iso-latin1 characters when in TeX mode
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for [EMAIL PROTECTED]:
> reassign 35287 ispell
Bug#35287: ibritish: American spellings allowed, British ones rejected
Bug reassigned from package `ibritish' to `ispell'.
> forwarded 35287 [EMAIL PROTECTED]
Bug#35287: ibritish: American spellings allowed, British ones rejected
[ Large crosspost to start the discussion, please reply to debian-devel
only. Simply respect the reply-to. ]
Hello everybody,
you may or not be aware that getting a Debian developer is quite long. I
want to propose a solution to facilitate the integration of new
Debian developers.
It's quite s
I basically accept the upstream developer's position. Here are my
comments to his response.
> > Torsten's suggestion of screwing backwards compatibility is not
> > acceptable.
OK. I haven't seen any systems which support SysV termio yet don't
support the POSIX.1 termios, but I accept that there
17 matches
Mail list logo
