On Thu, Jul 17, 2014 at 11:42 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > 17/07/2014 17:35, Scott Kostyshak: > >>> Maybe the list that allows to choose the spellchecker could read "none >>> available"? >> >> >> I wanted to come up with something that would signal to the user that >> it is a build issue and not a "can't find hunspell" issue (i.e. it's a >> "didn't tell me to look for hunspell" issue). > > > "none compiled in"? "not supported"?
Yes I like "none compiled in" but have mixed feelings. If it is someone who compiled LyX themselves, then it is good because it is a strong signal of how to fix the problem. But if it is someone using a package on their distro compiled by the packager then maybe that would be a scary/confusing message? What do others think? Scott
