Xchat sources have internal copy of sexy-spell-entry.{c,h} which is part of libsexy. I think it should use external libsexy and link against it.
Created attachment 171353 [details, diff] Patch against 2.8.6-r1 ebuild to use external libsexy xchat actually has a configure option to do so, here I'm attaching a diff against 2.8.6-r1 which uses this option.
Created attachment 171358 [details, diff] Patch against 2.8.6-r1 ebuild to use external gtkspell Here's another patch that builds against gtkspell. I would perefer that since SexySpellEdit has a bug in Turkish locale. See: http://bugzilla.gnome.org/show_bug.cgi?id=559982
Done on -r2, thanks.
The gtkspell version leaves a significant amount of vertical space below the text in the entry box (using Monospace font). This doesn't happen with the buit-in version. Is there any way to prevent this?
(In reply to comment #4) > The gtkspell version leaves a significant amount of vertical space below the > text in the entry box (using Monospace font). This doesn't happen with the > buit-in version. Is there any way to prevent this? > Indeed, it looks FUBAR. I downgraded to -r1.
^ Still broken ^
I'm seeing this as well, would be nice to get this regression fixed.
(In reply to comment #7) > I'm seeing this as well, would be nice to get this regression fixed. > Can you test if you can reproduce the suggestion issue with any other non-ascii characters. In any case, this still depends on upstream issue to be resolved.
(In reply to comment #8) > Can you test if you can reproduce the suggestion issue with any other > non-ascii characters. In any case, this still depends on upstream issue to be > resolved. Sorry, I was not talking about the suggestion issue, but about the much larger input line as mentioned in comment 4.
(In reply to comment #9) > Sorry, I was not talking about the suggestion issue, but about the much larger > input line as mentioned in comment 4. > But the only other option is using SexySpellEntry which is *borked* (See the upstream bug)
(In reply to comment #10) > But the only other option is using SexySpellEntry which is *borked* (See the > upstream bug) In which case it seems to me that the proper option is to fix the UI as well when using gtkspell as the preferred spelling widget.
Why do that, thats what breaks spell check support in xchat. to get spell check back working in xchat build with enchant statically linked and have enchant built eith the aspell use flag
(In reply to comment #12) > Why do that, thats what breaks spell check support in xchat. > > to get spell check back working in xchat build with enchant statically linked > and have enchant built eith the aspell use flag > i was wrong all you need is enchant built with aspell use flag
(In reply to comment #13) > (In reply to comment #12) > > Why do that, thats what breaks spell check support in xchat. > > > > to get spell check back working in xchat build with enchant statically linked > > and have enchant built eith the aspell use flag > > > > i was wrong all you need is enchant built with aspell use flag > I don't get what you mean, the problem is with the widget not enchant.
I don't think upstream will respond to bug in time. Resolving as UPSTREAM
