Am 17.01.2014 um 14:55 schrieb Ben Lowe <[email protected]>: > Dear Stephan, > > Thanks for your quick response. What option do I provide lyx with in > order to compile with enchant/hunspell etc.? I cannot find this > information in the README, INSTALL etc.,
Sorry for being unclear. You have to install the developer packages - aka rpms - for the spell checker of your choice. Something like hunspell-devel-* for hunspell (I don't know the package name for RedHat and I don't know either if it exists). After doing so LyX detects it at configure time and will be build with hunspell support. This should be mentioned in config.log. There is no configure option. > Until I do this, I cannot provide a path for Hunspell as the path > section is greyed out, and I cannot select the Enchant engine. Hunspell is not Enchant. Hunspell path is for hunspell spell checker. I'd recommend using hunspell. I don't know if enchant is usable. Stephan > On 17 January 2014 13:11, Stephan Witt <[email protected]> wrote: >> Am 17.01.2014 um 13:44 schrieb Ben Lowe <[email protected]>: >> >>> Hi, >>> >>> I'm using redhat 6; I've tried downloading the latest source and >>> following these steps: >>> http://wiki.lyx.org/LyX/CreatingLyXRPM#toc3 >>> >>> And also tried creating an RPM package, however the dictionary choice >>> in preferences > language settings > spellchecker; all options are >>> greyed out, and I cannot provide a hunspell path under preferences >>>> paths as this is greyed out. I have relevant hunspell dictionary >>> files in the ~/.lyx/dicts/ folder and they are named correctly. >>> >>> This a common issue with linux due to not compiling it with >>> spellchecking support, and a fix is apparently to use 'Enchant' engine >>> instead, however I have the Enchant package, and I still cannot select >>> any spellchecker engines from the spellchecker menu. >>> >>> Does anyone have any suggestions on how I can compile lyx on Redhat >>> with spell checking support? >> >> Hi, >> >> you have to provide the developer packages of the spell checker of your >> choice at compile time (of LyX). In case it's enchant you have to configure >> enchant, in case it's hunspell you may provide the path for the dictionary >> files under preferences if they're not found automatically. >> >> Stephan
