Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 8+ native spell checker support #52

Open
TingPing opened this issue Jan 20, 2017 · 4 comments
Open

Windows 8+ native spell checker support #52

TingPing opened this issue Jan 20, 2017 · 4 comments

Comments

@TingPing
Copy link
Contributor

TingPing commented Jan 20, 2017

Since this project has actually been somewhat active recently I thought I would bring this up.

https://github.com/hexchat/hexchat/tree/master/src/libenchant_win8

As the title says this uses the native spell checking support on Windows that I wrote a few years ago. I know this is bad manners but I don't personally use Windows often so I don't have an easy way to test integrating it into the build system and I just wanted to leave this here as at least a documented implementation for those who need it. It is a self contained plugin so it is easy to build externally.

@rrthomas
Copy link
Contributor

Thanks! I don't develop on Windows much either, but documenting this would be a good start.

In any case, the whole point of Enchant is that you can build providers separately, so there's no pressing need to include it as part of the library.

@hfiguiere
Copy link
Member

Let's mark this issue appropriately :-)

@bgermann
Copy link

I had a stab at this. The main problem is that mingw does not provide the spellcheck.h header that the win8 provider uses. I did not find a good resource how to build an autotools project with a Windows 10 SDK and do not know if it is possible at all. So this might be a good reason for #58 introducing meson.

@bgermann
Copy link

The thing got into mingw at version 8.0.1 https://sourceforge.net/p/mingw-w64/mingw-w64/ci/5ff3423c505df415ca4d75a62dadbf6b5696b8ae/
So maybe this is now worth trying again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants