Issue Details (XML | Word | Printable)

Key: FL-99
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Ken VanDine
Reporter: Thilo Pfennig
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Foresight Linux

xchat-gnome does not support spell checking

Created: 20/Jan/07 10:34 PM   Updated: 20/May/07 04:25 PM
Component/s: GNOME
Affects Version/s: 0.9.9
Fix Version/s: 1.2.1
Security Level: Public (Everyone can see this issue)

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. Bildschirmfoto-Preferences.png
(29 kB)


 Description  « Hide
my guess is that this might work with english LANG but not with "de_DE.UTF-8" . Will have to check what it does woth LANG=C after this report.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Thilo Pfennig added a comment - 20/Jan/07 11:01 PM
this has nothing todo with $LANG.

It says. "In order to get spell-checking you need to have libenchant installed with at least one dictionary" I have also installed aspell-de because i thought it might miss a dictionary. No success. What does it need to work?


Thilo Pfennig added a comment - 20/Jan/07 11:32 PM
There is also an issue with Abiword. it says it can not find the dictionary. So this is NOT an xchat-problem. Something with enchant.

Ken VanDine added a comment - 21/Jan/07 04:53 AM
Spell checking in xchat-gnome works for me in english.

enchant=1.1.6-1-1

Any ideas?


Thilo Pfennig added a comment - 28/Jan/07 12:43 AM
this is till true for FL 1.0,

Thilo Pfennig added a comment - 28/Jan/07 12:45 AM
this is how it looks

Ken VanDine added a comment - 28/Jan/07 07:42 PM
I see a list of locales, only 4

en, en_GB, en_CA, en_US

So all english. Did you verify you have enchant installed?

My guess is those are the only locales supported, we should investigate that.


Thilo Pfennig added a comment - 28/Jan/07 11:14 PM
I have enchant=1.1.6-1-1

Thilo Pfennig added a comment - 20/May/07 04:25 PM
this was fixed.