Quote:
Originally Posted by BetterRed
I have no expectations you would to apply them to hunspell dictionaries - that would definitely be a bridge too far. I just wanted to clarify how I 'adjust' the standard Word dictionaries.
|
I already made them work for the hunspell dictionaries as well... That was not so hard, getting the filename for the exclusion file was (long live CLID...).
Quote:
Originally Posted by BetterRed
As already indicated, I'll have no problems with having to restart Word when I want to switch from using Word's dictionaries to hunspell dictionaries and vice versa - but I would like to know which ones I'm currently using 
|
Hunspell only works for my procedure and there it is displayed whether the Word or Hunspell engine is used. If you want to switch custom dictionary a restart is only required for the Word spelling procedure. I made it work for using the Word spelling engine for my procedure.
Quote:
Originally Posted by BetterRed
By custom dictionaries I assume you mean the supplementary word lists that Word and hunspell can use and maintain. Are you saying they can be the same files - that would be cool? I use multiple 'custom dictionaries' in Word - one for general purpose, and others that are genre/domain specific.
|
Yes, you can use them both in my spelling procedure, but only one at the time.
Quote:
Originally Posted by BetterRed
Numbers are my main concern, I only mentioned the UPPERCASE and urls for 'completeness' sake.
I raise it because the spell checker in Sigil does ignore some words with numbers, but the spell checker in calibre doesn't ignore any - but both purport to use hunspell. If you're interested spellcheck this -- Attachment 146820 -- in sigil and calibre
The following is the same real book - sigil on the left, calibre on the right, with same dictionaries.
Attachment 146819
In the following index entry, Calibre reports 235n32 as a misspelling, but Sigil doesn't - and it is not because of semantic settings.
Code:
<a class="normal" href="../Text/Notes-1.html#page_235">235n32</a>
But for real books such as the one above I only convert them to DOCX for the purpose of iFilter based content searching. I would never spell check it in Word.
|
I have incorporated this, so my spelling engine uses the same settings as Word. However, I will also create a setting to ignore this for my specific procedure, as I feel that it would bypass several spelling mistakes. I will also set a strong warning about these settings in the manual.