search

Rainie3535 / sigil

Automatically exported from code.google.com/p/sigil
GNU General Public License v3.0
0 stars 0 forks source link

Inline spellchecker cannot handle accents #1127

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Enter a word with a letter with an accent (ë, á, é, and so on)
2. Word is identified as misspelled (with correct language)
3. With right click it can be replaced to something incorrect.
...

What is the expected output? What do you see instead?
Example: privé will become privé

What version of the product are you using? On what operating system?
Sigil 0.4902 on Windows XP and on Windows 7 x64

test epub attached and used language files. These were originally for 
OpenOffice.

Original issue reported on code.google.com by toxa...@gmail.com on 13 Dec 2011 at 5:47

Attachments:

GoogleCodeExporter commented 9 years ago 
Don't know if this will help, but I found this:

Dutch requires the - and ' and ’ to be accepted as part of a word. Otherwise, 
spell checking is functionally wrong in accepting words like bureau’s as 
correct. When using Hunspell, the best option to find the special characters to 
support as part of a word is reading the WORDCHARS clause from Hunspell's affix 
file.

Original comment by toxa...@gmail.com on 14 Dec 2011 at 7:26

GoogleCodeExporter commented 9 years ago 
I tried with my mother language that also has accents. This looks like encoding 
issue. I suppose that spelling is not working correctly for any other language 
that has accents.
1) I have a word "ērglis" that is marked as incorrect and suggestion is 
"çrglis" (we don't have ç as a character in our language. That kind of 
characters appear when file is saved in ASCII and not properly handled)
2) However, when I add "ērglis" to dictionary everything is fine (probably, 
because the new words get saved in Sigil's user_dict.txt which is UTF-8)

I use exactly the same dictionary files from LibreOffice. In LibreOffice spell 
checking is working properly.

Original comment by AJaunt...@gmail.com on 24 Dec 2011 at 9:52

GoogleCodeExporter commented 9 years ago 
Fixed. The encoding of the file was not being picked up properly.

Original comment by john@nachtimwald.com on 31 Dec 2011 at 12:39