On Mon, 4 Nov 2024 at 10:31, Agustin Martin <agmar...@debian.org> wrote:
> On Thu, Oct 31, 2024 at 11:06:34AM +0000, Reuben Thomas wrote: > > On Tue, 29 Oct 2024 at 18:15, Agustin Martin <agmar...@debian.org> > wrote: > > > Sorry, seems I did not explain myself correctly (and I am slowly > remembering about all this, so something of what I wrote may have been > inaccurate). > Thanks for the update! So, that is not really Aspell having Emacs-specific support for > Emacs-specific names, hidden from regular the aspell command-line, but > trying to keep some ispell compatibility regarding -d arguments. > So I'm still baffled: if Aspell doesn't know about "castellano" anywhere, then how does the command $ aspell check -d castellano mytext.txt work? If enchant people wants to add some of those aliases I would not go beyond > the equivalent ispell `-d' argument, so `enchant-2 -d ...' works similarly > as for ispell. > I don't know what you mean about adding aliases. My understanding from the above is that "castellano" is not known to aspell, so why would Enchant need to know about it? As you said: `aspell -l' uses locale based selection and I think it supports options shown by `aspell dump dicts'. So, since `aspell dump dicts` does not mention castellano (this is on a system with aspell-es installed), that means aspell doesn't know the name `castellano`, so I don't understand how using that name could possibly work! IIRC old enchant had some ispell code It had a complete copy of ispell in it. But that would only be used when ispell was used as the back-end, not when aspell or hunspell was used. -- https://rrt.sc3d.org
