Stephan Witt <st.w...@gmx.net> writes: > Note, the current implementation is guarded by _APPLE_ #ifdef. > After some discussion it could be more general... > > Therefore currently it is Apple-like: > 1) aspell user dir: /Users/stephan/Library/Application > Support/LyX-2.0.0svn/Aspell.framework/Resources/dict > 2) aspell bundle path: > /Users/stephan/cvs/lyx/lyx-build/LyX-2.0.0svn.app/Contents/Frameworks/Aspell.framework/Resources/dict > 3) macports path: /opt/local/share/aspell
OK, I see. Personally, I would put dictionaries together with the other files provided by LyX, and this in a machine independent way. Would anybody object to that. Would it be useful to windows people? >> Enchant is only a wrapper for other spellcheckers. As you say below the >> other alternative is the native OS X spellchecker. > > Yes, I had the hope to go with enchant or hunspell to have access to > the native OS X spellchecker. Hunspell can be seen as some kind of successor to aspell. At least it is supposed to be better (am I right?) Concerning Enchant, we do not know how to make AppleSpell support work, so writing it directly would be easier. >> What I would propose is to put dictionaries in >> $sysdir/aspell-dicts >> $userdir/aspell-dicts or maybe aspell instead of aspell-dicts. It is like the way we distribute fonts. The it is the packager's choice to put dictionaries there or not. > For the Apple app $sysdir would be > /Users/stephan/cvs/lyx/lyx-build/LyX-2.0.0svn.app/Contents/Resources? Yes. >> I think this should be an alternative to aspell, since it is the tool >> used by all other programs, after all. > > 1) Alternative in the sense of replacement of aspell? > 2) Or as another option for the user? > > I guess the answer is 2) Probably yes. Basic user probably assume that LyX should support the OS level dictionaries. Some advanced users may prefer to add dictionaries for less common language via aspell (or hunspell). JMarc
