• Avatar
    Permanently deleted user

    Same thing happens to me.

    I use spanish and the word in spanish for "what" spells "qué" or "que" depending if it's a question or a sentence.

    For some reason (maybe for mistake), I entered the wrong word "qu". Now I can't remove that freaking word and, every time I wrote that word, it changes to "qu"

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently deleted user

    The same for me. 'Tb' seems to be reserved word

    1
    Acciones de comentarios Permalink
  • Avatar
    Trey Bennett

    When ever I delete cap G god, it will stay gone for a few days but creeps back in. I never write it or will ever.

    Fix this now.. This is crazy discrimination at worst or some moron programer pushing some god agenda o. The SwiftKey team.

    1
    Acciones de comentarios Permalink
  • Avatar
    Gabby Morin

    Wow, glad I'm not the only one - it actually inspired me to start using "dog" in place of "god" (i.e. "oh my dog", "dogdamnit", etc.). Appropriately, making this comment has forced me to deal with this very issue once again - typing "god" for this comment required me to long-press and remove the "god" with a capital G prediction several times before it finally "took" by that last usage in this sentence. However, I attempted to type it again and it showed right back up. It's infuriating - and it's not just that word. I actually came here to the support forum because I'm having this same persistent issue with the word "Screenshots" - I realize, a word I essentially "taught" to SwiftKey - the problem is that SwiftKey keeps autocorrecting "screenshots" to "Screenshots", no matter how many times I remove the capitalized version of the word. I type "screenshots" and "Screenshots" is the predicted word - even after removing it, it still shows up as a prediction on the left side of the actual word I want "screenshots". The worst part is that if I don't spell "screenshots" correctly the first time, SwiftKey will only autocorrect it to the capitalized version and only offers that version in the prediction. Regardless of how many times I try to teach SwiftKey "screenshots" - spelling it correctly, selecting it's lower-case spelling in the predictive text box so it knows that's the one I want, it doesn't matter. SwiftKey only acknowledges the capitalized version I keep killing every time it pops up. It's maddening!

    0
    Acciones de comentarios Permalink