From agmartin@aq.upm.es Tue Nov 19 19:33:30 2002 From: agmartin@aq.upm.es (=?ISO-8859-1?Q?Agust=EDn_Mart=EDn_Domingo?=) Date: Tue, 19 Nov 2002 20:33:30 +0100 Subject: [Dict-common-dev] Re. aspell Fixes pending upload Message-ID: <3DDA920A.7060104@aq.upm.es> > These bugs are all fixed in the pending upload of Aspell 0.50.x, which > is currently being held back due to a licensing dispute that should be > resolved shortly. > Have you already notified maintainers of abiword and other apps using pspell that new aspell no longer has pspell support and that they must choose explicitely whether to use ispell or aspell in their apps? I personally prefer the old way (pspell) of doing things, although it will become a dead end at some time, and would keep it until the affix compresion support is merged into aspell, but that is only my point of view. I am cc'ing to the dict-common mailing list, since we were considering how to merge aspell into the Debian dictionaries policy at http://dict-common.sourceforge.net/ and everything it had was for the old aspell. By the way, seems that the new libtool has fixed the hppa FTBFS bug, even with old aspell. I am trying that now, but I have to leave. Will try again tomorrow. Cheers, Agustin -- ===================================================================== Agustin Martin Domingo, Dpto. de Fisica, ETS Arquitectura Madrid, (U. Politecnica de Madrid) tel: +34 91-336-6536, Fax: +34 91-336-6554, email:agmartin@aq.upm.es, http://corbu.aq.upm.es/~agmartin/welcome.html From nelson@bignachos.com Tue Nov 19 23:26:11 2002 From: nelson@bignachos.com (Brian Nelson) Date: Tue, 19 Nov 2002 15:26:11 -0800 Subject: [Dict-common-dev] Re: Re. aspell Fixes pending upload In-Reply-To: <3DDA920A.7060104@aq.upm.es> =?iso-8859-1?q?(Agust=EDn_Mart=EDn?= Domingo's message of "Tue, 19 Nov 2002 20:33:30 +0100") References: <3DDA920A.7060104@aq.upm.es> Message-ID: <87y97p16r0.fsf@sirius.bignachos.com> --=-=-= Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Agust=EDn Mart=EDn Domingo writes: >> These bugs are all fixed in the pending upload of Aspell 0.50.x, which >> is currently being held back due to a licensing dispute that should be >> resolved shortly. >> > Have you already notified maintainers of abiword and other apps using > pspell that new aspell no longer has pspell support and that they must > choose explicitely whether to use ispell or aspell in their apps? No, not yet. I was planning to wait until upload was imminent before alerting them, since it's not clear when the licensing issues will be resolved. Also, I figured it was more of an upstream problem than a maintainer problem. Since pspell is deprecated, upstreams should be moving away from it. Note that the author claims that the new Aspell is backward-compatible with the old aspell/pspell combo: http://savannah.gnu.org/download/aspell/manual/user/2_Getting.html#SECTION0= 0354000000000000000 > I personally prefer the old way (pspell) of doing things, although it > will become a dead end at some time, and would keep it until the affix > compresion support is merged into aspell, but that is only my point of > view. Pspell is already considered a dead end, by the author anyway. Affix compression support is expected in the next release. > I am cc'ing to the dict-common mailing list, since we were considering > how to merge aspell into the Debian dictionaries policy at > > http://dict-common.sourceforge.net/ > > and everything it had was for the old aspell. Hmm, I'm not sure how the new Aspell would be integrated into that policy. It seems to be pretty much independent of ispell and its dictionaries. If there's anything I can do to help though, please let me know. > By the way, seems that the new libtool has fixed the hppa FTBFS bug, > even with old aspell. I am trying that now, but I have to leave. Will > try again tomorrow. /me mutters some profanities regarding libtool under my breath... =2D-=20 Curse my natural showmanship! --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE92siT1Ng1YWbyRSERAgYxAJ0SwE4v/V+ZsukTK3fh+fdyb7CDAgCeMrKv EHrrCu65ShlNqN82ob1PjQE= =4z3U -----END PGP SIGNATURE----- --=-=-=-- From dict-common-dev@lists.sourceforge.net Wed Nov 20 09:02:56 2002 From: dict-common-dev@lists.sourceforge.net (Rafael Laboissiere) Date: Wed, 20 Nov 2002 10:02:56 +0100 Subject: [Dict-common-dev] Re: aspell Fixes pending upload In-Reply-To: <87y97p16r0.fsf@sirius.bignachos.com> References: <3DDA920A.7060104@aq.upm.es> <87y97p16r0.fsf@sirius.bignachos.com> Message-ID: <20021120090256.GU24505@laboiss0> * Brian Nelson [2002-11-19 15:26]: > Hmm, I'm not sure how the new Aspell would be integrated into that policy. > It seems to be pretty much independent of ispell and its dictionaries. You are 100% right. The new Policy have been created originally to fix the problem of using update-alternatives to set symlinks in /usr/lib/ispell and to introduce a debconf-base configuration. We also added lately support for emacsen, jed and mutt, what is a big improvement, too. Aspell support will probably have a completely different implementation. > If there's anything I can do to help though, please let me know. I think that what we need now are just ideas about how to have integrated aspell support (dictionary and application packages). It would be great to have some default choice based on locale. To sum up, things are pretty open right now (specially since the pspell project is dead). -- Rafael From agmartin@aq.upm.es Wed Nov 20 16:45:53 2002 From: agmartin@aq.upm.es (=?iso-8859-1?Q?Agust=EDn=20Mart=EDn?= Domingo) Date: Wed, 20 Nov 2002 17:45:53 +0100 Subject: [Dict-common-dev] Re: aspell Fixes pending upload References: <3DDA920A.7060104@aq.upm.es> <87y97p16r0.fsf@sirius.bignachos.com> <20021120090256.GU24505@laboiss0> Message-ID: <3DDBBC41.57B095E9@aq.upm.es> Rafael Laboissiere wrote: > > You are 100% right. The only overlapping thing I see is left is the emacs stuff, once the pspell way has been deprecated. A pity, I really liked that idea. > > > If there's anything I can do to help though, please let me know. > > I think that what we need now are just ideas about how to have integrated > aspell support (dictionary and application packages). It would be great to > have some default choice based on locale. To sum up, things are pretty open > right now (specially since the pspell project is dead). > I think aspell already makes its default selection locale based. I do not remember if based in the LANG or LANGUAGE environment variables. Cheers Agustin And by the way, Brian, welcome to the spelling stuff. From agmartin@aq.upm.es Wed Nov 20 12:23:26 2002 From: agmartin@aq.upm.es (=?iso-8859-1?Q?Agust=EDn=20Mart=EDn?= Domingo) Date: Wed, 20 Nov 2002 13:23:26 +0100 Subject: [Dict-common-dev] Re: Re. aspell Fixes pending upload References: <3DDA920A.7060104@aq.upm.es> <87y97p16r0.fsf@sirius.bignachos.com> Message-ID: <3DDB7EBE.BE6BAF89@aq.upm.es> Brian Nelson wrote: > = > Agust=EDn Mart=EDn Domingo writes: > = > = > No, not yet. I was planning to wait until upload was imminent before > alerting them, since it's not clear when the licensing issues will be > resolved. Also, I figured it was more of an upstream problem than a > maintainer problem. Since pspell is deprecated, upstreams should be > moving away from it. > = Thanks, that was one of my worries about that. May be you can start contacting maintainers so they can prepare things in advance. > Note that the author claims that the new Aspell is backward-compatible > with the old aspell/pspell combo: > = > http://savannah.gnu.org/download/aspell/manual/user/2_Getting.html#SECT= ION00354000000000000000 > = Thanks again, nice to know that. From what I read I had the other feeling. At least I remember reading that pspell-ispell modules were no longer available, but I might be wrong again, since things in aspell change fast. In the policy document for ispell dictionaries we implemented the need of the pspell pwli files so they can be used through the pspell-ispell module. I guess we should remove that now, what do you think?. There is still a place where both systems ispell and aspell are related, emacs. We currently rebuild the emacs menus for dictionaries from mainly the ispell stuff, that leaves outside aspell ones, that can only be used if the corresponding ispell dict is installed. This requires to be improved. > > I personally prefer the old way (pspell) of doing things, although it= > > will become a dead end at some time, and would keep it until the affi= x > > compresion support is merged into aspell, but that is only my point o= f > > view. > = > Pspell is already considered a dead end, by the author anyway. Affix > compression support is expected in the next release. > = An aditional suggestion then, myspell dicts as well as aspell dicts will then have mostly the same files. Some coordination is needed so the same dict can be used from within myspell or aspell without installing two dictionaries (something like a common installation dir and symlinks from the aspell/myspell preferred locations). In an ideal world somebody should change the ispell aff format to the myspell one with all that implies so we get rid of repeated dictionaries, just which spellchecker to use would then remain as a user/program choice without the extra burden of a lot of dictionaries for the same language. > > I am cc'ing to the dict-common mailing list, since we were considerin= g > > how to merge aspell into the Debian dictionaries policy at > > > > http://dict-common.sourceforge.net/ > > > > and everything it had was for the old aspell. > = > Hmm, I'm not sure how the new Aspell would be integrated into that > policy. It seems to be pretty much independent of ispell and its > dictionaries. If there's anything I can do to help though, please let > me know. I think the only remaining problem is the emacs stuff I pointed out before. Also we added some aspell stuff to the policy, mainly an excerpt of the aspell/pspell documentation. This might also be good for the new aspell, but is your choice. > = > > By the way, seems that the new libtool has fixed the hppa FTBFS bug, > > even with old aspell. I am trying that now, but I have to leave. Will= > > try again tomorrow. > = > /me mutters some profanities regarding libtool under my breath... > = I also have no idea about libtool, what sounds like kanji to me, just seemed that the FTBFS was caused by libtool and yesterday tried to rebuild at paer and see what happen. It built until it realised that hppa was not listed as an arch on the control file, but seemed to pass after the FTBFS problem. I will try again tomorrow, today I am at other University. Cheers, Agustin From agmartin@aq.upm.es Tue Nov 19 19:33:30 2002 From: agmartin@aq.upm.es (=?ISO-8859-1?Q?Agust=EDn_Mart=EDn_Domingo?=) Date: Tue, 19 Nov 2002 20:33:30 +0100 Subject: [Dict-common-dev] Re. aspell Fixes pending upload Message-ID: <3DDA920A.7060104@aq.upm.es> > These bugs are all fixed in the pending upload of Aspell 0.50.x, which > is currently being held back due to a licensing dispute that should be > resolved shortly. > Have you already notified maintainers of abiword and other apps using pspell that new aspell no longer has pspell support and that they must choose explicitely whether to use ispell or aspell in their apps? I personally prefer the old way (pspell) of doing things, although it will become a dead end at some time, and would keep it until the affix compresion support is merged into aspell, but that is only my point of view. I am cc'ing to the dict-common mailing list, since we were considering how to merge aspell into the Debian dictionaries policy at http://dict-common.sourceforge.net/ and everything it had was for the old aspell. By the way, seems that the new libtool has fixed the hppa FTBFS bug, even with old aspell. I am trying that now, but I have to leave. Will try again tomorrow. Cheers, Agustin -- ===================================================================== Agustin Martin Domingo, Dpto. de Fisica, ETS Arquitectura Madrid, (U. Politecnica de Madrid) tel: +34 91-336-6536, Fax: +34 91-336-6554, email:agmartin@aq.upm.es, http://corbu.aq.upm.es/~agmartin/welcome.html From nelson@bignachos.com Tue Nov 19 23:26:11 2002 From: nelson@bignachos.com (Brian Nelson) Date: Tue, 19 Nov 2002 15:26:11 -0800 Subject: [Dict-common-dev] Re: Re. aspell Fixes pending upload In-Reply-To: <3DDA920A.7060104@aq.upm.es> =?iso-8859-1?q?(Agust=EDn_Mart=EDn?= Domingo's message of "Tue, 19 Nov 2002 20:33:30 +0100") References: <3DDA920A.7060104@aq.upm.es> Message-ID: <87y97p16r0.fsf@sirius.bignachos.com> --=-=-= Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Agust=EDn Mart=EDn Domingo writes: >> These bugs are all fixed in the pending upload of Aspell 0.50.x, which >> is currently being held back due to a licensing dispute that should be >> resolved shortly. >> > Have you already notified maintainers of abiword and other apps using > pspell that new aspell no longer has pspell support and that they must > choose explicitely whether to use ispell or aspell in their apps? No, not yet. I was planning to wait until upload was imminent before alerting them, since it's not clear when the licensing issues will be resolved. Also, I figured it was more of an upstream problem than a maintainer problem. Since pspell is deprecated, upstreams should be moving away from it. Note that the author claims that the new Aspell is backward-compatible with the old aspell/pspell combo: http://savannah.gnu.org/download/aspell/manual/user/2_Getting.html#SECTION0= 0354000000000000000 > I personally prefer the old way (pspell) of doing things, although it > will become a dead end at some time, and would keep it until the affix > compresion support is merged into aspell, but that is only my point of > view. Pspell is already considered a dead end, by the author anyway. Affix compression support is expected in the next release. > I am cc'ing to the dict-common mailing list, since we were considering > how to merge aspell into the Debian dictionaries policy at > > http://dict-common.sourceforge.net/ > > and everything it had was for the old aspell. Hmm, I'm not sure how the new Aspell would be integrated into that policy. It seems to be pretty much independent of ispell and its dictionaries. If there's anything I can do to help though, please let me know. > By the way, seems that the new libtool has fixed the hppa FTBFS bug, > even with old aspell. I am trying that now, but I have to leave. Will > try again tomorrow. /me mutters some profanities regarding libtool under my breath... =2D-=20 Curse my natural showmanship! --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE92siT1Ng1YWbyRSERAgYxAJ0SwE4v/V+ZsukTK3fh+fdyb7CDAgCeMrKv EHrrCu65ShlNqN82ob1PjQE= =4z3U -----END PGP SIGNATURE----- --=-=-=-- From dict-common-dev@lists.sourceforge.net Wed Nov 20 09:02:56 2002 From: dict-common-dev@lists.sourceforge.net (Rafael Laboissiere) Date: Wed, 20 Nov 2002 10:02:56 +0100 Subject: [Dict-common-dev] Re: aspell Fixes pending upload In-Reply-To: <87y97p16r0.fsf@sirius.bignachos.com> References: <3DDA920A.7060104@aq.upm.es> <87y97p16r0.fsf@sirius.bignachos.com> Message-ID: <20021120090256.GU24505@laboiss0> * Brian Nelson [2002-11-19 15:26]: > Hmm, I'm not sure how the new Aspell would be integrated into that policy. > It seems to be pretty much independent of ispell and its dictionaries. You are 100% right. The new Policy have been created originally to fix the problem of using update-alternatives to set symlinks in /usr/lib/ispell and to introduce a debconf-base configuration. We also added lately support for emacsen, jed and mutt, what is a big improvement, too. Aspell support will probably have a completely different implementation. > If there's anything I can do to help though, please let me know. I think that what we need now are just ideas about how to have integrated aspell support (dictionary and application packages). It would be great to have some default choice based on locale. To sum up, things are pretty open right now (specially since the pspell project is dead). -- Rafael From agmartin@aq.upm.es Wed Nov 20 16:45:53 2002 From: agmartin@aq.upm.es (=?iso-8859-1?Q?Agust=EDn=20Mart=EDn?= Domingo) Date: Wed, 20 Nov 2002 17:45:53 +0100 Subject: [Dict-common-dev] Re: aspell Fixes pending upload References: <3DDA920A.7060104@aq.upm.es> <87y97p16r0.fsf@sirius.bignachos.com> <20021120090256.GU24505@laboiss0> Message-ID: <3DDBBC41.57B095E9@aq.upm.es> Rafael Laboissiere wrote: > > You are 100% right. The only overlapping thing I see is left is the emacs stuff, once the pspell way has been deprecated. A pity, I really liked that idea. > > > If there's anything I can do to help though, please let me know. > > I think that what we need now are just ideas about how to have integrated > aspell support (dictionary and application packages). It would be great to > have some default choice based on locale. To sum up, things are pretty open > right now (specially since the pspell project is dead). > I think aspell already makes its default selection locale based. I do not remember if based in the LANG or LANGUAGE environment variables. Cheers Agustin And by the way, Brian, welcome to the spelling stuff. From agmartin@aq.upm.es Wed Nov 20 12:23:26 2002 From: agmartin@aq.upm.es (=?iso-8859-1?Q?Agust=EDn=20Mart=EDn?= Domingo) Date: Wed, 20 Nov 2002 13:23:26 +0100 Subject: [Dict-common-dev] Re: Re. aspell Fixes pending upload References: <3DDA920A.7060104@aq.upm.es> <87y97p16r0.fsf@sirius.bignachos.com> Message-ID: <3DDB7EBE.BE6BAF89@aq.upm.es> Brian Nelson wrote: > = > Agust=EDn Mart=EDn Domingo writes: > = > = > No, not yet. I was planning to wait until upload was imminent before > alerting them, since it's not clear when the licensing issues will be > resolved. Also, I figured it was more of an upstream problem than a > maintainer problem. Since pspell is deprecated, upstreams should be > moving away from it. > = Thanks, that was one of my worries about that. May be you can start contacting maintainers so they can prepare things in advance. > Note that the author claims that the new Aspell is backward-compatible > with the old aspell/pspell combo: > = > http://savannah.gnu.org/download/aspell/manual/user/2_Getting.html#SECT= ION00354000000000000000 > = Thanks again, nice to know that. From what I read I had the other feeling. At least I remember reading that pspell-ispell modules were no longer available, but I might be wrong again, since things in aspell change fast. In the policy document for ispell dictionaries we implemented the need of the pspell pwli files so they can be used through the pspell-ispell module. I guess we should remove that now, what do you think?. There is still a place where both systems ispell and aspell are related, emacs. We currently rebuild the emacs menus for dictionaries from mainly the ispell stuff, that leaves outside aspell ones, that can only be used if the corresponding ispell dict is installed. This requires to be improved. > > I personally prefer the old way (pspell) of doing things, although it= > > will become a dead end at some time, and would keep it until the affi= x > > compresion support is merged into aspell, but that is only my point o= f > > view. > = > Pspell is already considered a dead end, by the author anyway. Affix > compression support is expected in the next release. > = An aditional suggestion then, myspell dicts as well as aspell dicts will then have mostly the same files. Some coordination is needed so the same dict can be used from within myspell or aspell without installing two dictionaries (something like a common installation dir and symlinks from the aspell/myspell preferred locations). In an ideal world somebody should change the ispell aff format to the myspell one with all that implies so we get rid of repeated dictionaries, just which spellchecker to use would then remain as a user/program choice without the extra burden of a lot of dictionaries for the same language. > > I am cc'ing to the dict-common mailing list, since we were considerin= g > > how to merge aspell into the Debian dictionaries policy at > > > > http://dict-common.sourceforge.net/ > > > > and everything it had was for the old aspell. > = > Hmm, I'm not sure how the new Aspell would be integrated into that > policy. It seems to be pretty much independent of ispell and its > dictionaries. If there's anything I can do to help though, please let > me know. I think the only remaining problem is the emacs stuff I pointed out before. Also we added some aspell stuff to the policy, mainly an excerpt of the aspell/pspell documentation. This might also be good for the new aspell, but is your choice. > = > > By the way, seems that the new libtool has fixed the hppa FTBFS bug, > > even with old aspell. I am trying that now, but I have to leave. Will= > > try again tomorrow. > = > /me mutters some profanities regarding libtool under my breath... > = I also have no idea about libtool, what sounds like kanji to me, just seemed that the FTBFS was caused by libtool and yesterday tried to rebuild at paer and see what happen. It built until it realised that hppa was not listed as an arch on the control file, but seemed to pass after the FTBFS problem. I will try again tomorrow, today I am at other University. Cheers, Agustin