Drar Apple, I'd like to talk to you about the misspelling program On My iPhone

Drar Apple, and Mr. Jobs,

I like nu iPhone, I really do, but there is à problem. I spell fairly
well, but the spell checker jeeps changing what I write into
gibberish. IT is à chore giving all the mistakes I have to correctly.

There seems to be no way to turné the misspelling program off. Since
the iPhone is à network device, maybe the off switch is at your end.
If IT is, could you please TURN THE DAMNED THING OFF, BECAUSE I AM
GOING CRAZY!

Sorry for the outburst.

Kind Regards,

Henrik Mårtensson

Sent from my iPhone

Comments

Stuart Roebuck said…
Select:

Settings->General->Keyboard

and turn off "Auto-Correction".

However, it sounds like you perhaps have the wrong keyboard language setting and that it might be trying to spell words in a different language than you are typing in? Is that a possibility?
June 29, 2009 11:48 PM
Kallokain said…
Thanks!

I am using a Swedish keyboard, because I live in Sweden and need the å, ä, and ö characters to write names. The language is set to English though, because I almost always write in English. The iPhone ought to handle that. Otherwise there would be no point to having separate keyboard and language settings.
June 30, 2009 12:38 AM
Stuart Roebuck said…
Henrik,

I agree that it should cope, but in the meantime, you can enter accents on the English keyboard by just holding the letter you want an accent on and a selection of accents appear to choose from. Perhaps that's too long-winded for lots of typing?
June 30, 2009 9:01 PM
Thomas Nilsson said…
If you select multiple keyboard layouts to be active the spelling correction actually follows the layout. And it is easy to change because you get a small globe next to your space key.
August 11, 2009 10:16 AM
Post a Comment

Popular posts from this blog

Waterfall vs. Agile: Battle of the Dunces or A Race to the Bottom?

Image
The major software methodology wars since the mid 1950’s. Someone was wrong on the Internet, so here we go… In a recent HBR article, It’s Time to End the Battle Between Waterfall and Agile , the author sets up a false premise: There is a war between Waterfall methodology and Agile. The war must end. And finally, you can combine the approaches to get the best of both worlds. This sounds good, but the article is based on a misunderstanding of both Waterfall and Agile. Also, there is no war between Waterfall methodology and Agile. There can’t be, because Waterfall methodology does not exist! Waterfall is a name for large projects that failed in the 1960’s. Waterfall was never a methodology, but a failure to apply the methodologies that existed back then. As I will show towards the end of this article, at least one of the “successful” Waterfall projects mentioned in the HBR article was neither successful, nor a Waterfall project. I got invaluable help from Alistair Cockburn. He fact che...
Read more

Performance Evaluations, Business Strategy, and Agile Methodologies

Image
It is performance evaluation time in many companies. This can be stressful, both to the people being evaluated, and the people doing the evaluation. In companies adopting agile software development methods, the tension can be extraordinary. Individual performance evaluations run counter to agile philosophy, which emphasizes team performance over individual performance. However, managers and corporate leaders need to take a few steps back, and consider the impact performance evaluations have on the organization as a whole. Especially now, in the midst of a recession, it is important to look at a companies current policies to see if they can be improved, or if they are actually holding the company back. So, how can a manager evaluate policy? Performance evaluation policies can serve as an excellent example. I'll confine myself to discussing the so-called ‘rank and yank’ methods. These are performance reviews were employees are ranked using a forced ranking system. It usually looks so...
Read more

Agile Requirements Structures, Part 1

Image
If you have worked in large Agile projects or programs, you may have noticed that there is often quite a bit of confusion about requirements, what the requirement types are, their purpose, how to write them, how to use them, and above all, what not to do with them. There are many causes for this confusion. Here are some of the more common I have seen: Nobody in the organization has read up on the requirements model it is using, so everyone makes their own interpretation. The organization deviates from a standard requirements model, but nobody knows which standard model the organization is deviating from, and/or there is no agreement about how they deviate from it. The organization has not documented its own requirements model very well. The organization mixes two or more different requirements models, often without realizing it. The organization has documented its requirements model, but finding the documentation is an epic project in itself, on par with when Henry Sta...
Read more