Can't insert Special Characters/Emoji/Symbols to any document

Has anyone found another solution? I don't have Webroot, and I have no problem opening the Emojis, but when I click on them (and yes I know where), be it one or two (or a hundred *lol*) times - nothing happens.

It used to work til a while ago, and I haven't found a way to make it work again...

DDoes drag/drop work at all? Do you also have the problem in TextEdit?

This is the real problem that nobody seems to have has addressed so far.

I can open emoji however when I click or double-click on any icon, they do not appear on my text.

Does anybody have an answer?

Thanks

Raymond288 wrote:

I can open emoji however when I click or double-click on any icon, they do not appear on my text.

Does this happen in TextEdit?

Does drag/drop work?

Do you have Webroot garbage installed?

This happens with Pages documents and also with emails.

Raymond288 wrote:

This happens with Pages documents and also with emails.

Are you talking about Pages 4 (09) or Pages 5 (13)?

Are you talking about outgoing emails you are composing in the Mail app?

And the other questions you may have missed:

Do you have this problem with TextEdit?

Does Drag/drop work?

Do you have Webroot installed?

although the response is not directed at me, since i have the same problem, i'll answer:

pages 5.6.1 (and working with OS X el capitan, 10.11.4).

same problem when composing emails in the mail app. whether replying or composing a new 1: no difference.

yes, i also have the same problem in textedit.

drag & drop works (as does copy/paste).

if i have webroot, i can not find it (and certainly never installed it knowingly).

in addition, i suddenly can no longer hold down a key and have special characters appear (e.g.: french accents or german umlaute such as à, ç or ä, ö, ü). instead the letter just repeats itself as long as i hold down the keyyyyyyyyyyyyyy - which is pretty annoying for someone who writes in different languages.

i know there is a solution as i encountered the problem with the keys before but i can not find it any longer.

y/help!

mittgenstein wrote:

i suddenly can no longer hold down a key and have special characters appear

This is something else that webroot can do.

But also try going to system prefs/keyboard/input sources and adding a Spanish or French keyboard to your list and restarting.

mittgenstein wrote:

drag & drop works (as does copy/paste).

That's good, at least you have a ways to input things.

You might try setting up a new user account and seeing whether double-click works when you are logged into that.

In addition, I suddenly can no longer hold down a key and have special characters appear (e.g.: french accents or german umlaute such as à, ç or ä, ö, ü). instead the letter just repeats itself as long as i hold down the keyyyyyyyyyyyyyy - which is pretty annoying for someone who writes in different languages.

Launchpad : Other : Terminal.

Copy/paste the following into the Terminal and press return. This will restore the accented characters on a key press. When you are done, quit (command+Q) Terminal.

defaults write -g ApplePressAndHoldEnabled -bool true

Tom's suggestion about other languages is also useful.

hello tom & viking, thanks for the replies!

i tried tom's suggestion (since i saw it first) and am officially floored. not only did it bring back the hold-down feature (with the és and äs etc.), i can now also double-click on emojis again.

apart from the fact that i never disabled any additional keyboard (actually i don't recall ever installing any), it is equally bizarre that i only installed the german keyboard but am now also getting french and norwegian (etc.) characters.

i also don't quite understand how this could be linked to the emojis & special characters via drop-down menu (resp. control-command-spacebar).

in any event: it did fix the problem (for now ;-)) but i am not sure if it solved 1 of many apple-mysteries... 😊

greetings!

mittgenstein wrote:

i can now also double-click on emojis again.

That is really interesting!

I have not read all the responses to this, but I fixed my problem by closing Parallels. I was running Windows 10 in Coherence mode.

elopez1 wrote:

I have not read all the responses to this, but I fixed my problem by closing Parallels. I was running Windows 10 in Coherence mode.

That's a new one! Thanks for reporting it.

No problem! 🙂