I can't seem to get the inline spelling check feature to work in opera10 on 64bit slack. The option is there on the right click menu, but it just doesn't seem to do anything. Anyone else see this? And does anyone know if it works on 32bit Slack13 or even 12.2 for that matter?

Looking at the /usr/bin/opera wrapper it is looking for libaspell 1.5, which it should find ok as it's in /usr/lib64.

Running a "aspell dump dicts" shows that the dictionaries are installed correctly and aspell works from the command line. I've tried using both my normal en_GB and the default en_US just in case it was a locale issue, but that doesn't appear to make any difference either. I've also tried running the unmodified opera install directly from it's extracted tarball.

I've also tried 'enable spellcheck as default' under opera:config, but that also makes no difference.

There's a spellcheck.so under /usr/lib64/opera that's not executable by default. I've tried setting that to 755 in case it made a difference. it didn't (I don't know if shared libraries have to be marked executable or not, but it was worth a shot). By running
"strings </usr/lib64/opera/spellcheck.so" I can find references to libaspell.so.15, but interestingly, a "strings </usr/lib64/opera" doesn't result in either libaspell.so or spellcheck.so, and it's not listed in ldd's output either, so god knows how they're loading it.

I Tried googling but was just getting lots of unrelated hits.


Anyone got any clues for me on this one please? I've just about come to the end of my knowledge on this.


update: This ubuntu page seems to suggest 32bit libaspell is required, though this seems a little strange to me. Anyway, I'm not going to be installing a 32bit library just for Opera when I've got a 64bit version of the same library already installed.

It is working fine in my installation of Slackware64-13. Rarely do I ever use the SlackBuild as the packages available directly from the Opera web site usually work very well.

Opera doesn't show a 64 bit version for Slackware, yet, on their main download page, so you have to dig around a bit. I download the latest builds from here:

http://my.opera.com/desktopteam/blog/

Not sure if I can help you with the exact details but this seems to have to do with the dictionary you are using. It may be that Opera is set to us English UK but only the English US dictionary is available.

edit: sorry, I saw that you looked into the dict issue through aspell.

That's interesting. The slackbuild really doesn't do a great deal other than run their install script with some parameters. I actually tried just running it inplace directly from the unchanged extracted tar.bz2 but even that doesn't work.

Which version are you running cwizardone and what did you do to install it? Also have you made your system multilib*, as that might explain it if that Ubuntu forum post was correct.

I've tried both opera-10.00.gcc4-qt4.x86_64.tar.bz2 and the more recent opera-10.10-4644.gcc4-qt4.x86_64.tar.bz2 snapshot.


edit: Ah, It looks like you are multilib from the distro in your profile. That might explain it. Though why it's insisting on a 32bit libaspell when there's a native 64bit version of the same lib to match the 64bit app is beyond me.

Admin. Please delete. duplicate message.

My apologies. I should have read your first message closer.

Aspell is not needed as the dictionary is "bullt-in" to Opera 10, so multilib really has nothing to do with it, but, btw, I was running 64 bit Opera in Slackware64 for many days before installing the multilib files.

To change or add a dictionary, open a composer window and right click on a blank space. A menu will pop up and pick "change or add dictionaries" (or something similar). Another window will open with a list of available dictionaries.

Cheers.

Nope, I occasionally see a greyed-out 'dictionaries' option, but it's not always present in the right click menu of the composer background. I've tried installing Eric's multilib gcc/glib and converted and installed the 32bit aspell packages just to see if that ubuntu forum post was right about it needing 32bit, but it doesn't change a great deal.

I'm gonna have to give-up on this now. I've put over 6 hours into trying to get this working now, and I can't justify spending the time on it anymore. There must be something wrong with my install somehow.

When I downloaded the slack64 dvd I got some errors on some packages while installing. When I checked the dvd I found that it was corrupted during download. I did a manual check on all the md5sums of the packages and individually downloaded and reinstalled all the ones that failed the md5check to save having to grab the whole 4GB file again (There weren't that many, and they were mostly trivial packages like tetex). I would have thought that this action would have sorted it all out and I've certainly not had any problems with anything else but I guess it's possible that some corruption slipped through, though I would have expected md5 to pick-up any problems.

I might try and redownload the slack dvd again and do a reinstall if I can work up the enthusiasm once I've got over the "Why don't I just use Windows" mood I'm currently in.

Thankyou to cwizard and matty for trying to help.

Know the feeling. I was feeling that way over a video issue that I was finally able to trace back to VirtualBox. It does seem I (we?) spend a great deal of time trying to get things to run as the did (or do) in winblows. If mickeysoft wasn't such a unethical bunch of thieves I would use winblows, but as they are one of the worst "corporate citizens" I won't use any of their product, if I don't have to, on principle.

As to Aspell, as I said before, you don't need it, unless you want to use it for something other than Opera.

Good Luck.
BTW, everytime I get in one of those "Why don't I just use Windows" moods, I run winblows for a while and it "cures" me in about 20 minutes or so.

If you look in /usr/bin/opera script towards the end you'll still see references to libaspell.so, so although it doesn't work in the same way as the 9.6 opera spell check worked, it appears it still uses the underlying libaspell.

However, libaspell or no, I can't get it working, so it's academic.

Just FYI.
Cheers.

http://en.wikipedia.org/wiki/Opera_10
"Previous versions of Opera contained an on-demand spell-checker based on Aspell. Opera 10 introduced an inline spell checker based on Hunspell. This is available in multi-line text areas and in the mail client. As you type, misspelled words are underlined, and can be corrected via a right click menu. The US-English dictionary is included, and there is an interface to download additional dictionaries from within the browser. This inline spell-checker has support for 48 languages."


http://hunspell.sourceforge.net/
"Hunspell is the default spell checker of OpenOffice.org and Mozilla Firefox 3 & Thunderbird..."


http://en.wikipedia.org/wiki/Hunspell
"...Hunspell is based on MySpell and is backward-compatible with MySpell dictionaries. While MySpell uses 8-bit ASCII character encoding, Hunspell can use Unicode UTF-8-encoded dictionaries.

Hunspell is the spell checker of:
OpenOffice.org, a cross-platform office suite (starting with version 2.0.2 March 8, 2006)
Mozilla products Thunderbird / Firefox (starting with version 3) and SeaMonkey (starting with version 2)
WinShell, an integrated development environment (IDE) for TeX / LaTeX on Windows
Yudit, a Unicode text editor for the X Window System
Opera 10, a multiplatform web browser and internet suite.
Google Chrome, an open source web browser developed by Google [1].
The Bat! email client by RITLABS S.R.L. since version 4.0
Apple's MacOS X 10.6 Snow Leopard

Moreover, Hunspell is supported by Enchant and Emacs...."

Thanks Cwiz. I guess the remaining references to libaspell in the script are just a case of the Opera devs being sloppy. If the spellcheck is indeed a built-in component as it seems, then it's even more puzzling why it isn't working. Oh well. *sigh*