I can confirm it in :

OpenOffice.org 3.2.1 
OOO320m19 (Build:9505)
ooo-build 3.2.1.4

except the case: 
>(...)This happens even if you ignore AutoInput and
enter the whole word(...)

what in my test shows correctly lower case if and only if I do type all letters. Typing "tes" will make "Test" to appear, while typing "test" will result in correct lower case. 

Note: If by mistake first "Test" was actually: "Test " (with space) then obviously I have to type "test " to get lower case.

There is however a bit of inconsistency. If I do type "TEST" as a first word and then enter "te" then I do get "teST" as auto input result instead of "TEST".

If I do enter "TeSt" or "TEst" as a first word then typing "te" results in "teSt" in first case but "TEst" in second case. If I type just "t" then in second case result is "tEst"!

It's really a bit non-intuitive and it seems that first letter is treated differently than following ones. What is reasonable since in Ido-European languages most sentences, names and etc. if starts with capital letter then only the first letter is capital. So it is fine to assume that "ada" should match "Adam" and be typed like "Adam" while "nic" matching "NICOLAS" should rather be "nicOLAS" than "NICOLAS" since having name in all capitals is not expected.

Suggestions:
- doing matching as case sensitive is not the best idea. The auto input is intended to speed up entering repeating data. Remembering about correct shift or not shift is not what I do expect when going for fast input;

- do not changing case when we have a non-case sensitive match is not good then. If I had a "Test" and want quickly re-enter it in another cell then I do just type "te" and I've got what I want. It's like speaking, upper and lower case do not differ, while we still expect matching person name to be correctly typed. I do say "write mcdonald" and expect: "McDonald".

Solution:
- if typing whole word works as I have seen (makes it to use correct case) then IT IS NOT A BUG.

Confirmed with Windows Vista & 7 version 3.3.0
There needs to be a way to either individually on a input undo the auto-correct or stop it from correcting. AS suggested if you type more then the 1st letter in a different case it doesn't auto correct. There are instances where the capitalization differences are important. There has to be a way to turn it off or undo it without resorting to not using the AutoInput at all.

This doesn't make sense as it is.

I believe this is a bug as I don't remember it doing it before if you manually fixed it. Also it's not happening in LibraOffice. 

This is a complete deal breaker for my ability to use or suggest OpenOffice, it makes the spreadsheet useless for anyone with large spreadsheets to deal with. I need autoinput for 90% of what I'm doing but I need to be able to force it to take the case the way I need it for the 10% of the time. My only current option is to turn it off. That the only way I can get what I need into a cell that needs different case. This renders this product useless to me.

This is ridiculous. It's very frustrating and very difficult to work around or disable for the average user. I would give it a higher importance than "trivial".

I have a list of names, combined from various sources. I am trying correct "BARBARA" to "Barbara", but because there is another instance of "BARBARA" somewhere in that column, I cannot do so. 

Similarly, if I have "Barbara Ann" and I enter the cell and remove the " Ann" to change it to "Barbara", it 'corrects' it to "BARBARA" because an instance of that exists somewhere else.

The ONLY way I am able to get this text in here is by typing "Barbara" somewhere in another column, then using "Paste Special > Text only" to overwrite the text in the cell. 

In addition, avoiding this behaviour by turning off Autoinput altogether is in "Tools > Cell Contents > Autoinput (uncheck)". I would have expected it to be on one of the panels in "Tools > Options > Calc"

Assuming this behaviour must continue to exist, I would suggest a behaviour similar to the auto capitalization of the first letter after a period. In MS Word and on my phone, the first letter after a period is automatically capitalized, but if I backspace it undoes the change of case. 

- RG>

I agree, this is more than "trivial".
I agree with sztejkat, that case-insensitive matching is better. But I would not assume anything about the cells containing Indo-European names, so I would not treat the first letter specially. People (including myself) put weird, non-language stuff into spreadsheet cells. (Sometimes by mistake, but that can be fixed.) If someone enters different cases in different cells, I would assume they meant to.
How about:
1. Case-insensitive match, but
2. When user hits TAB to cycle through the options, show all the different case versions. If the user has a lot of versions of the same letters with different case, and those differences are irrelevant, they may find this annoying. OK, so they can go back and fix their data, which is probably a good thing anyway.
3. First show the version that most closely matches in case to what they have typed. So let's say above cells contain "Barbara" and "BARBARA". If user starts typing "Ba", offer to AutoInput "Barbara"; if they press TAB, show "BARBARA". Conversely, if they start typing "BA", do the opposite.
4. Regardless of the above: If user goes into Edit mode (F2) either while first entering the cell or afterwards, assume they know what they're doing and don't AutoInput at all. Currently OO Calc changes case even when I edit a cell with F2.

One more suggestion:
5. If OO Calc completes user input via an AutoInput (or changes input via AutoCorrect / Capitalize or AutoCorrect / Replace), and the user does a single "undo" (CONTROL-Z or menu, Edit, Undo), then OO Calc should undo the automatic change only. That is, consider the automatic change as a _separate_ change that happens _after_ the user input. A second "undo" should undo the user input.

oo 4.1.2 with windows 10, same issue.
a walkaround is to wrap CLEAN() around the text :

A > CLEAN("a") > a

so far it's working here.

regards,
c

+1

I'm wondering why AutoInput is enabled by default?

Lets set this one on confirmed. At least I can do that much now.